Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Tue, 20 Oct 2026 09:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	673 ms	156.226.168.166
Tue, 20 Oct 2026 08:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1087 ms	156.226.168.166
Tue, 20 Oct 2026 07:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	693 ms	156.226.168.166
Tue, 20 Oct 2026 06:55:19 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	747 ms	156.226.168.166
Tue, 20 Oct 2026 05:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	935 ms	156.226.168.166
Tue, 20 Oct 2026 04:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	4129 ms	156.226.168.166
Tue, 20 Oct 2026 03:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	2401 ms	156.226.168.166
Tue, 20 Oct 2026 03:03:24 UTC	🇷🇺 RU Probe	🟢 HTTP 204 OK	993 ms	156.226.168.166
Tue, 20 Oct 2026 02:55:20 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	686 ms	156.226.168.166

⚙️ پارامترهای فنی پروتکل

Verified protocol configuration attributes required for manual client profiles.

آدرس هاست / سرور 206.238.238.148

پورت 2053

امنیت (Security) TLS

نوع انتقال (Transport) WS

مسیر (Path) /HK001

UUID f5f0babe-aea2-4f07-a1fc-3c9820253f49

اثر انگشت TLS 17184800

🛡️

Standard TLS Encryption (WS)

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

Port 2053 (Non-standard • High Risk) uTLS: 17184800 (Active)

Standard TLS encryption channel over WS. Provides robust end-to-end data security suitable for networks with standard censorship policies.

Network Port Analysis: Non-standard port (2053). Mobile operators and restricted whitelist networks frequently drop non-443/8443 traffic at the firewall layer.

uTLS Handshake Security Analysis (17184800): Emulating 17184800 TLS parameters to protect against passive fingerprinting.

Client Handshake Masking (uTLS): Emulating 17184800 TLS parameters to protect against passive fingerprinting.

❓ Frequently Asked Questions for Node #17184800

How does the TLS security profile protect my connection? ▼

Standard TLS encryption channel over WS. Provides robust end-to-end data security suitable for networks with standard censorship policies.

What client apps are recommended for this VLESS key? ▼

We recommend modern clients supporting VLESS Reality and Vision: Happ, Incy, v2RayTun, FlClashX, Koala Clash, Karing, and v2rayNG.

What should I do if this server stops responding? ▼

Free public keys are updated and re-verified automatically every 15-30 minutes. If this key goes offline, use our 1-click subscription link to always receive only fresh, currently responsive servers.

🌐 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 ⏱ 10.43s

1. Exit IP & Autonomous System (Identity) 🇭🇰 HK

Public Exit IPv4: 156.226.168.166

Network (ASN / Org): AS61112 · AKILE LTD

BGP Prefix / Subnet: —

Node Location: Hong Kong, Kowloon — 🇭🇰 HK

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

Address Class: 🖥️ Hosting / Datacenter

Risk Score:

20 / 100 (95% conf)

Detection Flags:

hosting

Operator / Provider: AKILE LTD

3. Geolocation Consensus (IPv4)

Providers tallied: 25

🇭🇰 HK Hong Kong

68% (17/25)

🇸🇨 SC Seychelles

32% (8/25)

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

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	● blocked	—	unsupported country	2206 ms
ChatGPT (app)	● blocked	—	blocked	2041 ms
YouTube Premium	● available	—	—	2437 ms
Netflix	● available	🇭🇰 HK	full catalogue	4028 ms
Claude	● blocked	🇭🇰 HK	not available in this region	2423 ms
TikTok	● available	—	—	3701 ms
Gemini	● available	—	—	2936 ms
NotebookLM	○ error	—	request failed	—

🤖 5. AI Model API Endpoints (Direct Probe)

AI Endpoint	Vendor	State	HTTP	Detail	RTT
OpenAI	OpenAI	● blocked	403	the API refused this region	2388 ms
Anthropic	Anthropic	● blocked	403	the API refused this region	2450 ms
Google Gemini	Google	● reachable	403	answered, credentials not supplied	2482 ms
DeepSeek	DeepSeek	● reachable	401	answered, credentials not supplied	2581 ms
Qwen (Singapore)	Alibaba	● reachable	401	answered, credentials not supplied	2584 ms
Qwen (Beijing)	Alibaba	● error	—	request failed	—
Kimi / Moonshot	Moonshot	● error	—	request failed	—
Zhipu GLM	Zhipu	● reachable	401	answered, credentials not supplied	1764 ms