🌐 VLESS REALITY Live Verified Node

CZ (CZ) — VLESS TCP Node

Host: 193.124.17.190:443 • Tested: 1:51:43 PM

Checked Latency 1150 ms

Est. Bandwidth 0.0 Mbps

24h Uptime SLA 100%

Exit Consensus CZ (Verified)

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

vless://ed042cf7-efe0-49bd-848b-8d7e655111ff@193.124.17.190:443?encryption=none&flow=xtls-rprx-vision&fp=firefox&pbk=J-dv-HrWfQ_IOoyutv0Kg-rO8QwoRwc02dS1dS_tblk&security=reality&sid=1036b2383b72&sni=www.mozilla.org&type=tcp#%F0%9F%8C%90CZ-freevpnkeys.com-TG-%40yavpn_robot

1. Direct Single Key Copy the URI above into Happ, v2RayTun, v2rayNG, or Hiddify. 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% (15 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Wed, 21 Oct 2026 13:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1150 ms	193.124.17.190
Wed, 21 Oct 2026 12:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	888 ms	193.124.17.190
Wed, 21 Oct 2026 11:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1535 ms	193.124.17.190
Wed, 21 Oct 2026 10:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	960 ms	193.124.17.190
Wed, 21 Oct 2026 09:51:43 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1100 ms	193.124.17.190
Wed, 21 Oct 2026 08:55:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	894 ms	193.124.17.190
Wed, 21 Oct 2026 07:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1452 ms	193.124.17.190
Wed, 21 Oct 2026 06:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1454 ms	193.124.17.190
Wed, 21 Oct 2026 05:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1214 ms	193.124.17.190
Wed, 21 Oct 2026 04:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1054 ms	193.124.17.190
Wed, 21 Oct 2026 03:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1404 ms	193.124.17.190
Wed, 21 Oct 2026 02:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	787 ms	193.124.17.190
Wed, 21 Oct 2026 01:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1332 ms	193.124.17.190
Wed, 21 Oct 2026 01:03:51 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	1623 ms	193.124.17.190
Wed, 21 Oct 2026 00:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	759 ms	193.124.17.190

⚙️ Protocol Parameter Specification

Verified protocol configuration attributes required for manual client profiles.

Host / Address 193.124.17.190

Port 443

Security Protocol REALITY

Transport Type TCP

SNI (Server Name Indication) www.mozilla.org

Public Key (pbk) J-dv-HrWfQ_IOoyutv0Kg-rO8QwoRwc02dS1dS_tblk

Short ID (sid) 1036b2383b72

Flow xtls-rprx-vision

UUID ed042cf7-efe0-49bd-848b-8d7e655111ff

TLS Fingerprint 17584172

🛡️

Zero-Signature Reality Relay (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: 17584172 Custom Handshake (Active Cloaking)

Configured with advanced Reality evasion protocols over RAW / TCP, endpoint 193.124.***.***:443 ensures sustained packet throughput through aggressive firewalls.

Network Port Analysis: Firewall gateways in Iran and China permit port 443 unconditionally to avoid breaking domestic banking portals and commercial digital services.

SNI Masking Analysis (www.mozilla.org): Masking under unobtrusive host www.mozilla.org ensures outstanding longevity across mobile networks operated by MCI, Irancell, and Rightel.

uTLS Handshake Security Analysis (17584172): Emulating 17584172 safeguards the encrypted stream from unauthorized fingerprint correlation across public internet exchanges.

Flow Technology: Vision padding ("xtls-rprx-vision") randomizes encrypted payload lengths, preventing DPI middleboxes from measuring TLS negotiation characteristics.

Client Handshake Masking (uTLS): Emulating 17584172 safeguards the encrypted stream from unauthorized fingerprint correlation across public internet exchanges.

REALITY Cryptography: Reality encryption utilizing token (1036b2383b72) ensures complete forward secrecy and eliminates proxy detection risks.

❓ Frequently Asked Questions for Node #17584172

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

Configured with advanced Reality evasion protocols over RAW / TCP, endpoint 193.124.***.***:443 ensures sustained packet throughput through aggressive firewalls. 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 open-source clients supporting modern protocols: Happ, Clash Meta (Mihomo), Sing-box, v2rayNG, Streisand, and Hiddify. 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? ▼

Firewall gateways in Iran and China permit port 443 unconditionally to avoid breaking domestic banking portals and commercial digital services. Masking under unobtrusive host www.mozilla.org ensures outstanding longevity across mobile networks operated by MCI, Irancell, and Rightel. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.

What steps should I take if node #N (193.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 ⏱ 11.30s

1. Exit IP & Autonomous System (Identity) 🇨🇿 CZ

Public Exit IPv4: 193.124.17.190

Network (ASN / Org): AS57043 · HOSTKEY B.V.

BGP Prefix / Subnet: —

Node Location: Amsterdam, North Holland — 🇨🇿 CZ

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

Address Class: 🖥️ Hosting / Datacenter

Risk Score:

20 / 100 (95% conf)

Detection Flags:

hosting

Operator / Provider: HOSTKEY B.V.

3. Geolocation Consensus (IPv4)

Providers tallied: 23

🇨🇿 CZ Czech Republic

48% (11/23)

🇳🇱 NL Netherlands

39% (9/23)

🇷🇺 RU Russia

9% (2/23)

🇵🇪 PE Peru

4% (1/23)

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

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	● available	—	—	3161 ms
ChatGPT (app)	● available	—	—	2774 ms
YouTube Premium	● available	—	—	3179 ms
Netflix	● available	🇨🇿 CZ	full catalogue	3657 ms
Claude	○ error	🇳🇱 NL	Cloudflare challenged the request, so availability was never tested	486 ms
TikTok	● available	—	—	2859 ms
Gemini	● available	—	—	2881 ms
NotebookLM	● available	—	sign-in required	4798 ms

🤖 5. AI Model API Endpoints (Direct Probe)

AI Endpoint	Vendor	State	HTTP	Detail	RTT
OpenAI	OpenAI	● reachable	401	answered, credentials not supplied	2365 ms
Anthropic	Anthropic	● reachable	401	answered, credentials not supplied	2582 ms
Google Gemini	Google	● reachable	403	answered, credentials not supplied	2295 ms
DeepSeek	DeepSeek	● reachable	401	answered, credentials not supplied	2782 ms
Qwen (Singapore)	Alibaba	● reachable	401	answered, credentials not supplied	3269 ms
Qwen (Beijing)	Alibaba	● error	—	request failed	—
Kimi / Moonshot	Moonshot	● error	—	request failed	—
Zhipu GLM	Zhipu	● reachable	401	answered, credentials not supplied	2393 ms