🌐 VLESS Live Verified Node

LK (LK) — VLESS WS Node

Host: 104.17.71.206:8443 • Tested: 8:55:14 AM

Checked Latency 966 ms

Est. Bandwidth 0.0 Mbps

24h Uptime SLA 81%

Exit Consensus LK (Verified)

⚡ Direct Connection URI (VLESS • LK) Xray-core Verified • 81% Uptime

vless://c136a12c-4260-48a7-a1e6-fbda83a11045@104.17.71.206:8443?security=tls&type=ws&path=%2F&host=free.sahanwickramasinghe.me&packetEncoding=xudp&sni=free.sahanwickramasinghe.me&fp=chrome#%F0%9F%8C%90LK-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: 81% (21 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Wed, 21 Oct 2026 08:55:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	966 ms	62.197.156.21
Wed, 21 Oct 2026 07:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	759 ms	62.197.156.21
Wed, 21 Oct 2026 06:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1195 ms	62.197.156.21
Wed, 21 Oct 2026 05:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	614 ms	62.197.156.21
Wed, 21 Oct 2026 04:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	893 ms	62.197.156.21
Wed, 21 Oct 2026 03:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	671 ms	62.197.156.21
Wed, 21 Oct 2026 02:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	2186 ms	62.197.156.21
Wed, 21 Oct 2026 01:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	595 ms	62.197.156.21
Wed, 21 Oct 2026 00:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1215 ms	62.197.156.21
Tue, 20 Oct 2026 23:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	610 ms	62.197.156.21
Tue, 20 Oct 2026 22:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	625 ms	62.197.156.21
Tue, 20 Oct 2026 21:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	619 ms	62.197.156.21
Tue, 20 Oct 2026 17:55:20 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	62.197.156.21
Tue, 20 Oct 2026 16:25:22 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	62.197.156.21
Tue, 20 Oct 2026 15:55:20 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	62.197.156.21

⚙️ Protocol Parameter Specification

Verified protocol configuration attributes required for manual client profiles.

Host / Address 104.17.71.206

Port 8443

Security Protocol TLS

Transport Type WS

SNI (Server Name Indication) free.sahanwickramasinghe.me

Path /

UUID c136a12c-4260-48a7-a1e6-fbda83a11045

TLS Fingerprint 16656364

🛡️

Direct TLS Encrypted Channel (WS)

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

SNI: Discreet Camouflage Host (Optimized for Evasion) Port 8443 (Alternative Web Channel) uTLS: 16656364 Custom Handshake (Active Cloaking)

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

Network Port Analysis: Port 8443 serves as a globally documented secondary HTTPS channel, reliably handling cloud traffic across international transit backbones.

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

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

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

❓ Frequently Asked Questions for Node #16656364

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

Protected by standard TLS encryption over WS, endpoint 104.17.***.***:8443 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 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 8443 and domain masking perform under heavy censorship in Iran and China? ▼

Port 8443 serves as a globally documented secondary HTTPS channel, reliably handling cloud traffic across international transit backbones. Camouflaged behind neutral destination free.sahanwickramasinghe.me, 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 (104.17.***.***) 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 ⏱ 12.71s

1. Exit IP & Autonomous System (Identity) 🇱🇰 LK

Public Exit IPv4: 62.197.156.21

Network (ASN / Org): AS209854 · Cyberzone S.A.

BGP Prefix / Subnet: —

Node Location: Dambulla, Central Province — 🇱🇰 LK

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

Address Class: 🖥️ Hosting / Datacenter

Risk Score:

20 / 100 (95% conf)

Detection Flags:

hosting

Operator / Provider: Cyberzone S.A.

3. Geolocation Consensus (IPv4)

Providers tallied: 23

🇱🇰 LK Sri Lanka

87% (20/23)

🇭🇰 HK Hong Kong

9% (2/23)

🇸🇬 SG Singapore

4% (1/23)

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

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	● available	—	—	1796 ms
ChatGPT (app)	● available	—	—	2698 ms
YouTube Premium	○ error	—	request failed	—
Netflix	● available	🇱🇰 LK	full catalogue	4606 ms
Claude	○ error	🇸🇬 SG	Cloudflare challenged the request, so availability was never tested	417 ms
TikTok	● available	—	—	2085 ms
Gemini	○ error	—	unexpected HTTP 429	3785 ms
NotebookLM	● available	—	sign-in required	4031 ms

🤖 5. AI Model API Endpoints (Direct Probe)

AI Endpoint	Vendor	State	HTTP	Detail	RTT
OpenAI	OpenAI	● reachable	401	answered, credentials not supplied	2426 ms
Anthropic	Anthropic	● error	—	request failed	—
Google Gemini	Google	● reachable	403	answered, credentials not supplied	1702 ms
DeepSeek	DeepSeek	● reachable	401	answered, credentials not supplied	1997 ms
Qwen (Singapore)	Alibaba	● reachable	401	answered, credentials not supplied	1901 ms
Qwen (Beijing)	Alibaba	● error	—	request failed	—
Kimi / Moonshot	Moonshot	● error	—	request failed	—
Zhipu GLM	Zhipu	● reachable	401	answered, credentials not supplied	2290 ms