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

United States (US) — VLESS TCP Node

Host: 162.35.8.62:443 • Tested: 7:20:47 PM

Checked Latency 601 ms

Est. Bandwidth 0.0 Mbps

24h Uptime SLA 100%

Exit Consensus US (Verified)

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

vless://056405e8-de9f-4d0d-8145-956f13cc34da@162.35.8.62:443?fp=chrome&pbk=5-9YzvyXcZ4J5Z4OaVTUbxUU2InvnwT17m0XY-Jse1E&security=reality&sid=257420d9d430152a&sni=a0688bt.us4.h1clayd.click&type=tcp#%F0%9F%87%BA%F0%9F%87%B8US-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: 100% (32 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Wed, 21 Oct 2026 19:20:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	601 ms	162.35.8.62
Wed, 21 Oct 2026 18:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1991 ms	162.35.8.62
Wed, 21 Oct 2026 17:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	894 ms	162.35.8.62
Wed, 21 Oct 2026 17:20:48 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1959 ms	162.35.8.62
Wed, 21 Oct 2026 16:39:13 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1848 ms	162.35.8.62
Wed, 21 Oct 2026 15:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1543 ms	162.35.8.62
Wed, 21 Oct 2026 15:21:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1107 ms	162.35.8.62
Wed, 21 Oct 2026 14:21:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1445 ms	162.35.8.62
Wed, 21 Oct 2026 13:21:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1902 ms	162.35.8.62
Wed, 21 Oct 2026 12:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1153 ms	162.35.8.62
Wed, 21 Oct 2026 12:21:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1437 ms	162.35.8.62
Wed, 21 Oct 2026 11:21:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1424 ms	162.35.8.62
Wed, 21 Oct 2026 10:21:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	942 ms	162.35.8.62
Wed, 21 Oct 2026 09:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1247 ms	162.35.8.62
Wed, 21 Oct 2026 09:13:40 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	2666 ms	162.35.8.62

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

Verified protocol configuration attributes required for manual client profiles.

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

پورت 443

امنیت (Security) REALITY

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

شاخص SNI a0688bt.us4.h1clayd.click

کلید عمومی (pbk) 5-9YzvyXcZ4J5Z4OaVTUbxUU2InvnwT17m0XY-Jse1E

شناسه کوتاه (sid) 257420d9d430152a

UUID 056405e8-de9f-4d0d-8145-956f13cc34da

اثر انگشت TLS 17131599

🛡️

VLESS Stealth Cloaking via RAW / TCP

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

SNI: Discreet Camouflage Host (Optimized for Evasion) Port 443 (Universal HTTPS Gateway) uTLS: 17131599 Custom Handshake (Active Cloaking)

Configured with advanced Reality evasion protocols over RAW / TCP, endpoint 162.35.***.***:443 ensures sustained packet throughput through aggressive firewalls.

Network Port Analysis: Port 443 functions as the bedrock gateway for encrypted web communications, making discriminatory packet drops virtually impossible without crippling nationwide commerce.

SNI Masking Analysis (a0688bt.us4.h1clayd.click): Camouflaged behind neutral destination a0688bt.us4.h1clayd.click, this node avoids heuristic scrutiny and active probe lists maintained by authoritarian firewalls.

uTLS Handshake Security Analysis (17131599): Applying custom 17131599 client parameters conceals underlying application identity during transport layer negotiations.

Client Handshake Masking (uTLS): Applying custom 17131599 client parameters conceals underlying application identity during transport layer negotiations.

REALITY Cryptography: Server-pinned Reality key (5-9YzvyXcZ...) coupled with session ID (257420d9d430152a) guarantees zero-knowledge mutual authorization in Netherlands.

❓ Frequently Asked Questions for Node #17131599

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

Configured with advanced Reality evasion protocols over RAW / TCP, endpoint 162.35.***.***:443 ensures sustained packet throughput through aggressive firewalls. 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? ▼

Port 443 functions as the bedrock gateway for encrypted web communications, making discriminatory packet drops virtually impossible without crippling nationwide commerce. Camouflaged behind neutral destination a0688bt.us4.h1clayd.click, this node avoids heuristic scrutiny and active probe lists maintained by authoritarian firewalls. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.

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

1. Exit IP & Autonomous System (Identity) 🇺🇸 US

Public Exit IPv4: 162.35.8.62

Network (ASN / Org): AS26666

BGP Prefix / Subnet: —

Node Location: San Jose (North San Jose), California — 🇺🇸 US

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

Address Class: 🏠 Residential / ISP

Risk Score:

0 / 100 (95% conf)

Detection Flags:

clean

Operator / Provider: —

3. Geolocation Consensus (IPv4)

Providers tallied: 17

🇺🇸 US United States

88% (15/17)

🇷🇺 RU Russia

12% (2/17)

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

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	● available	—	—	3095 ms
ChatGPT (app)	● available	—	—	3006 ms
YouTube Premium	● blocked	🇷🇺 RU	not offered in this country	2915 ms
Netflix	● available	🇺🇸 US	full catalogue	4513 ms
Claude	○ error	🇺🇸 US	Cloudflare challenged the request, so availability was never tested	666 ms
TikTok	● available	—	—	3093 ms
Gemini	● blocked	🇷🇺 RU	not offered in this country	2888 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	2895 ms
Anthropic	Anthropic	● reachable	401	answered, credentials not supplied	2746 ms
Google Gemini	Google	● reachable	403	answered, credentials not supplied	2650 ms
DeepSeek	DeepSeek	● reachable	401	answered, credentials not supplied	3113 ms
Qwen (Singapore)	Alibaba	● reachable	401	answered, credentials not supplied	3916 ms
Qwen (Beijing)	Alibaba	● error	—	request failed	—
Kimi / Moonshot	Moonshot	● error	—	request failed	—
Zhipu GLM	Zhipu	● reachable	401	answered, credentials not supplied	3226 ms