🌐 VLESS Live Verified Node

KZ (KZ) — VLESS WS Node

Host: 104.238.24.185:443 • Tested: 9:50:47 PM

Checked Latency 969 ms

Est. Bandwidth 0.0 Mbps

24h Uptime SLA 88.5%

Exit Consensus KZ (Verified)

⚡ Direct Connection URI (VLESS • KZ) Xray-core Verified • 88.5% Uptime

vless://495c7195-85b8-498a-bf20-2ea9ce9175b5@104.238.24.185:443?sni=snip.edgeoneai.cc.cd&type=ws&host=snip.edgeoneai.cc.cd&path=/fdip=sstp://vpn:vpn@public-vpn-200.opengw.net:443fp=chrome&security=tls#%F0%9F%8C%90KZ-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: 88.5% (26 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Thu, 22 Oct 2026 21:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	969 ms	2a09:bac5:47e5:25eb::3c7:7
Thu, 22 Oct 2026 20:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1008 ms	2a09:bac5:47e5:25eb::3c7:19
Thu, 22 Oct 2026 19:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1135 ms	2a09:bac5:47e5:25eb::3c7:7
Thu, 22 Oct 2026 18:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	984 ms	2a09:bac5:47e5:25eb::3c7:19
Thu, 22 Oct 2026 17:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	864 ms	2a09:bac5:47e5:25eb::3c7:18
Thu, 22 Oct 2026 16:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	902 ms	2a09:bac5:47e5:25eb::3c7:7
Thu, 22 Oct 2026 15:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1500 ms	2a09:bac5:47e5:25eb::3c7:7
Thu, 22 Oct 2026 14:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	864 ms	2a09:bac5:47e5:25eb::3c7:7
Thu, 22 Oct 2026 13:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	765 ms	2a09:bac5:47e5:25eb::3c7:7
Thu, 22 Oct 2026 13:20:47 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	2a09:bac5:47e5:25eb::3c7:7
Thu, 22 Oct 2026 12:50:47 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	2a09:bac5:47e5:25eb::3c7:7
Thu, 22 Oct 2026 11:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1700 ms	2a09:bac5:47e5:25eb::3c7:7
Thu, 22 Oct 2026 11:20:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	819 ms	2a09:bac5:47e5:25eb::3c7:7
Thu, 22 Oct 2026 10:20:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	984 ms	2a09:bac5:47e5:25eb::3c7:7
Thu, 22 Oct 2026 09:20:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	716 ms	2a09:bac5:47e5:25eb::3c7:7

⚙️ Protocol Parameter Specification

Verified protocol configuration attributes required for manual client profiles.

Host / Address 104.238.24.185

Port 443

Security Protocol TLS

Transport Type WS

SNI (Server Name Indication) snip.edgeoneai.cc.cd

Path /fdip=sstp://vpn:vpn@public-vpn-200.opengw.net:443fp=chrome

UUID 495c7195-85b8-498a-bf20-2ea9ce9175b5

TLS Fingerprint 16011854

🛡️

Direct TLS Encrypted Channel (WS)

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

SNI: Discreet Camouflage Host (Optimized for Evasion) Port 443 (Universal HTTPS Gateway) uTLS: 16011854 Custom Handshake (Active Cloaking)

Server 104.238.***.***:443 deploys industry-standard TLS cryptographic protection across WS, ensuring complete confidentiality across Tier-1 International Carrier.

Network Port Analysis: Selecting port 443 allows client connections to blend seamlessly with millions of simultaneous browser sessions across international border checkpoints.

SNI Masking Analysis (snip.edgeoneai.cc.cd): The obscure profile of snip.edgeoneai.cc.cd shields data streams from statistical traffic classification algorithms at international border gateways.

uTLS Handshake Security Analysis (16011854): Configuring 16011854 parameters delivers consistent connection anonymity across diverse intermediate carrier networks.

Client Handshake Masking (uTLS): Configuring 16011854 parameters delivers consistent connection anonymity across diverse intermediate carrier networks.

❓ Frequently Asked Questions for Node #16011854

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

Server 104.238.***.***:443 deploys industry-standard TLS cryptographic protection across WS, ensuring complete confidentiality across Tier-1 International Carrier. 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? ▼

Selecting port 443 allows client connections to blend seamlessly with millions of simultaneous browser sessions across international border checkpoints. The obscure profile of snip.edgeoneai.cc.cd shields data streams from statistical traffic classification algorithms at international border gateways. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.

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

1. Exit IP & Autonomous System (Identity) 🇰🇿 KZ

Public Exit IPv4: 2a09:bac5:47e5:25eb::3c7:7

Network (ASN / Org): AS13335 · Cloudflare, Inc.

BGP Prefix / Subnet: —

Node Location: Aktobe, Aktyubinskaya Oblast’ — 🇰🇿 KZ

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

Address Class: 🖥️ Hosting / Datacenter

Risk Score:

20 / 100 (95% conf)

Detection Flags:

hosting

Operator / Provider: Cloudflare, Inc.

3. Geolocation Consensus (IPv4)

Providers tallied: 20

🇰🇿 KZ Kazakhstan

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)	○ error	—	request failed	—
ChatGPT (app)	○ error	—	request failed	—
YouTube Premium	● available	—	—	2211 ms
Netflix	● available	🇰🇿 KZ	full catalogue	4082 ms
Claude	○ error	—	request failed	—
TikTok	● available	—	—	2498 ms
Gemini	● available	—	—	2402 ms
NotebookLM	● available	—	sign-in required	4887 ms

🤖 5. AI Model API Endpoints (Direct Probe)

AI Endpoint	Vendor	State	HTTP	Detail	RTT
OpenAI	OpenAI	● error	—	request failed	—
Anthropic	Anthropic	● error	—	request failed	—
Google Gemini	Google	● reachable	403	answered, credentials not supplied	2474 ms
DeepSeek	DeepSeek	● reachable	401	answered, credentials not supplied	2391 ms
Qwen (Singapore)	Alibaba	● reachable	401	answered, credentials not supplied	2904 ms
Qwen (Beijing)	Alibaba	● reachable	401	answered, credentials not supplied	3485 ms
Kimi / Moonshot	Moonshot	● reachable	401	answered, credentials not supplied	3900 ms
Zhipu GLM	Zhipu	● reachable	401	answered, credentials not supplied	3692 ms