Node No Longer Responding
This server is no longer responding (verified by our checker). Recommended working alternatives:
IN (IN) — VLESS TCP Node
Host: 5.253.28.224:40443 • Tested: 2:55:20 PM
⚡ 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:
📊 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 15:55:20 UTC | 🇺🇸 US Main | 🔴 Failed (unreachable) | — | 5.253.42.164 |
| Tue, 20 Oct 2026 14:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 2739 ms | 5.253.42.164 |
| Tue, 20 Oct 2026 13:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 2648 ms | 5.253.42.164 |
| Tue, 20 Oct 2026 12:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1872 ms | 5.253.42.164 |
| Tue, 20 Oct 2026 11:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 2415 ms | 5.253.42.164 |
| Tue, 20 Oct 2026 10:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 2526 ms | 5.253.42.164 |
| Tue, 20 Oct 2026 09:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 2596 ms | 5.253.42.164 |
| Tue, 20 Oct 2026 08:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 3305 ms | 5.253.42.164 |
| Tue, 20 Oct 2026 07:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1338 ms | 5.253.42.164 |
| Tue, 20 Oct 2026 06:55:19 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 2235 ms | 5.253.42.164 |
| Tue, 20 Oct 2026 05:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1108 ms | 5.253.42.164 |
| Tue, 20 Oct 2026 04:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 561 ms | 5.253.42.164 |
| Tue, 20 Oct 2026 03:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 747 ms | 5.253.42.164 |
| Tue, 20 Oct 2026 02:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 681 ms | 5.253.42.164 |
| Tue, 20 Oct 2026 01:55:20 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 898 ms | 5.253.42.164 |
⚙️ Protocol Parameter Specification
Verified protocol configuration attributes required for manual client profiles.
Xray REALITY over RAW / TCP
Cryptographic resistance profile and Deep Packet Inspection (DPI) evasion analysis
This node utilizes RAW / TCP transport with Xray REALITY. It applies TLS-in-TLS masking to eliminate identifiable proxy signatures, making the handshake look like a legitimate browser connection.
deepl.com): Masked under a low-profile external domain (deepl.com), which effectively reduces detection risk from automated DPI heuristics. ❓ Frequently Asked Questions for Node #13779169
How does the REALITY security profile protect my connection? ▼
This node utilizes RAW / TCP transport with Xray REALITY. It applies TLS-in-TLS masking to eliminate identifiable proxy signatures, making the handshake look like a legitimate browser connection.
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.
3. Geolocation Consensus (IPv4)
Providers tallied: 10🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)
| Service | Status | Region | Technical Detail | RTT |
|---|---|---|---|---|
| ChatGPT (web) | ● available | — | — | 3351 ms |
| ChatGPT (app) | ● available | — | — | 4964 ms |
| YouTube Premium | ● available | — | — | 4468 ms |
| Netflix | ○ error | — | request failed | 6045 ms |
| Claude | ○ error | 🇮🇳 IN | Cloudflare challenged the request, so availability was never tested | 1431 ms |
| TikTok | ○ error | — | request failed | — |
| Gemini | ○ error | — | unexpected HTTP 403 | 3870 ms |
| NotebookLM | ○ error | — | unexpected HTTP 403 | 3479 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 | ● reachable | 403 | answered, credentials not supplied | 3553 ms | |
| DeepSeek | DeepSeek | ● error | — | request failed | — |
| Qwen (Singapore) | Alibaba | ● error | — | request failed | — |
| Qwen (Beijing) | Alibaba | ● error | — | request failed | — |
| Kimi / Moonshot | Moonshot | ● error | — | request failed | — |
| Zhipu GLM | Zhipu | ● error | — | request failed | — |
🗺️ 6. GeoIP Databases (16 Independent Providers)
7. Popular Services Geo Detection (21 probes)
8. CDN Edge Location (PoP)
🔄 Auto-Updating App Subscriptions
Subscribe to all active verified IN VLESS nodes with automatic background updates:
✨ Related Working Nodes
Top verified alternatives with matching protocol and country: