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

RS (RS) — VLESS TCP Node

Host: 185.105.108.176:443 • Tested: 10:20:47 PM

Checked Latency 1415 ms

Est. Bandwidth 0.0 Mbps

24h Uptime SLA 96.3%

Exit Consensus RS (Verified)

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

vless://689a62e4-37e7-41de-9e6a-f2a56368c9e2@185.105.108.176:443?type=tcp&headerType=none&security=reality&encryption=none&sni=www.google.co.uk&fp=firefox&pbk=U9O1sbuPwoTowF3Ka7CIgUZlRjokulxSwsYohEGCLA8&sid=0d87fec579&flow=xtls-rprx-vision#%F0%9F%8C%90RS-freevpnkeys.com-TG-%40yavpn_robot

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

۲. اشتراک خودکار رایگان برای بروزرسانی خودکار سرورها، لینک اشتراک را اضافه کنید: 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: 96.3% (27 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Fri, 23 Oct 2026 22:20:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1415 ms	185.72.11.73
Fri, 23 Oct 2026 21:20:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1040 ms	185.72.11.73
Fri, 23 Oct 2026 20:20:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	2280 ms	185.72.11.73
Fri, 23 Oct 2026 19:20:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1793 ms	185.72.11.73
Fri, 23 Oct 2026 18:50:47 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	185.72.11.73
Fri, 23 Oct 2026 17:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	802 ms	185.72.11.73
Fri, 23 Oct 2026 16:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	2541 ms	185.72.11.73
Fri, 23 Oct 2026 15:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	2102 ms	185.72.11.73
Fri, 23 Oct 2026 14:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	3695 ms	185.72.11.73
Fri, 23 Oct 2026 13:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	2240 ms	185.72.11.73
Fri, 23 Oct 2026 12:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	2006 ms	185.72.11.73
Fri, 23 Oct 2026 11:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	3949 ms	185.72.11.73
Fri, 23 Oct 2026 10:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	2527 ms	185.72.11.73
Fri, 23 Oct 2026 09:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1957 ms	185.72.11.73
Fri, 23 Oct 2026 08:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	3139 ms	185.72.11.73

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

Verified protocol configuration attributes required for manual client profiles.

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

پورت 443

امنیت (Security) REALITY

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

شاخص SNI www.google.co.uk

کلید عمومی (pbk) U9O1sbuPwoTowF3Ka7CIgUZlRjokulxSwsYohEGCLA8

شناسه کوتاه (sid) 0d87fec579

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

UUID 689a62e4-37e7-41de-9e6a-f2a56368c9e2

اثر انگشت TLS 18191671

🛡️

Hardened Reality Ingress (RAW / TCP)

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

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

This routing point in Netherlands pairs RAW / TCP transport with authenticated Reality masking to prevent active probing filters from flagging proxy handshakes.

Network Port Analysis: Traversing egress routes through port 443 provides maximum reliability since international border firewalls allow encrypted web handshakes unrestricted passage.

SNI Masking Analysis (www.google.co.uk): Massive tech infrastructure domains like www.google.co.uk are subjected to synthetic handshake replays by sophisticated inspection systems.

uTLS Handshake Security Analysis (18191671): The 18191671 emulation profile standardizes cryptographic cipher orderings to resist passive inspection sweeps.

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

Client Handshake Masking (uTLS): The 18191671 emulation profile standardizes cryptographic cipher orderings to resist passive inspection sweeps.

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

❓ Frequently Asked Questions for Node #18191671

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

This routing point in Netherlands pairs RAW / TCP transport with authenticated Reality masking to prevent active probing filters from flagging proxy handshakes. 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 clients supporting modern protocols: Happ, Incy (incy.cc), v2RayTun, Clash Meta (Mihomo), Sing-box, v2rayNG, and Streisand. 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? ▼

Traversing egress routes through port 443 provides maximum reliability since international border firewalls allow encrypted web handshakes unrestricted passage. Massive tech infrastructure domains like www.google.co.uk are subjected to synthetic handshake replays by sophisticated inspection systems. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.

What steps should I take if node #N (185.105.***.***) 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 ⏱ 9.99s

1. Exit IP & Autonomous System (Identity) 🇷🇸 RS

Public Exit IPv4: 185.72.11.73

Network (ASN / Org): AS205007 · TradeZone LLC

BGP Prefix / Subnet: —

Node Location: T'bilisi (Isani-Samgori), T'bilisi — 🇷🇸 RS

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

Address Class: 🏠 Residential / ISP

Risk Score:

0 / 100 (95% conf)

Detection Flags:

clean

Operator / Provider: TradeZone LLC

3. Geolocation Consensus (IPv4)

Providers tallied: 25

🇷🇸 RS Serbia

76% (19/25)

🇬🇪 GE Georgia

12% (3/25)

🇷🇺 RU Russia

8% (2/25)

🇳🇱 NL Netherlands

4% (1/25)

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

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	● available	—	—	2220 ms
ChatGPT (app)	● available	—	—	2035 ms
YouTube Premium	● blocked	🇷🇺 RU	not offered in this country	2417 ms
Netflix	● available	🇷🇸 RS	full catalogue	4509 ms
Claude	○ error	🇷🇸 RS	Cloudflare challenged the request, so availability was never tested	200 ms
TikTok	● available	—	—	2530 ms
Gemini	● blocked	🇷🇺 RU	not offered in this country	1914 ms
NotebookLM	● blocked	🇷🇺 RU	not offered in this country	—

🤖 5. AI Model API Endpoints (Direct Probe)

AI Endpoint	Vendor	State	HTTP	Detail	RTT
OpenAI	OpenAI	● reachable	401	answered, credentials not supplied	2227 ms
Anthropic	Anthropic	● reachable	401	answered, credentials not supplied	2197 ms
Google Gemini	Google	● reachable	403	answered, credentials not supplied	2239 ms
DeepSeek	DeepSeek	● reachable	401	answered, credentials not supplied	2806 ms
Qwen (Singapore)	Alibaba	● reachable	401	answered, credentials not supplied	2809 ms
Qwen (Beijing)	Alibaba	● error	—	request failed	—
Kimi / Moonshot	Moonshot	● error	—	request failed	—
Zhipu GLM	Zhipu	● reachable	401	answered, credentials not supplied	2690 ms