Japan (JP) — VLESS WS Node
Host: 104.24.31.89:443 • Tested: 1:20:47 AM
vless://4e4f1f70-5e56-4a76-bb9d-db087f4690c4@104.24.31.89:443?fp=chrome&host=jp3.yohototo.top&path=%2Ftyxyws&security=tls&sni=jp3.yohototo.top&type=ws#%F0%9F%87%AF%F0%9F%87%B5JP-freevpnkeys.com-TG-%40yavpn_robot https://freevpnkeys.com/sub/happ ⚡ 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 |
|---|---|---|---|---|
| Sat, 24 Oct 2026 01:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 502 ms | 158.101.158.101 |
| Sat, 24 Oct 2026 00:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1060 ms | 158.101.158.101 |
| Fri, 23 Oct 2026 23:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1534 ms | 158.101.158.101 |
| Fri, 23 Oct 2026 22:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 2016 ms | 158.101.158.101 |
| Fri, 23 Oct 2026 21:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1009 ms | 158.101.158.101 |
| Fri, 23 Oct 2026 20:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 2864 ms | 158.101.158.101 |
| Fri, 23 Oct 2026 19:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1094 ms | 158.101.158.101 |
| Fri, 23 Oct 2026 18:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1538 ms | 158.101.158.101 |
| Fri, 23 Oct 2026 17:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 2253 ms | 158.101.158.101 |
| Fri, 23 Oct 2026 16:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1809 ms | 158.101.158.101 |
| Fri, 23 Oct 2026 15:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1455 ms | 158.101.158.101 |
| Fri, 23 Oct 2026 14:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1696 ms | 158.101.158.101 |
| Fri, 23 Oct 2026 13:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 801 ms | 158.101.158.101 |
| Fri, 23 Oct 2026 12:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 1096 ms | 158.101.158.101 |
| Fri, 23 Oct 2026 11:20:47 UTC | 🇺🇸 US Main | 🟢 HTTP 204 OK | 2094 ms | 158.101.158.101 |
⚙️ Protocol Parameter Specification
Verified protocol configuration attributes required for manual client profiles.
Direct TLS Encrypted Channel (WS)
Cryptographic resistance profile and Deep Packet Inspection (DPI) evasion analysis
Encrypted channel with clean TLS negotiation on host 104.24.***.***, safeguarding packets from third-party interception and data tampering.
jp3.yohototo.top): Employing low-traffic property jp3.yohototo.top drastically minimizes the probability of synthetic replay attacks by the Great Firewall. ❓ Frequently Asked Questions for Node #13785340
How does node #N bypass state-level censorship and firewall restrictions? ▼
Encrypted channel with clean TLS negotiation on host 104.24.***.***, safeguarding packets from third-party interception and data tampering. 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 delivers unmatched survivability across enterprise networks, public university campuses, and mobile data providers. Employing low-traffic property jp3.yohototo.top drastically minimizes the probability of synthetic replay attacks by the Great Firewall. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.
What steps should I take if node #N (104.24.***.***) 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: 18🔓 4. Service Availability & Anti-Bot Checks (Stash Checks)
| Service | Status | Region | Technical Detail | RTT |
|---|---|---|---|---|
| ChatGPT (web) | ● available | — | — | 2074 ms |
| ChatGPT (app) | ● available | — | — | 2508 ms |
| YouTube Premium | ○ error | — | request failed | — |
| Netflix | ● available | 🇯🇵 JP | full catalogue | 6007 ms |
| Claude | ○ error | 🇯🇵 JP | Cloudflare challenged the request, so availability was never tested | 2401 ms |
| TikTok | ● available | — | — | 4669 ms |
| Gemini | ○ error | — | request failed | — |
| NotebookLM | ● available | — | sign-in required | 5732 ms |
🤖 5. AI Model API Endpoints (Direct Probe)
| AI Endpoint | Vendor | State | HTTP | Detail | RTT |
|---|---|---|---|---|---|
| OpenAI | OpenAI | ● reachable | 401 | answered, credentials not supplied | 1602 ms |
| Anthropic | Anthropic | ● reachable | 401 | answered, credentials not supplied | 1604 ms |
| Google Gemini | ● reachable | 403 | answered, credentials not supplied | 1603 ms | |
| DeepSeek | DeepSeek | ● reachable | 401 | answered, credentials not supplied | 2214 ms |
| Qwen (Singapore) | Alibaba | ● error | — | request failed | — |
| Qwen (Beijing) | Alibaba | ● reachable | 401 | answered, credentials not supplied | 1686 ms |
| Kimi / Moonshot | Moonshot | ● reachable | 401 | answered, credentials not supplied | 3798 ms |
| Zhipu GLM | Zhipu | ● reachable | 401 | answered, credentials not supplied | 2568 ms |
🗺️ 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 Japan VLESS nodes with automatic background updates:
✨ Related Working Nodes
Top verified alternatives with matching protocol and country: