🌐 VLESS REALITY Live Verified Node

UA (UA) — VLESS TCP Node

Host: 31.222.235.81:443 • Tested: 4:54:14 PM

Checked Latency 1506 ms

Est. Bandwidth 0.0 Mbps

24h Uptime SLA 88.5%

Exit Consensus UA (Verified)

⚡ Direct Connection URI (VLESS • UA) Xray-core Verified • 88.5% Uptime

vless://d8b58872-cc25-4bb2-badb-b86399c075fa@31.222.235.81:443?security=reality&encryption=none&pbk=L9IllZt5vcjYVY_6rmCJ_9ypmJsBK8dSWkNVCStrZjk&headerType=none&fp=chrome&type=tcp&sni=www.cloudflare.com&sid=d8b58872#%F0%9F%8C%90UA-freevpnkeys.com-TG-%40yavpn_robot

1. Direct Single Key Copy the URI above into Happ, Incy, v2RayTun, or v2rayNG. Re-tested every 30 min.

2. Free Auto-Updating Subscription Auto-sync fresh working nodes every 30 min: https://freevpnkeys.com/sub/happ

3. Private 10 Gbps Anti-DPI Multi-Key Need zero congestion, 10 Gbps speed & strict ISP whitelist bypass? Get a private key in Telegram bot @yavpn_robot (~$0.05/day).

⚡ Interactive Browser Ping Test

Direct client-to-node round-trip time (RTT) measured in your browser.

👍 Community Health Rating

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

🚀 1-Click App Import

Instantly add this proxy node to your favorite client application:

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: 88.5% (26 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Tue, 03 Nov 2026 16:54:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1506 ms	31.222.235.81
Tue, 03 Nov 2026 15:54:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	814 ms	31.222.235.81
Tue, 03 Nov 2026 15:24:14 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	31.222.235.81
Tue, 03 Nov 2026 14:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	803 ms	31.222.235.81
Tue, 03 Nov 2026 13:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	2015 ms	31.222.235.81
Tue, 03 Nov 2026 12:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1097 ms	31.222.235.81
Tue, 03 Nov 2026 11:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	550 ms	31.222.235.81
Tue, 03 Nov 2026 10:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1847 ms	31.222.235.81
Tue, 03 Nov 2026 09:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	895 ms	31.222.235.81
Tue, 03 Nov 2026 08:24:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	610 ms	31.222.235.81
Tue, 03 Nov 2026 07:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	2163 ms	31.222.235.81
Tue, 03 Nov 2026 06:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	650 ms	31.222.235.81
Tue, 03 Nov 2026 05:24:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	852 ms	31.222.235.81
Tue, 03 Nov 2026 04:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1299 ms	31.222.235.81
Tue, 03 Nov 2026 03:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	2078 ms	31.222.235.81

⚙️ Protocol Parameter Specification

Verified protocol configuration attributes required for manual client profiles.

Host / Address 31.222.235.81

Port 443

Security Protocol REALITY

Transport Type TCP

SNI (Server Name Indication) www.cloudflare.com

Public Key (pbk) L9IllZt5vcjYVY_6rmCJ_9ypmJsBK8dSWkNVCStrZjk

Short ID (sid) d8b58872

UUID d8b58872-cc25-4bb2-badb-b86399c075fa

TLS Fingerprint 20511827

🛡️

VLESS Stealth Cloaking via 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: 20511827 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: Port 443 functions as the bedrock gateway for encrypted web communications, making discriminatory packet drops virtually impossible without crippling nationwide commerce.

SNI Masking Analysis (www.cloudflare.com): Masking under dominant cloud property (www.cloudflare.com) exposes the server to active probing sweeps conducted by the Great Firewall and national perimeter monitors.

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

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

REALITY Cryptography: Server-pinned Reality key (L9IllZt5vc...) coupled with session ID (d8b58872) guarantees zero-knowledge mutual authorization in Netherlands.

❓ Frequently Asked Questions for Node #20511827

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? ▼

Port 443 functions as the bedrock gateway for encrypted web communications, making discriminatory packet drops virtually impossible without crippling nationwide commerce. Masking under dominant cloud property (www.cloudflare.com) exposes the server to active probing sweeps conducted by the Great Firewall and national perimeter monitors. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.

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

1. Exit IP & Autonomous System (Identity) 🇺🇦 UA

Public Exit IPv4: 31.222.235.81

Network (ASN / Org): AS202302 · NETH LLC

BGP Prefix / Subnet: —

Node Location: Kyiv, Kyiv City — 🇺🇦 UA

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

Address Class: 🖥️ Hosting / Datacenter

Risk Score:

20 / 100 (95% conf)

Detection Flags:

hosting

Operator / Provider: NETH LLC

3. Geolocation Consensus (IPv4)

Providers tallied: 21

🇺🇦 UA Ukraine

90% (19/21)

🇮🇷 IR Iran

10% (2/21)

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

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	● available	—	—	2773 ms
ChatGPT (app)	● available	—	—	2616 ms
YouTube Premium	● blocked	🇮🇷 IR	not offered in this country	2725 ms
Netflix	● available	🇺🇦 UA	full catalogue	3979 ms
Claude	● available	🇺🇦 UA	Anthropic API reachable	257 ms
TikTok	● available	—	—	3523 ms
Gemini	● blocked	🇮🇷 IR	not offered in this country	—
NotebookLM	● blocked	🇮🇷 IR	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	2840 ms
Anthropic	Anthropic	● reachable	401	answered, credentials not supplied	2839 ms
Google Gemini	Google	● reachable	403	answered, credentials not supplied	2901 ms
DeepSeek	DeepSeek	● reachable	401	answered, credentials not supplied	2917 ms
Qwen (Singapore)	Alibaba	● reachable	401	answered, credentials not supplied	3229 ms
Qwen (Beijing)	Alibaba	● error	—	request failed	—
Kimi / Moonshot	Moonshot	● error	—	request failed	—
Zhipu GLM	Zhipu	● reachable	401	answered, credentials not supplied	2774 ms