节点已停止响应
此节点已无响应（经拨测确认）。推荐使用以下可用备选节点：
United States (US) — TROJAN WS Node
Host: 188.114.98.0:443 • Tested: 3:51:43 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 |
|---|---|---|---|---|
| Wed, 21 Oct 2026 16:07:46 UTC | 🇺🇸 US Main | 🔴 Failed (timeout_or_captive_portal) | — | 2602:f9f3:1:0:5054:ff:fe4c:4f10 |
| Wed, 21 Oct 2026 15:51:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 503 ms | 2602:f9f3:1:0:5054:ff:fe4c:4f10 |
| Wed, 21 Oct 2026 15:21:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 604 ms | 2602:f9f3:1:0:5054:ff:fe4c:4f10 |
| Wed, 21 Oct 2026 14:51:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 482 ms | 2602:f9f3:1:0:5054:ff:fe4c:4f10 |
| Wed, 21 Oct 2026 14:21:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 628 ms | 2602:f9f3:1:0:5054:ff:fe4c:4f10 |
| Wed, 21 Oct 2026 13:51:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1047 ms | 2602:f9f3:1:0:5054:ff:fe4c:4f10 |
| Wed, 21 Oct 2026 13:21:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1032 ms | 2602:f9f3:1:0:5054:ff:fe4c:4f10 |
| Wed, 21 Oct 2026 12:51:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 640 ms | 2602:f9f3:1:0:5054:ff:fe4c:4f10 |
| Wed, 21 Oct 2026 12:21:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 674 ms | 2602:f9f3:1:0:5054:ff:fe4c:4f10 |
| Wed, 21 Oct 2026 11:51:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 553 ms | 2602:f9f3:1:0:5054:ff:fe4c:4f10 |
| Wed, 21 Oct 2026 11:21:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 643 ms | 2602:f9f3:1:0:5054:ff:fe4c:4f10 |
| Wed, 21 Oct 2026 10:51:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 996 ms | 2602:f9f3:1:0:5054:ff:fe4c:4f10 |
| Wed, 21 Oct 2026 10:21:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 522 ms | 2602:f9f3:1:0:5054:ff:fe4c:4f10 |
| Wed, 21 Oct 2026 09:51:43 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1448 ms | 2602:f9f3:1:0:5054:ff:fe4c:4f10 |
| Wed, 21 Oct 2026 09:13:40 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 550 ms | 2602:f9f3:1:0:5054:ff:fe4c:4f10 |
⚙️ 协议核心技术参数
Verified protocol configuration attributes required for manual client profiles.
Direct TLS Encrypted Channel (WS)
Cryptographic resistance profile and Deep Packet Inspection (DPI) evasion analysis
Protected by standard TLS encryption over WS, endpoint 188.114.***.***:443 guarantees private, uncompromised transit through international corridors.
nat3.xxai.dpdns.org): Utilizing discreet domain nat3.xxai.dpdns.org enables the proxy tunnel to navigate Iranian and Chinese inspection hardware without triggering suspicion. ❓ Frequently Asked Questions for Node #13812311
How does node #N bypass state-level censorship and firewall restrictions? ▼
Protected by standard TLS encryption over WS, endpoint 188.114.***.***: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 TROJAN 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? ▼
Traversing egress routes through port 443 provides maximum reliability since international border firewalls allow encrypted web handshakes unrestricted passage. Utilizing discreet domain nat3.xxai.dpdns.org enables the proxy tunnel to navigate Iranian and Chinese inspection hardware without triggering suspicion. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.
What steps should I take if node #N (188.114.***.***) 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: 7🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)
| Service | Status | Region | Technical Detail | RTT |
|---|---|---|---|---|
| ChatGPT (web) | ○ untested | — | awaiting tunnel probe | — |
| Claude (Anthropic) | ○ untested | — | awaiting tunnel probe | — |
| Google Gemini | ○ untested | — | awaiting tunnel probe | — |
| Google NotebookLM | ○ untested | — | awaiting tunnel probe | — |
| YouTube Premium | ○ untested | — | awaiting tunnel probe | — |
| Netflix | ○ untested | — | awaiting tunnel probe | — |
| TikTok | ○ untested | — | awaiting tunnel probe | — |
🗺️ 6. GeoIP Databases (16 Independent Providers)
🔄 客户端自动更新订阅
一键订阅所有 United States 地区 TROJAN 协议在线节点，支持后台自动同步：
✨ 同类可用节点推荐
同国家及同协议的高分备选可用节点：