Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Mon, 26 Oct 2026 17:42:04 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	201.10.91.98
Mon, 26 Oct 2026 17:12:04 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	201.10.91.98
Mon, 26 Oct 2026 16:42:04 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	201.10.91.98
Mon, 26 Oct 2026 16:12:04 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	201.10.91.98
Mon, 26 Oct 2026 15:42:04 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	201.10.91.98
Mon, 26 Oct 2026 14:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	775 ms	201.10.91.98
Mon, 26 Oct 2026 13:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	755 ms	201.10.91.98
Mon, 26 Oct 2026 12:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	944 ms	201.10.91.98
Mon, 26 Oct 2026 11:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	839 ms	201.10.91.98
Mon, 26 Oct 2026 10:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	639 ms	201.10.91.98
Mon, 26 Oct 2026 09:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	972 ms	201.10.91.98
Mon, 26 Oct 2026 08:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	743 ms	201.10.91.98
Mon, 26 Oct 2026 07:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	657 ms	201.10.91.98
Mon, 26 Oct 2026 06:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	696 ms	201.10.91.98
Mon, 26 Oct 2026 05:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	962 ms	201.10.91.98

⚙️ پارامترهای فنی پروتکل

Verified protocol configuration attributes required for manual client profiles.

آدرس هاست / سرور 201.10.91.98

پورت 8443

امنیت (Security) TLS

نوع انتقال (Transport) WS

شاخص SNI pl3.pad-sservice.lat

مسیر (Path) /PL3W

UUID 2b0e5676-fb62-4bf0-9607-6e7818421e8e

اثر انگشت TLS 19779669

🛡️

Direct TLS Encrypted Channel (WS)

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

SNI: Discreet Camouflage Host (Optimized for Evasion) Port 8443 (Alternative Web Channel) uTLS: 19779669 Custom Handshake (Active Cloaking)

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

Network Port Analysis: Connections directed to port 8443 traverse middleboxes smoothly by mimicking auxiliary cloud service APIs.

SNI Masking Analysis (pl3.pad-sservice.lat): Unremarkable domain pl3.pad-sservice.lat blends seamlessly into general international transit noise, preventing automated endpoint isolation.

uTLS Handshake Security Analysis (19779669): Using 19779669 parameters provides dependable transport-level obfuscation across international multi-hop paths.

Client Handshake Masking (uTLS): Using 19779669 parameters provides dependable transport-level obfuscation across international multi-hop paths.

❓ Frequently Asked Questions for Node #19779669

How does node #N bypass state-level censorship and firewall restrictions? ▼

Encrypted channel with clean TLS negotiation on host 201.10.***.***, 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 8443 and domain masking perform under heavy censorship in Iran and China? ▼

Connections directed to port 8443 traverse middleboxes smoothly by mimicking auxiliary cloud service APIs. Unremarkable domain pl3.pad-sservice.lat blends seamlessly into general international transit noise, preventing automated endpoint isolation. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.

What steps should I take if node #N (201.10.***.***) 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 ⏱ 9.91s

1. Exit IP & Autonomous System (Identity) 🇵🇱 PL

Public Exit IPv4: 201.10.91.98

Network (ASN / Org): AS219095 · Paul Sagov

BGP Prefix / Subnet: —

Node Location: Warsaw, Mazovia — 🇵🇱 PL

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

Address Class: 🖥️ Hosting / Datacenter

Risk Score:

20 / 100 (95% conf)

Detection Flags:

hosting

Operator / Provider: Paul Sagov

3. Geolocation Consensus (IPv4)

Providers tallied: 24

🇵🇱 PL Poland

96% (23/24)

🇧🇷 BR Brazil

4% (1/24)

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

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	● available	—	—	1268 ms
ChatGPT (app)	● available	—	—	1088 ms
YouTube Premium	● available	—	—	1242 ms
Netflix	● available	🇵🇱 PL	full catalogue	2322 ms
Claude	○ error	🇵🇱 PL	Cloudflare challenged the request, so availability was never tested	123 ms
TikTok	● available	—	—	1531 ms
Gemini	○ error	—	request failed	—
NotebookLM	● available	—	sign-in required	3022 ms

🤖 5. AI Model API Endpoints (Direct Probe)

AI Endpoint	Vendor	State	HTTP	Detail	RTT
OpenAI	OpenAI	● reachable	401	answered, credentials not supplied	1209 ms
Anthropic	Anthropic	● reachable	401	answered, credentials not supplied	1224 ms
Google Gemini	Google	● reachable	403	answered, credentials not supplied	1249 ms
DeepSeek	DeepSeek	● reachable	401	answered, credentials not supplied	1407 ms
Qwen (Singapore)	Alibaba	● reachable	401	answered, credentials not supplied	1612 ms
Qwen (Beijing)	Alibaba	● error	—	request failed	—
Kimi / Moonshot	Moonshot	● error	—	request failed	—
Zhipu GLM	Zhipu	● reachable	401	answered, credentials not supplied	1307 ms