🇯🇵 WEBPROXY Live Verified Node

Japan (JP) — WEBPROXY WS Node

Host: tgeller.shuzizhaimin.com:443 • Tested: 12:25:20 PM

✈️ Open in Telegram
Checked Latency 545 ms
Est. Bandwidth 0.0 Mbps
24h Uptime SLA 77.8%
Exit Consensus JP (Verified)

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

24h SLA: 77.8% (27 probes)
Probe Time Probe Node Verdict Latency (RTT) Exit IP
Tue, 20 Oct 2026 12:25:20 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 545 ms 54.168.76.14
Tue, 20 Oct 2026 11:25:21 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 486 ms 54.168.76.14
Tue, 20 Oct 2026 10:25:20 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 483 ms 54.168.76.14
Tue, 20 Oct 2026 09:25:20 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 507 ms 54.168.76.14
Tue, 20 Oct 2026 08:25:20 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 538 ms 54.168.76.14
Tue, 20 Oct 2026 07:25:20 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 492 ms 54.168.76.14
Tue, 20 Oct 2026 06:25:20 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 488 ms 54.168.76.14
Tue, 20 Oct 2026 05:55:20 UTC 🇺🇸 US Main 🔴 Failed (unreachable) — 54.168.76.14
Tue, 20 Oct 2026 04:55:20 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 551 ms 54.168.76.14
Tue, 20 Oct 2026 03:55:20 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 505 ms 54.168.76.14
Tue, 20 Oct 2026 02:55:20 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 482 ms 54.168.76.14
Tue, 20 Oct 2026 01:55:20 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 508 ms 54.168.76.14
Tue, 20 Oct 2026 01:25:20 UTC 🇺🇸 US Main 🔴 Failed (unreachable) — 54.168.76.14
Tue, 20 Oct 2026 00:25:20 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 541 ms 54.168.76.14
Mon, 19 Oct 2026 23:55:20 UTC 🇺🇸 US Main 🔴 Failed (unreachable) — 54.168.76.14

⚙️ Protocol Parameter Specification

Verified protocol configuration attributes required for manual client profiles.

Host / Address tgeller.shuzizhaimin.com
Port 443
Security Protocol TLS
Transport Type WS
SNI (Server Name Indication) tgeller.shuzizhaimin.com
Secret 548593a9c0688f4f7d9d57377897d964
🛡️

Telegram WEB-Proxy (HTTPS / WebSocket Bridge)

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

SNI: Direct Match (Standard TLS) Port 443 (Standard HTTPS) uTLS: Telegram WebView (Native HTTPS)

Native Telegram WEB-Proxy (tproxy-server / telemt) operating over standard HTTPS port 443 with HMAC-SHA256 bridge authentication and WebSocket transport.

Network Port Analysis: Port 443 is the universal standard for secure HTTPS traffic. Firewalls and ISPs cannot block it without disrupting regular web access.
SNI Masking Analysis (tgeller.shuzizhaimin.com): SNI matches target server hostname — clean standard TLS handshake with no cross-domain mismatch.
uTLS Handshake Security Analysis (Native Telegram WebView): Native Telegram WEB-Proxy uses the authentic system WebView HTTPS/WebSocket TLS stack on port 443, indistinguishable from regular web traffic.
Client Handshake Masking (uTLS): Native Telegram WEB-Proxy uses the authentic system WebView HTTPS/WebSocket TLS stack on port 443, indistinguishable from regular web traffic.

❓ Frequently Asked Questions for Node #14951338

How does the TLS security profile protect my connection? ▼

Native Telegram WEB-Proxy (tproxy-server / telemt) operating over standard HTTPS port 443 with HMAC-SHA256 bridge authentication and WebSocket transport.

What client apps are recommended for this WEBPROXY 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.

GeoCheck v1.4 ⏱ 0.63s
1. Exit IP & Autonomous System (Identity) 🇯🇵 JP
Public Exit IPv4: 54.168.76.14
Network (ASN / Org): AS16509 · Amazon.com, Inc.
BGP Prefix / Subnet: —
Node Location: Shibuya, Tokyo — 🇯🇵 JP
2. IP Address Reputation (proxycheck.io v3) Hosting
Address Class: 🖥️ Hosting / Datacenter
Risk Score:
20 / 100 (95% conf)
Detection Flags:
hosting
Operator / Provider: Amazon.com, Inc.

3. Geolocation Consensus (IPv4)

Providers tallied: 10
🇯🇵 JP Japan
100% (10/10)

🔓 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)

cloudflare.com 🇯🇵 JP
iplocation.com 🇯🇵 JP
maxmind.com —
rdap.db.ripe.net —
ipinfo.io —
ipregistry.co 🇯🇵 JP
ipapi.co 🇯🇵 JP
country.is 🇯🇵 JP
geoapify.com 🇯🇵 JP
geojs.io 🇯🇵 JP
ipapi.is 🇯🇵 JP
ipbase.com —
ipquery.io 🇯🇵 JP
ipwho.is —
ip-api.com 🇯🇵 JP
2ip.io —

🔄 Auto-Updating App Subscriptions

Subscribe to all active verified Japan WEBPROXY nodes with automatic background updates:

Unified Smart Subscription Auto-Detect
Clash / mihomo YAML Subscription Clash.Meta

✨ Related Working Nodes

Top verified alternatives with matching protocol and country:

📱

Scan Node QR Code

Node QR Code

Scan with Happ, v2rayNG, Streisand, or Hiddify camera scanner to import node.

🛡️ ISP Blocking VPN? → Try @yavpn_robot
✓ Key copied to clipboard

💎 Private Multi-Key (5 RUB/day)

Get a dedicated multi-key (5 RUB/day) with carrier whitelist bypass in @yavpn_robot.