🇯🇵 VLESS Live Verified Node

Japan (JP) — VLESS WS Node

Host: 104.24.0.1:443 • Tested: 7:12:04 PM

Checked Latency 1047 ms

Est. Bandwidth 0.0 Mbps

24h Uptime SLA 95%

Exit Consensus JP (Verified)

⚡ Direct Connection URI (VLESS • Japan) Xray-core Verified • 95% Uptime

vless://4e4f1f70-5e56-4a76-bb9d-db087f4690c4@104.24.0.1:443?alpn=http%2F1.1&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

1. Direct Single Key Copy the URI above into Happ, Incy, v2RayTun, or v2rayNG. Re-tested every 30 min.

2. Free Auto-Updating Subscription Auto-sync fresh working nodes every 30 min: https://freevpnkeys.com/sub/happ

3. Private 10 Gbps Anti-DPI Multi-Key Need zero congestion, 10 Gbps speed & strict ISP whitelist bypass? Get a private key in Telegram bot @yavpn_robot (~$0.05/day).

⚡ 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:

Happ ↗

iOS / Android / PC / Mac

v2RayTun ↗

Android / iOS / PC / Mac

Incy ↗

iOS / Android / PC / Mac

v2rayNG ↗

Android

FlClashX / Clash ↗

Windows / macOS / Android

Karing / sing-box ↗

Core / GUI

📊 Recent Verification History

Automated multi-point health probes through Xray-core / libxray (verified every 30 minutes)

24h SLA: 95% (20 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Sun, 25 Oct 2026 19:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1047 ms	158.101.158.101
Sun, 25 Oct 2026 18:42:04 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	158.101.158.101
Sun, 25 Oct 2026 17:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	817 ms	158.101.158.101
Sun, 25 Oct 2026 16:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1111 ms	158.101.158.101
Sun, 25 Oct 2026 15:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1983 ms	158.101.158.101
Sun, 25 Oct 2026 14:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1109 ms	158.101.158.101
Sun, 25 Oct 2026 13:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	996 ms	158.101.158.101
Sun, 25 Oct 2026 12:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1339 ms	158.101.158.101
Sun, 25 Oct 2026 11:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1111 ms	158.101.158.101
Sun, 25 Oct 2026 10:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1547 ms	158.101.158.101
Sun, 25 Oct 2026 09:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1338 ms	158.101.158.101
Sun, 25 Oct 2026 08:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1102 ms	158.101.158.101
Sun, 25 Oct 2026 07:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1895 ms	158.101.158.101
Sun, 25 Oct 2026 06:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1741 ms	158.101.158.101
Sun, 25 Oct 2026 05:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1349 ms	158.101.158.101

⚙️ Protocol Parameter Specification

Verified protocol configuration attributes required for manual client profiles.

Host / Address 104.24.0.1

Port 443

Security Protocol TLS

Transport Type WS

SNI (Server Name Indication) jp3.yohototo.top

Path /tyxyws

UUID 4e4f1f70-5e56-4a76-bb9d-db087f4690c4

TLS Fingerprint 19459986

🛡️

Direct TLS Encrypted Channel (WS)

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

SNI: Discreet Camouflage Host (Optimized for Evasion) Port 443 (Universal HTTPS Gateway) uTLS: 19459986 Custom Handshake (Active Cloaking)

Encrypted channel with clean TLS negotiation on host 104.24.***.***, safeguarding packets from third-party interception and data tampering.

Network Port Analysis: Port 443 delivers unmatched survivability across enterprise networks, public university campuses, and mobile data providers.

SNI Masking Analysis (jp3.yohototo.top): Employing low-traffic property jp3.yohototo.top drastically minimizes the probability of synthetic replay attacks by the Great Firewall.

uTLS Handshake Security Analysis (19459986): The 19459986 configuration helps packets blend smoothly into aggregate background web communications.

Client Handshake Masking (uTLS): The 19459986 configuration helps packets blend smoothly into aggregate background web communications.

❓ Frequently Asked Questions for Node #19459986

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.

GeoCheck v1.4 ⏱ 18.90s

1. Exit IP & Autonomous System (Identity) 🇯🇵 JP

Public Exit IPv4: 158.101.158.101

Network (ASN / Org): AS31898 · Oracle Corporation

BGP Prefix / Subnet: —

Node Location: Inzai (Otsuka), Chiba — 🇯🇵 JP

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

Address Class: 🖥️ Hosting / Datacenter

Risk Score:

20 / 100 (95% conf)

Detection Flags:

hosting

Operator / Provider: Oracle Corporation

3. Geolocation Consensus (IPv4)

Providers tallied: 18

🇯🇵 JP Japan

100% (18/18)

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

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	● available	—	—	2206 ms
ChatGPT (app)	● available	—	—	3512 ms
YouTube Premium	● available	—	—	2462 ms
Netflix	● available	🇯🇵 JP	full catalogue	3496 ms
Claude	○ error	🇯🇵 JP	Cloudflare challenged the request, so availability was never tested	178 ms
TikTok	○ error	—	request failed	—
Gemini	○ error	—	request failed	—
NotebookLM	○ error	—	request failed	—

🤖 5. AI Model API Endpoints (Direct Probe)

AI Endpoint	Vendor	State	HTTP	Detail	RTT
OpenAI	OpenAI	● reachable	401	answered, credentials not supplied	3416 ms
Anthropic	Anthropic	● reachable	401	answered, credentials not supplied	2033 ms
Google Gemini	Google	● error	—	request failed	—
DeepSeek	DeepSeek	● reachable	401	answered, credentials not supplied	2372 ms
Qwen (Singapore)	Alibaba	● error	—	request failed	—
Qwen (Beijing)	Alibaba	● error	—	request failed	—
Kimi / Moonshot	Moonshot	● reachable	401	answered, credentials not supplied	3608 ms
Zhipu GLM	Zhipu	● error	—	request failed	—