🇩🇪 VLESS Live Verified Node

Germany (DE) — VLESS WS Node

Host: 91.107.244.35:465 • Tested: 7:54:15 AM

Checked Latency 1547 ms

Est. Bandwidth 0.0 Mbps

24h Uptime SLA 92.5%

Exit Consensus DE (Verified)

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

vless://a356fa77-7199-417a-80dd-0c0925789161@91.107.244.35:465?encryption=none&security=tls&sni=hw5.roghanmo.com&type=ws&path=/#%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: 92.5% (93 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Tue, 03 Nov 2026 07:54:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1547 ms	91.107.244.35
Tue, 03 Nov 2026 06:54:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	745 ms	91.107.244.35
Tue, 03 Nov 2026 06:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	322 ms	91.107.244.35
Tue, 03 Nov 2026 05:24:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1259 ms	91.107.244.35
Tue, 03 Nov 2026 04:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	854 ms	91.107.244.35
Tue, 03 Nov 2026 03:54:14 UTC	🇺🇸 US Main	🔴 Failed (unreachable)	—	91.107.244.35
Tue, 03 Nov 2026 02:54:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1194 ms	91.107.244.35
Tue, 03 Nov 2026 02:24:14 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	91.107.244.35
Tue, 03 Nov 2026 01:24:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	789 ms	91.107.244.35
Tue, 03 Nov 2026 00:21:53 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	914 ms	91.107.244.35
Mon, 02 Nov 2026 23:51:54 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	977 ms	91.107.244.35
Mon, 02 Nov 2026 22:51:54 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1160 ms	91.107.244.35
Mon, 02 Nov 2026 22:21:54 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	758 ms	91.107.244.35
Mon, 02 Nov 2026 21:21:53 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	808 ms	91.107.244.35
Mon, 02 Nov 2026 20:51:53 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	91.107.244.35

⚙️ Protocol Parameter Specification

Verified protocol configuration attributes required for manual client profiles.

Host / Address 91.107.244.35

Port 465

Security Protocol TLS

Transport Type WS

SNI (Server Name Indication) hw5.roghanmo.com

Path /

UUID a356fa77-7199-417a-80dd-0c0925789161

TLS Fingerprint 23045353

🛡️

Direct TLS Encrypted Channel (WS)

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

SNI: Discreet Camouflage Host (Optimized for Evasion) Port 465 (Non-Standard • Heightened Evasion Risk) uTLS: 23045353 Custom Handshake (Active Cloaking)

Protected by standard TLS encryption over WS, endpoint 91.107.***.***:465 guarantees private, uncompromised transit through international corridors.

Network Port Analysis: Non-standard port (465) carries elevated blocking probability because authoritarian firewalls in Iran and China actively filter unexpected port numbers.

SNI Masking Analysis (hw5.roghanmo.com): Camouflaged behind neutral destination hw5.roghanmo.com, this node avoids heuristic scrutiny and active probe lists maintained by authoritarian firewalls.

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

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

❓ Frequently Asked Questions for Node #23045353

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

Protected by standard TLS encryption over WS, endpoint 91.107.***.***:465 guarantees private, uncompromised transit through international corridors. 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 465 and domain masking perform under heavy censorship in Iran and China? ▼

Non-standard port (465) carries elevated blocking probability because authoritarian firewalls in Iran and China actively filter unexpected port numbers. Camouflaged behind neutral destination hw5.roghanmo.com, 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 (91.107.***.***) 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 ⏱ 16.11s

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

Public Exit IPv4: 91.107.244.35

Network (ASN / Org): AS24940 · Hetzner Online GmbH

BGP Prefix / Subnet: —

Node Location: Nuremberg, Bavaria — 🇩🇪 DE

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

Address Class: 🖥️ Hosting / Datacenter

Risk Score:

20 / 100 (95% conf)

Detection Flags:

hosting

Operator / Provider: Hetzner Online GmbH

3. Geolocation Consensus (IPv4)

Providers tallied: 22

🇩🇪 DE Germany

100% (22/22)

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

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	● available	—	—	3078 ms
ChatGPT (app)	● available	—	—	2107 ms
YouTube Premium	● available	—	—	2397 ms
Netflix	● available	🇩🇪 DE	full catalogue	3105 ms
Claude	○ error	🇩🇪 DE	Cloudflare challenged the request, so availability was never tested	406 ms
TikTok	● available	—	—	2403 ms
Gemini	● available	—	—	2499 ms
NotebookLM	○ error	—	request failed	—

🤖 5. AI Model API Endpoints (Direct Probe)

AI Endpoint	Vendor	State	HTTP	Detail	RTT
OpenAI	OpenAI	● reachable	401	answered, credentials not supplied	2476 ms
Anthropic	Anthropic	● error	—	request failed	—
Google Gemini	Google	● reachable	403	answered, credentials not supplied	2190 ms
DeepSeek	DeepSeek	● reachable	401	answered, credentials not supplied	2298 ms
Qwen (Singapore)	Alibaba	● reachable	401	answered, credentials not supplied	2875 ms
Qwen (Beijing)	Alibaba	● error	—	request failed	—
Kimi / Moonshot	Moonshot	● error	—	request failed	—
Zhipu GLM	Zhipu	● reachable	401	answered, credentials not supplied	2203 ms