🇺🇸 VLESS Live Verified Node

United States (US) — VLESS WS Node

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

Checked Latency 68 ms

Est. Bandwidth 0.0 Mbps

24h Uptime SLA 96%

Exit Consensus US (Verified)

⚡ Direct Connection URI (VLESS • United States) Xray-core Verified • 96% Uptime

vless://495c7195-85b8-498a-bf20-2ea9ce9175b5@104.18.89.52:443?encryption=none&security=tls&type=ws&host=snip.edgeoneai.cc.cd&path=%2Ffdip%3Dsstp%3A%2F%2Fvpn%3Avpn%40public-vpn-200.opengw.net%3A443fp%3Dchrome&sni=snip.edgeoneai.cc.cd#%F0%9F%87%BA%F0%9F%87%B8US-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: 96% (25 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Thu, 22 Oct 2026 21:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	68 ms	2a09:bac5:6d75:e78::171:2c0
Thu, 22 Oct 2026 20:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	50 ms	2a09:bac5:6d75:290f::417:75
Thu, 22 Oct 2026 19:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	502 ms	2a09:bac5:6d75:2678::3d5:42
Thu, 22 Oct 2026 18:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	49 ms	2a09:bac5:6d75:aa::11:1fa
Thu, 22 Oct 2026 17:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	148 ms	2a09:bac5:6d75:2678::3d5:42
Thu, 22 Oct 2026 16:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	353 ms	2a09:bac5:6d75:290f::417:75
Thu, 22 Oct 2026 15:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	274 ms	2a09:bac5:6d75:aa::11:1fa
Thu, 22 Oct 2026 14:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	134 ms	2a09:bac5:6d75:290f::417:75
Thu, 22 Oct 2026 13:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	389 ms	2a09:bac5:6d75:290f::417:75
Thu, 22 Oct 2026 12:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	351 ms	2a09:bac5:6d75:290f::417:75
Thu, 22 Oct 2026 11:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	593 ms	2a09:bac5:6d75:aa::11:1fa
Thu, 22 Oct 2026 10:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	158 ms	2a09:bac5:6d75:e6e::170:c6
Thu, 22 Oct 2026 09:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	67 ms	2a09:bac5:6d75:e6e::170:c6
Thu, 22 Oct 2026 08:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	350 ms	2a09:bac5:6d75:2678::3d5:42
Thu, 22 Oct 2026 07:50:47 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	67 ms	2a09:bac5:6d75:290f::417:75

⚙️ Protocol Parameter Specification

Verified protocol configuration attributes required for manual client profiles.

Host / Address 104.18.89.52

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 17891989

🛡️

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: 17891989 Custom Handshake (Active Cloaking)

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

Network Port Analysis: Port 443 functions as the bedrock gateway for encrypted web communications, making discriminatory packet drops virtually impossible without crippling nationwide commerce.

SNI Masking Analysis (snip.edgeoneai.cc.cd): Camouflaged behind neutral destination snip.edgeoneai.cc.cd, this node avoids heuristic scrutiny and active probe lists maintained by authoritarian firewalls.

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

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

❓ Frequently Asked Questions for Node #17891989

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

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

Port 443 functions as the bedrock gateway for encrypted web communications, making discriminatory packet drops virtually impossible without crippling nationwide commerce. Camouflaged behind neutral destination snip.edgeoneai.cc.cd, 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.18.***.***) 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 ⏱ 1.94s

1. Exit IP & Autonomous System (Identity) 🇺🇸 US

Public Exit IPv4: 2a09:bac5:6d75:e78::171:2c0

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

BGP Prefix / Subnet: —

Node Location: Miami, Florida — 🇺🇸 US

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

🇺🇸 US United States

100% (20/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	—	—	216 ms
Netflix	● available	🇺🇸 US	full catalogue	740 ms
Claude	○ error	—	request failed	—
TikTok	● available	—	—	481 ms
Gemini	● available	—	—	880 ms
NotebookLM	● available	—	sign-in required	327 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	151 ms
DeepSeek	DeepSeek	● reachable	401	answered, credentials not supplied	453 ms
Qwen (Singapore)	Alibaba	● reachable	401	answered, credentials not supplied	923 ms
Qwen (Beijing)	Alibaba	● reachable	401	answered, credentials not supplied	1081 ms
Kimi / Moonshot	Moonshot	● reachable	401	answered, credentials not supplied	1234 ms
Zhipu GLM	Zhipu	● reachable	401	answered, credentials not supplied	715 ms