⚠️

Node No Longer Responding

This server is no longer responding (verified by our checker). Recommended working alternatives:

🇳🇱 MTPROXY Server Sleeping / Dead

Netherlands (NL) — MTPROXY TCP Node

Host: max.kimt.click:443 • Tested: 6:10:58 AM

✈️ Open in Telegram
Checked Latency Offline / Timeout
Est. Bandwidth 0 Mbps
24h Uptime SLA 0% (Inactive)
Exit Consensus NL (Unreachable)

⚡ 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: 65.5% (29 probes)
Probe Time Probe Node Verdict Latency (RTT) Exit IP
Mon, 19 Oct 2026 07:10:58 UTC 🇺🇸 US Main 🔴 Failed (unreachable) — 177.1.202.217
Mon, 19 Oct 2026 06:10:58 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 226 ms 177.1.202.217
Mon, 19 Oct 2026 05:10:59 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 314 ms 177.1.202.217
Mon, 19 Oct 2026 04:10:58 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 286 ms 177.1.202.217
Mon, 19 Oct 2026 03:10:58 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 232 ms 177.1.202.217
Mon, 19 Oct 2026 02:10:58 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 319 ms 177.1.202.217
Mon, 19 Oct 2026 01:40:58 UTC 🇺🇸 US Main 🔴 Failed (unreachable) — 177.1.202.217
Mon, 19 Oct 2026 00:40:58 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 273 ms 177.1.202.217
Mon, 19 Oct 2026 00:10:58 UTC 🇺🇸 US Main 🔴 Failed (unreachable) — 177.1.202.217
Sun, 18 Oct 2026 23:40:58 UTC 🇺🇸 US Main 🔴 Failed (unreachable) — 177.1.202.217
Sun, 18 Oct 2026 22:40:58 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 232 ms 177.1.202.217
Sun, 18 Oct 2026 22:10:58 UTC 🇺🇸 US Main 🔴 Failed (unreachable) — 177.1.202.217
Sun, 18 Oct 2026 21:10:58 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 253 ms 177.1.202.217
Sun, 18 Oct 2026 20:10:58 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 298 ms 177.1.202.217
Sun, 18 Oct 2026 19:10:58 UTC 🇺🇸 US Main 🟢 HTTP 204 OK 242 ms 177.1.202.217

⚙️ Protocol Parameter Specification

Verified protocol configuration attributes required for manual client profiles.

Host / Address max.kimt.click
Port 443
Security Protocol TLS
Transport Type TCP
Secret ee1b153cf06dbd43c6085c359a6702eb936d61782e6b696d742e636c69636b
🛡️

Standard TLS Encryption (RAW / TCP)

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

Port 443 (Standard HTTPS) uTLS: MTProto FakeTLS (ee-secret)

Standard TLS encryption channel over RAW / TCP. Provides robust end-to-end data security suitable for networks with standard censorship policies.

Network Port Analysis: Port 443 is the universal standard for secure HTTPS traffic. Firewalls and ISPs cannot block it without disrupting regular web access.
uTLS Handshake Security Analysis (Native Telegram WebView): MTProto FakeTLS emulates a standard TLS 1.3 handshake to the target SNI domain.
Client Handshake Masking (uTLS): MTProto FakeTLS emulates a standard TLS 1.3 handshake to the target SNI domain.

❓ Frequently Asked Questions for Node #16035692

How does the TLS security profile protect my connection? ▼

Standard TLS encryption channel over RAW / TCP. Provides robust end-to-end data security suitable for networks with standard censorship policies.

What client apps are recommended for this MTPROXY 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
1. Exit IP & Autonomous System (Identity) 🇳🇱 NL
Public Exit IPv4: 177.1.202.217
Network (ASN / Org): — · V tal
BGP Prefix / Subnet: —
Node Location: São Paulo, São Paulo — 🇳🇱 NL
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: 11
🇳🇱 NL Netherlands
82% (9/11)
🇧🇷 BR Brazil
18% (2/11)

🔓 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 🇳🇱 NL
iplocation.com 🇳🇱 NL
maxmind.com —
rdap.db.ripe.net 🇳🇱 NL
ipinfo.io —
ipregistry.co 🇳🇱 NL
ipapi.co —
country.is 🇳🇱 NL
geoapify.com 🇳🇱 NL
geojs.io 🇳🇱 NL
ipapi.is 🇧🇷 BR
ipbase.com 🇳🇱 NL
ipquery.io 🇧🇷 BR
ipwho.is —
ip-api.com 🇳🇱 NL
2ip.io —

🔄 Auto-Updating App Subscriptions

Subscribe to all active verified Netherlands MTPROXY 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.