KR (KR) — VLESS TCP Node
Host: 158.247.199.164:443 • Tested: 6:55:20 PM
⚡ 浏览器端实时延迟测速
直接从您的当前浏览器向该节点发起真实 RTT 往返时延测算。
👍 Community Health Rating
Does this server currently connect and route traffic from your location?
🚀 一键导入客户端
直接点击下方按钮快速添加到主流代理软件:
📊 Recent Verification History
Automated multi-point health probes through Xray-core / libxray (verified every 30 minutes)
| Probe Time | Probe Node | Verdict | Latency (RTT) | Exit IP |
|---|---|---|---|---|
| Tue, 20 Oct 2026 22:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 2401:c080:1c01:e72:5400:6ff:fecf:2848 |
| Tue, 20 Oct 2026 22:25:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 2401:c080:1c01:e72:5400:6ff:fecf:2848 |
| Tue, 20 Oct 2026 21:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 2401:c080:1c01:e72:5400:6ff:fecf:2848 |
| Tue, 20 Oct 2026 21:25:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 2401:c080:1c01:e72:5400:6ff:fecf:2848 |
| Tue, 20 Oct 2026 20:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 2401:c080:1c01:e72:5400:6ff:fecf:2848 |
| Tue, 20 Oct 2026 20:25:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 2401:c080:1c01:e72:5400:6ff:fecf:2848 |
| Tue, 20 Oct 2026 19:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 2401:c080:1c01:e72:5400:6ff:fecf:2848 |
| Tue, 20 Oct 2026 18:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 751 ms | 2401:c080:1c01:e72:5400:6ff:fecf:2848 |
| Tue, 20 Oct 2026 17:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 709 ms | 64.176.231.183 |
| Tue, 20 Oct 2026 16:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 543 ms | 2401:c080:1c01:e72:5400:6ff:fecf:2848 |
| Tue, 20 Oct 2026 16:06:11 UTC | 🇷🇺 RU Probe | 🔴 Failed (tspu_timeout) | — | 2401:c080:1c01:e72:5400:6ff:fecf:2848 |
| Tue, 20 Oct 2026 15:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 520 ms | 64.176.231.183 |
| Tue, 20 Oct 2026 14:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 680 ms | 2401:c080:1c01:e72:5400:6ff:fecf:2848 |
| Tue, 20 Oct 2026 13:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 538 ms | 2401:c080:1c01:e72:5400:6ff:fecf:2848 |
| Tue, 20 Oct 2026 12:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1294 ms | 2401:c080:1c01:e72:5400:6ff:fecf:2848 |
⚙️ 协议核心技术参数
Verified protocol configuration attributes required for manual client profiles.
Zero-Signature Reality Relay (RAW / TCP)
Cryptographic resistance profile and Deep Packet Inspection (DPI) evasion analysis
Configured with advanced Reality evasion protocols over RAW / TCP, endpoint 158.247.***.***:443 ensures sustained packet throughput through aggressive firewalls.
www.apple.com): Employing prominent hostname www.apple.com elevates detection probability because national firewalls closely monitor inbound cloud traffic distributions. ❓ Frequently Asked Questions for Node #17203194
How does node #N bypass state-level censorship and firewall restrictions? ▼
Configured with advanced Reality evasion protocols over RAW / TCP, endpoint 158.247.***.***: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 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? ▼
Firewall gateways in Iran and China permit port 443 unconditionally to avoid breaking domestic banking portals and commercial digital services. Employing prominent hostname www.apple.com elevates detection probability because national firewalls closely monitor inbound cloud traffic distributions. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.
What steps should I take if node #N (158.247.***.***) 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.
3. Geolocation Consensus (IPv4)
Providers tallied: 24🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)
| Service | Status | Region | Technical Detail | RTT |
|---|---|---|---|---|
| ChatGPT (web) | ● available | — | — | 1809 ms |
| ChatGPT (app) | ● available | — | — | 2222 ms |
| YouTube Premium | ○ error | — | request failed | — |
| Netflix | ○ error | — | request failed | 2098 ms |
| Claude | ○ error | 🇰🇷 KR | Cloudflare challenged the request, so availability was never tested | 1080 ms |
| TikTok | ● available | — | — | 4421 ms |
| Gemini | ● available | — | — | 1803 ms |
| NotebookLM | ● available | — | sign-in required | 2835 ms |
🤖 5. AI Model API Endpoints (Direct Probe)
| AI Endpoint | Vendor | State | HTTP | Detail | RTT |
|---|---|---|---|---|---|
| OpenAI | OpenAI | ● reachable | 401 | answered, credentials not supplied | 1477 ms |
| Anthropic | Anthropic | ● reachable | 401 | answered, credentials not supplied | 1409 ms |
| Google Gemini | ● reachable | 403 | answered, credentials not supplied | 2296 ms | |
| DeepSeek | DeepSeek | ● reachable | 401 | answered, credentials not supplied | 2412 ms |
| Qwen (Singapore) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 1507 ms |
| Qwen (Beijing) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 1885 ms |
| Kimi / Moonshot | Moonshot | ● error | — | request failed | — |
| Zhipu GLM | Zhipu | ● reachable | 401 | answered, credentials not supplied | 2442 ms |
🗺️ 6. GeoIP Databases (16 Independent Providers)
7. Popular Services Geo Detection (21 probes)
8. CDN Edge Location (PoP)
🔄 客户端自动更新订阅
一键订阅所有 KR 地区 VLESS 协议在线节点,支持后台自动同步:
✨ 同类可用节点推荐
同国家及同协议的高分备选可用节点: