🇬🇧 VLESS REALITY نود فعال و تاییدشده

United Kingdom (GB) — VLESS TCP Node

Host: 104.239.12.81:443 • Tested: 2:21:43 PM

Checked Latency 814 ms

Est. Bandwidth 0.0 Mbps

24h Uptime SLA 100%

Exit Consensus GB (Verified)

⚡ لینک مستقیم اتصال (VLESS • United Kingdom) Xray-core Verified • 100% Uptime

vless://d806a58b-33aa-42e0-b170-395e49c16b37@104.239.12.81:443?encryption=none&flow=xtls-rprx-vision&fp=firefox&pbk=Y0noOXC8qHmbM0GmDpj-9BBwKSOtHs-uMbNfKU050GQ&security=reality&sid=b558b9305a0b&sni=www.microsoft.com&type=tcp#%F0%9F%87%AC%F0%9F%87%A7GB-freevpnkeys.com-TG-%40yavpn_robot

۱. ایمپورت مستقیم کلید لینک بالا را در Happ، v2RayTun، v2rayNG یا Hiddify کپی کنید.

۲. اشتراک خودکار رایگان برای بروزرسانی خودکار سرورها، لینک اشتراک را اضافه کنید: https://freevpnkeys.com/sub/happ

۳. کلید اختصاصی بدون افت سرعت برای سرعت ۱۰ گیگابیت و دور زدن محدودیت‌های شدید ملی، کلید اختصاصی را از ربات تلگرام @yavpn_robot دریافت کنید.

⚡ تست زنده تاخیر مرورگر

اندازه‌گیری زمان رفت و برگشت (RTT) از مرورگر شما تا این نود.

👍 Community Health Rating

Does this server currently connect and route traffic from your location?

🚀 افزودن با ۱ کلیک به اپلیکیشن

افزودن سریع این سرور به برنامه‌های محبوب فیلترشکن:

Happ ↗

iOS / Android / PC / Mac

v2RayTun ↗

Android / iOS / PC / Mac

Incy ↗

iOS / Android / PC / Mac

v2rayNG ↗

Android

FlClashX / Clash ↗

Windows / macOS / Android

Karing / sing-box ↗

Core / GUI

📊 Recent Verification History

Automated multi-point health probes through Xray-core / libxray (verified every 30 minutes)

24h SLA: 100% (22 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Wed, 21 Oct 2026 14:21:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	814 ms	104.239.12.81
Wed, 21 Oct 2026 13:21:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	759 ms	104.239.12.81
Wed, 21 Oct 2026 12:21:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1312 ms	104.239.12.81
Wed, 21 Oct 2026 11:21:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	839 ms	104.239.12.81
Wed, 21 Oct 2026 10:21:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	764 ms	104.239.12.81
Wed, 21 Oct 2026 09:13:40 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	993 ms	104.239.12.81
Wed, 21 Oct 2026 07:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	904 ms	104.239.12.81
Wed, 21 Oct 2026 06:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	960 ms	104.239.12.81
Wed, 21 Oct 2026 05:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1295 ms	104.239.12.81
Wed, 21 Oct 2026 04:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	764 ms	104.239.12.81
Wed, 21 Oct 2026 03:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	786 ms	104.239.12.81
Wed, 21 Oct 2026 02:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1530 ms	104.239.12.81
Wed, 21 Oct 2026 01:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	753 ms	104.239.12.81
Wed, 21 Oct 2026 00:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	826 ms	104.239.12.81
Tue, 20 Oct 2026 23:59:35 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	1251 ms	104.239.12.81

⚙️ پارامترهای فنی پروتکل

Verified protocol configuration attributes required for manual client profiles.

آدرس هاست / سرور 104.239.12.81

پورت 443

امنیت (Security) REALITY

نوع انتقال (Transport) TCP

شاخص SNI www.microsoft.com

کلید عمومی (pbk) Y0noOXC8qHmbM0GmDpj-9BBwKSOtHs-uMbNfKU050GQ

شناسه کوتاه (sid) b558b9305a0b

جریان (Flow) xtls-rprx-vision

UUID d806a58b-33aa-42e0-b170-395e49c16b37

اثر انگشت TLS 17461632

🛡️

Next-Gen VLESS Vision Tunnel

Cryptographic resistance profile and Deep Packet Inspection (DPI) evasion analysis

SNI: Major Cloud Target SNI (Active Probe Susceptibility) Port 443 (Universal HTTPS Gateway) uTLS: 17461632 Custom Handshake (Active Cloaking)

Deployed across RAW / TCP transport with proprietary Reality proxy shielding, node 104.239.***.***:443 evades state-level deep packet inspection in highly restricted regions such as China and Iran.

Network Port Analysis: Selecting port 443 allows client connections to blend seamlessly with millions of simultaneous browser sessions across international border checkpoints.

SNI Masking Analysis (www.microsoft.com): Censorship filters in China and Iran cross-reference SNI www.microsoft.com against authentic regional IP clusters, terminating unverified routing pairs.

uTLS Handshake Security Analysis (17461632): Configuring 17461632 parameters delivers consistent connection anonymity across diverse intermediate carrier networks.

Flow Technology: Vision padding ("xtls-rprx-vision") randomizes encrypted payload lengths, preventing DPI middleboxes from measuring TLS negotiation characteristics.

Client Handshake Masking (uTLS): Configuring 17461632 parameters delivers consistent connection anonymity across diverse intermediate carrier networks.

REALITY Cryptography: Node 104.239.***.*** authenticates incoming requests using pinned key (Y0noOXC8qH...), preventing unauthorized middlebox injection.

❓ Frequently Asked Questions for Node #17461632

How does node #N bypass state-level censorship and firewall restrictions? ▼

Deployed across RAW / TCP transport with proprietary Reality proxy shielding, node 104.239.***.***:443 evades state-level deep packet inspection in highly restricted regions such as China and Iran. Located in Netherlands and peered with Tier-1 International Carrier, it sustains verified 99.6% reliability with low response times around 58 ms.

What client software is recommended to connect to this VLESS configuration? ▼

We advise using proven open-source clients supporting modern protocols: Happ, Clash Meta (Mihomo), Sing-box, v2rayNG, Streisand, and Hiddify. Each platform supports direct QR scanning and instant URI import.

Can this node unblock restricted artificial intelligence platforms and global 4K media? ▼

Yes. Routing through Tier-1 International Carrier in Netherlands provides pristine residential or clean datacenter egress. Verified nodes reliably bypass regional barriers on OpenAI ChatGPT, Anthropic Claude, Google Gemini, YouTube Premium, and Netflix without captcha challenges.

How do port 443 and domain masking perform under heavy censorship in Iran and China? ▼

Selecting port 443 allows client connections to blend seamlessly with millions of simultaneous browser sessions across international border checkpoints. Censorship filters in China and Iran cross-reference SNI www.microsoft.com against authentic regional IP clusters, terminating unverified routing pairs. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.

What steps should I take if node #N (104.239.***.***) experiences a connection timeout? ▼

Our automated probing infrastructure validates public keys continuously. If this endpoint becomes unreachable, import our dynamic subscription URL (/sub/happ/all or /sub/clash/all) to maintain an always-updated list of responsive proxy nodes.

🌐 7-Service Geocheck & Regional Consensus

Authentic multi-provider exit node audit across 16 GeoIP databases, RIPE/ASN, proxycheck.io v3, CDN PoP, AI APIs, and Stash probes.

GeoCheck v1.4 ⏱ 10.27s

1. Exit IP & Autonomous System (Identity) 🇬🇧 GB

Public Exit IPv4: 104.239.12.81

Network (ASN / Org): AS57043 · TNGNET B.V.

BGP Prefix / Subnet: —

Node Location: Hoofddorp, North Holland — 🇬🇧 GB

2. IP Address Reputation (proxycheck.io v3) Hosting

Address Class: 🖥️ Hosting / Datacenter

Risk Score:

20 / 100 (95% conf)

Detection Flags:

hosting

Operator / Provider: TNGNET B.V.

3. Geolocation Consensus (IPv4)

Providers tallied: 25

🇬🇧 GB United Kingdom

56% (14/25)

🇳🇱 NL Netherlands

44% (11/25)

🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	● available	—	—	2295 ms
ChatGPT (app)	● available	—	—	2009 ms
YouTube Premium	● available	—	—	2175 ms
Netflix	● available	🇬🇧 GB	full catalogue	3386 ms
Claude	○ error	🇳🇱 NL	Cloudflare challenged the request, so availability was never tested	264 ms
TikTok	● available	—	—	2303 ms
Gemini	● available	—	—	2380 ms
NotebookLM	● available	—	sign-in required	4306 ms

🤖 5. AI Model API Endpoints (Direct Probe)

AI Endpoint	Vendor	State	HTTP	Detail	RTT
OpenAI	OpenAI	● reachable	401	answered, credentials not supplied	1928 ms
Anthropic	Anthropic	● reachable	401	answered, credentials not supplied	2090 ms
Google Gemini	Google	● reachable	403	answered, credentials not supplied	1879 ms
DeepSeek	DeepSeek	● reachable	401	answered, credentials not supplied	2183 ms
Qwen (Singapore)	Alibaba	● reachable	401	answered, credentials not supplied	2792 ms
Qwen (Beijing)	Alibaba	● error	—	request failed	—
Kimi / Moonshot	Moonshot	● error	—	request failed	—
Zhipu GLM	Zhipu	● reachable	401	answered, credentials not supplied	2128 ms