🇩🇪 VLESS Live Verified Node

Germany (DE) — VLESS XHTTP Node

Host: 199.232.78.160:443 • Tested: 4:39:13 PM

Checked Latency 787 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://891b8403-db54-43a5-83de-f10610cd60f2@199.232.78.160:443?mode=auto&pcs=cd6e838b9bfe31cab8b3d5c858b0d6223fe84ece236c1fdb281be93c302e1e6e&path=/@WanCloudFA&security=tls&alpn=h2&encryption=none&insecure=0&host=WanCloud.global.ssl.fastly.net&fp=chrome&type=xhttp&allowInsecure=0&sni=Firefox.com#%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% (18 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Wed, 21 Oct 2026 16:39:13 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	787 ms	2a04:3542:1000:910:d474:96ff:fe4d:7a2b
Wed, 21 Oct 2026 15:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	863 ms	2a04:3542:1000:910:d474:96ff:fe4d:7a2b
Wed, 21 Oct 2026 14:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1100 ms	2a04:3542:1000:910:d474:96ff:fe4d:7a2b
Wed, 21 Oct 2026 13:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	223 ms	2a04:3542:1000:910:d474:96ff:fe4d:7a2b
Wed, 21 Oct 2026 12:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	233 ms	2a04:3542:1000:910:d474:96ff:fe4d:7a2b
Wed, 21 Oct 2026 11:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	238 ms	2a04:3542:1000:910:d474:96ff:fe4d:7a2b
Wed, 21 Oct 2026 10:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	720 ms	2a04:3542:1000:910:d474:96ff:fe4d:7a2b
Wed, 21 Oct 2026 09:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	381 ms	2a04:3542:1000:910:d474:96ff:fe4d:7a2b
Wed, 21 Oct 2026 08:55:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	713 ms	2a04:3542:1000:910:d474:96ff:fe4d:7a2b
Wed, 21 Oct 2026 08:15:17 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	875 ms	2a04:3542:1000:910:d474:96ff:fe4d:7a2b
Wed, 21 Oct 2026 07:25:21 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	798 ms	2a04:3542:1000:910:d474:96ff:fe4d:7a2b
Wed, 21 Oct 2026 06:25:21 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	698 ms	2a04:3542:1000:910:d474:96ff:fe4d:7a2b
Wed, 21 Oct 2026 05:25:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	786 ms	2a04:3542:1000:910:d474:96ff:fe4d:7a2b
Wed, 21 Oct 2026 04:25:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	852 ms	2a04:3542:1000:910:d474:96ff:fe4d:7a2b
Wed, 21 Oct 2026 03:25:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1488 ms	2a04:3542:1000:910:d474:96ff:fe4d:7a2b

⚙️ Protocol Parameter Specification

Verified protocol configuration attributes required for manual client profiles.

Host / Address 199.232.78.160

Port 443

Security Protocol TLS

Transport Type XHTTP

SNI (Server Name Indication) Firefox.com

Path /@WanCloudFA

UUID 891b8403-db54-43a5-83de-f10610cd60f2

TLS Fingerprint 17503373

🛡️

Asynchronous xHTTP Split-Stream Mesh

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

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

Deploying xHTTP on server 199.232.***.*** completely scrambles protocol signatures and packet duration metrics.

Network Port Analysis: With traffic routed across port 443, data packets pass uninhibited through carrier-grade network address translation gateways worldwide.

SNI Masking Analysis (Firefox.com): Traffic directed toward major brand Firefox.com triggers automated certificate provenance checks on national gateway routers.

uTLS Handshake Security Analysis (17503373): Configured 17503373 parameters ensure client handshakes adhere to accepted cryptographic conventions without alerting middlebox monitors.

Client Handshake Masking (uTLS): Configured 17503373 parameters ensure client handshakes adhere to accepted cryptographic conventions without alerting middlebox monitors.

❓ Frequently Asked Questions for Node #17503373

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

Deploying xHTTP on server 199.232.***.*** completely scrambles protocol signatures and packet duration metrics. 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? ▼

With traffic routed across port 443, data packets pass uninhibited through carrier-grade network address translation gateways worldwide. Traffic directed toward major brand Firefox.com triggers automated certificate provenance checks on national gateway routers. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.

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

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

Public Exit IPv4: 2a04:3542:1000:910:d474:96ff:fe4d:7a2b

Network (ASN / Org): AS202053 · UpCloud Ltd

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: UpCloud Ltd

3. Geolocation Consensus (IPv4)

Providers tallied: 23

🇩🇪 DE Germany

48% (11/23)

🇪🇸 ES Spain

30% (7/23)

🇫🇮 FI Finland

17% (4/23)

🇬🇧 GB United Kingdom

4% (1/23)

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

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	● available	—	—	1278 ms
ChatGPT (app)	● available	—	—	1096 ms
YouTube Premium	● available	—	—	1320 ms
Netflix	● available	🇪🇸 ES	full catalogue	2788 ms
Claude	○ error	🇩🇪 DE	Cloudflare challenged the request, so availability was never tested	306 ms
TikTok	● available	—	—	1083 ms
Gemini	● available	—	—	1410 ms
NotebookLM	● available	—	sign-in required	1730 ms

🤖 5. AI Model API Endpoints (Direct Probe)

AI Endpoint	Vendor	State	HTTP	Detail	RTT
OpenAI	OpenAI	● reachable	401	answered, credentials not supplied	1188 ms
Anthropic	Anthropic	● reachable	401	answered, credentials not supplied	888 ms
Google Gemini	Google	● reachable	403	answered, credentials not supplied	1311 ms
DeepSeek	DeepSeek	● reachable	401	answered, credentials not supplied	1492 ms
Qwen (Singapore)	Alibaba	● reachable	401	answered, credentials not supplied	1504 ms
Qwen (Beijing)	Alibaba	● reachable	401	answered, credentials not supplied	1893 ms
Kimi / Moonshot	Moonshot	● reachable	401	answered, credentials not supplied	3201 ms
Zhipu GLM	Zhipu	● reachable	401	answered, credentials not supplied	1600 ms