🇩🇪 VLESS REALITY Live Verified Node

Germany (DE) — VLESS TCP Node

Host: 176.124.223.254:8443 • Tested: 7:21:53 PM

Checked Latency 2187 ms

Est. Bandwidth 0.0 Mbps

24h Uptime SLA 94.9%

Exit Consensus DE (Verified)

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

vless://d5b3e363-4143-435f-80d3-a51568283a22@176.124.223.254:8443?encryption=none&flow=xtls-rprx-vision&fp=firefox&pbk=SbVKOEMjK0sIlbwg4akyBg5mL5KZwwB-ed4eEE7YnRc&security=reality&sni=de2-site.kartamira.cc&type=tcp#%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: 94.9% (39 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Fri, 30 Oct 2026 19:34:11 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	954 ms	193.223.107.106
Fri, 30 Oct 2026 19:29:07 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	701 ms	193.223.107.106
Fri, 30 Oct 2026 19:24:10 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	563 ms	193.223.107.106
Fri, 30 Oct 2026 19:21:53 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	2187 ms	193.223.107.106
Fri, 30 Oct 2026 19:19:06 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	580 ms	193.223.107.106
Fri, 30 Oct 2026 19:03:02 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	652 ms	193.223.107.106
Fri, 30 Oct 2026 18:57:47 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	941 ms	193.223.107.106
Fri, 30 Oct 2026 18:47:33 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	1279 ms	193.223.107.106
Fri, 30 Oct 2026 18:42:05 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	559 ms	193.223.107.106
Fri, 30 Oct 2026 18:32:13 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	1555 ms	193.223.107.106
Fri, 30 Oct 2026 18:26:51 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	548 ms	193.223.107.106
Fri, 30 Oct 2026 18:21:54 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	2120 ms	193.223.107.106
Fri, 30 Oct 2026 18:06:24 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	891 ms	193.223.107.106
Fri, 30 Oct 2026 17:51:20 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	1966 ms	193.223.107.106
Fri, 30 Oct 2026 17:46:22 UTC	🇷🇺 RU Probe	🔴 Failed (tspu_timeout)	—	193.223.107.106

⚙️ Protocol Parameter Specification

Verified protocol configuration attributes required for manual client profiles.

Host / Address 176.124.223.254

Port 8443

Security Protocol REALITY

Transport Type TCP

SNI (Server Name Indication) de2-site.kartamira.cc

Public Key (pbk) SbVKOEMjK0sIlbwg4akyBg5mL5KZwwB-ed4eEE7YnRc

Flow xtls-rprx-vision

UUID d5b3e363-4143-435f-80d3-a51568283a22

TLS Fingerprint 21892613

🛡️

Perimeter-Defeating VLESS Node

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

SNI: Discreet Camouflage Host (Optimized for Evasion) Port 8443 (Alternative Web Channel) uTLS: 21892613 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: The configuration utilizes port 8443 to provide redundant network ingress for users experiencing regional routing anomalies.

SNI Masking Analysis (de2-site.kartamira.cc): By steering clear of prominent corporate brands, domain de2-site.kartamira.cc maintains uninterrupted transit across heavily policed internet pipelines.

uTLS Handshake Security Analysis (21892613): Emulating 21892613 parameters provides adequate traffic camouflage across standard commercial broadband providers.

Flow Technology: Deploying "xtls-rprx-vision" ensures the encrypted session resists advanced machine-learning classification models at border gateways.

Client Handshake Masking (uTLS): Emulating 21892613 parameters provides adequate traffic camouflage across standard commercial broadband providers.

REALITY Cryptography: Cryptographic validation via public key (SbVKOEMjK0...) and Short ID (—) ensures secure handshake verification with Tier-1 International Carrier.

❓ Frequently Asked Questions for Node #21892613

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 8443 and domain masking perform under heavy censorship in Iran and China? ▼

The configuration utilizes port 8443 to provide redundant network ingress for users experiencing regional routing anomalies. By steering clear of prominent corporate brands, domain de2-site.kartamira.cc maintains uninterrupted transit across heavily policed internet pipelines. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.

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

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

Public Exit IPv4: 193.223.107.106

Network (ASN / Org): AS198883 · Tabunscic Anatoli

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: Tabunscic Anatoli

3. Geolocation Consensus (IPv4)

Providers tallied: 23

🇩🇪 DE Germany

52% (12/23)

🇹🇷 TR Turkey

48% (11/23)

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

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	● available	—	—	1517 ms
ChatGPT (app)	● available	—	—	2394 ms
YouTube Premium	● available	—	—	1603 ms
Netflix	● available	🇩🇪 DE	full catalogue	3425 ms
Claude	○ error	🇩🇪 DE	Cloudflare challenged the request, so availability was never tested	417 ms
TikTok	● available	—	—	2422 ms
Gemini	● available	—	—	2422 ms
NotebookLM	● blocked	—	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	2511 ms
Anthropic	Anthropic	● reachable	401	answered, credentials not supplied	1810 ms
Google Gemini	Google	● reachable	403	answered, credentials not supplied	2011 ms
DeepSeek	DeepSeek	● reachable	401	answered, credentials not supplied	2931 ms
Qwen (Singapore)	Alibaba	● error	—	request failed	—
Qwen (Beijing)	Alibaba	● error	—	request failed	—
Kimi / Moonshot	Moonshot	● error	—	request failed	—
Zhipu GLM	Zhipu	● reachable	401	answered, credentials not supplied	2524 ms