Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Mon, 19 Oct 2026 08:10:58 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	506 ms	177.1.187.107
Mon, 19 Oct 2026 07:10:58 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1783 ms	177.1.187.107
Mon, 19 Oct 2026 06:40:58 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	177.1.187.107
Mon, 19 Oct 2026 06:10:58 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	177.1.187.107
Mon, 19 Oct 2026 05:40:58 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	177.1.187.107
Mon, 19 Oct 2026 04:40:58 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	546 ms	177.1.187.107
Mon, 19 Oct 2026 03:40:58 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	551 ms	177.1.187.107
Mon, 19 Oct 2026 02:40:58 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1015 ms	177.1.187.107
Mon, 19 Oct 2026 01:40:58 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	3607 ms	177.1.187.107
Mon, 19 Oct 2026 00:40:58 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	450 ms	177.1.187.107
Sun, 18 Oct 2026 23:40:58 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1111 ms	177.1.187.107

⚙️ Protocol Parameter Specification

Verified protocol configuration attributes required for manual client profiles.

Host / Address 146.75.32.8

Port 443

Security Protocol TLS

Transport Type XHTTP

SNI (Server Name Indication) Account.fastly.com

Path /

UUID 7eecba82-6a8a-4f6a-bff9-baa092931150

TLS Fingerprint 16666260

🛡️

xHTTP Cutting-Edge Transport

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

SNI: High-Profile Global SNI (Probing Risk) Port 443 (Standard HTTPS) uTLS: 16666260 (Active)

This node utilizes xHTTP transport — a state-of-the-art Xray transport protocol that offers maximum censorship resistance against active probing and DPI filters.

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 (Account.fastly.com): High-profile global domains (Account.fastly.com) are monitored by censorship systems; Reality endpoints with these SNIs face aggressive active probing.

uTLS Handshake Security Analysis (16666260): Emulating 16666260 TLS parameters to protect against passive fingerprinting.

Client Handshake Masking (uTLS): Emulating 16666260 TLS parameters to protect against passive fingerprinting.

❓ Frequently Asked Questions for Node #16666260

How does the TLS security profile protect my connection? ▼

This node utilizes xHTTP transport — a state-of-the-art Xray transport protocol that offers maximum censorship resistance against active probing and DPI filters.

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.

GeoCheck v1.4 ⏱ 20.19s

1. Exit IP & Autonomous System (Identity) 🇩🇪 DE

Public Exit IPv4: 177.1.187.107

Network (ASN / Org): — · V tal

BGP Prefix / Subnet: —

Node Location: São Paulo, São Paulo — 🇩🇪 DE

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

Address Class: 🏠 Residential / ISP

Risk Score:

0 / 100 (95% conf)

Detection Flags:

clean

Operator / Provider: V tal

3. Geolocation Consensus (IPv4)

Providers tallied: 8

🇩🇪 DE Germany

75% (6/8)

🇧🇷 BR Brazil

25% (2/8)

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

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	○ error	—	request failed	—
ChatGPT (app)	● available	—	—	583 ms
YouTube Premium	○ error	—	request failed	—
Netflix	● available	🇩🇪 DE	full catalogue	6001 ms
Claude	○ error	—	Cloudflare challenged the request, so availability was never tested	2125 ms
TikTok	○ error	—	request failed	—
Gemini	● available	—	—	5248 ms
NotebookLM	○ error	—	request failed	—

🤖 5. AI Model API Endpoints (Direct Probe)

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