🇩🇪 VLESS REALITY Live Verified Node

Germany (DE) — VLESS TCP Node

Host: 177.3.222.142:443 • Tested: 10:12:04 AM

Checked Latency 819 ms

Est. Bandwidth 0.0 Mbps

24h Uptime SLA 100%

Exit Consensus DE (Verified)

⚡ Direct Connection URI (VLESS • Germany) Xray-core Verified • 100% Uptime

vless://50a87e21-f0e2-4b53-a787-91adfe748f63@177.3.222.142:443?type=tcp&security=reality&flow=xtls-rprx-vision&fp=chrome&pbk=6PJlXT9xrgJP8RXfhpWDMKPh4eqGt_IZmenc_a6v0gg&sni=gemsubbgem.world#%F0%9F%87%A9%F0%9F%87%AADE-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: 100% (24 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Mon, 26 Oct 2026 10:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	819 ms	177.3.222.142
Mon, 26 Oct 2026 09:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	889 ms	177.3.222.142
Mon, 26 Oct 2026 08:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	552 ms	177.3.222.142
Mon, 26 Oct 2026 07:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	390 ms	177.3.222.142
Mon, 26 Oct 2026 06:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1164 ms	177.3.222.142
Mon, 26 Oct 2026 05:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	298 ms	177.3.222.142
Mon, 26 Oct 2026 04:12:05 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	803 ms	177.3.222.142
Mon, 26 Oct 2026 03:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	462 ms	177.3.222.142
Mon, 26 Oct 2026 02:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1044 ms	177.3.222.142
Mon, 26 Oct 2026 01:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	820 ms	177.3.222.142
Mon, 26 Oct 2026 00:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	250 ms	177.3.222.142
Sun, 25 Oct 2026 23:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	966 ms	177.3.222.142
Sun, 25 Oct 2026 22:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	586 ms	177.3.222.142
Sun, 25 Oct 2026 21:12:05 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	603 ms	177.3.222.142
Sun, 25 Oct 2026 20:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	783 ms	177.3.222.142

⚙️ Protocol Parameter Specification

Verified protocol configuration attributes required for manual client profiles.

Host / Address 177.3.222.142

Port 443

Security Protocol REALITY

Transport Type TCP

SNI (Server Name Indication) gemsubbgem.world

Public Key (pbk) 6PJlXT9xrgJP8RXfhpWDMKPh4eqGt_IZmenc_a6v0gg

Flow xtls-rprx-vision

UUID 50a87e21-f0e2-4b53-a787-91adfe748f63

TLS Fingerprint 19490879

🛡️

Cryptographic Reality Shield on 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: 19490879 Custom Handshake (Active Cloaking)

The endpoint leverages cryptographic Reality camouflage over RAW / TCP to secure international internet access with an observed round-trip latency of 58 ms.

Network Port Analysis: Operating over standard port 443 bypasses common heuristic firewall rules that automatically discard anomalous transport layer assignments.

SNI Masking Analysis (gemsubbgem.world): Unremarkable domain gemsubbgem.world blends seamlessly into general international transit noise, preventing automated endpoint isolation.

uTLS Handshake Security Analysis (19490879): Using 19490879 parameters provides dependable transport-level obfuscation across international multi-hop paths.

Flow Technology: The "xtls-rprx-vision" mechanism introduces dynamic frame padding to disguise packet size patterns from Great Firewall classification engines.

Client Handshake Masking (uTLS): Using 19490879 parameters provides dependable transport-level obfuscation across international multi-hop paths.

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

❓ Frequently Asked Questions for Node #19490879

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

The endpoint leverages cryptographic Reality camouflage over RAW / TCP to secure international internet access with an observed round-trip latency of 58 ms. 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? ▼

Operating over standard port 443 bypasses common heuristic firewall rules that automatically discard anomalous transport layer assignments. Unremarkable domain gemsubbgem.world blends seamlessly into general international transit noise, preventing automated endpoint isolation. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.

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

1. Exit IP & Autonomous System (Identity) 🇩🇪 DE

Public Exit IPv4: 177.3.222.142

Network (ASN / Org): AS2 · PLAY2GO - FZCO

BGP Prefix / Subnet: —

Node Location: Frankfurt am Main, Hesse — 🇩🇪 DE

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

Address Class: 🖥️ Hosting / Datacenter

Risk Score:

20 / 100 (95% conf)

Detection Flags:

hosting

Operator / Provider: PLAY2GO - FZCO

3. Geolocation Consensus (IPv4)

Providers tallied: 20

🇩🇪 DE Germany

95% (19/20)

🇺🇸 US United States

5% (1/20)

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

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	● available	—	—	2232 ms
ChatGPT (app)	● available	—	—	2027 ms
YouTube Premium	● available	—	—	1498 ms
Netflix	● available	🇩🇪 DE	full catalogue	5490 ms
Claude	○ error	🇩🇪 DE	Cloudflare challenged the request, so availability was never tested	137 ms
TikTok	● available	—	—	3116 ms
Gemini	○ error	—	AI endpoint unreachable	1877 ms
NotebookLM	● available	—	sign-in required	5602 ms

🤖 5. AI Model API Endpoints (Direct Probe)

AI Endpoint	Vendor	State	HTTP	Detail	RTT
OpenAI	OpenAI	● reachable	401	answered, credentials not supplied	3493 ms
Anthropic	Anthropic	● reachable	401	answered, credentials not supplied	2423 ms
Google Gemini	Google	● error	—	request failed	—
DeepSeek	DeepSeek	● reachable	401	answered, credentials not supplied	2284 ms
Qwen (Singapore)	Alibaba	● error	—	request failed	—
Qwen (Beijing)	Alibaba	● error	—	request failed	—
Kimi / Moonshot	Moonshot	● reachable	401	answered, credentials not supplied	2778 ms
Zhipu GLM	Zhipu	● error	—	request failed	—