🌐 VLESS REALITY نود فعال و تاییدشده

KZ (KZ) — VLESS TCP Node

Host: 31.130.153.101:443 • Tested: 4:42:04 AM

Checked Latency 869 ms

Est. Bandwidth 0.0 Mbps

24h Uptime SLA 88.5%

Exit Consensus KZ (Verified)

⚡ لینک مستقیم اتصال (VLESS • KZ) Xray-core Verified • 88.5% Uptime

vless://3cd95e58-9f0a-47e1-9937-64a58e949aa5@31.130.153.101:443?encryption=none&flow=xtls-rprx-vision&pbk=6eN2NciEaZis5J4muRRqpfLQ1OglI3A8lNSTmAGo6Do&security=reality&sid=3c6fc84d&sni=stats.vk-portal.net&type=tcp&fp=chrome#%F0%9F%8C%90KZ-freevpnkeys.com-TG-%40yavpn_robot

۱. ایمپورت مستقیم کلید لینک بالا را در Happ، Incy، v2RayTun یا v2rayNG کپی کنید.

۲. اشتراک خودکار رایگان برای بروزرسانی خودکار سرورها، لینک اشتراک را اضافه کنید: https://freevpnkeys.com/sub/happ

۳. کلید اختصاصی بدون افت سرعت برای سرعت ۱۰ گیگابیت و دور زدن محدودیت‌های شدید ملی، کلید اختصاصی را از ربات تلگرام @yavpn_robot دریافت کنید.

⚡ تست زنده تاخیر مرورگر

اندازه‌گیری زمان رفت و برگشت (RTT) از مرورگر شما تا این نود.

👍 Community Health Rating

Does this server currently connect and route traffic from your location?

🚀 افزودن با ۱ کلیک به اپلیکیشن

افزودن سریع این سرور به برنامه‌های محبوب فیلترشکن:

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: 88.5% (26 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Mon, 26 Oct 2026 04:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	869 ms	31.130.153.101
Mon, 26 Oct 2026 03:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1080 ms	31.130.153.101
Mon, 26 Oct 2026 02:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	804 ms	31.130.153.101
Mon, 26 Oct 2026 02:12:04 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	31.130.153.101
Mon, 26 Oct 2026 01:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1054 ms	31.130.153.101
Mon, 26 Oct 2026 00:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1067 ms	31.130.153.101
Sun, 25 Oct 2026 23:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1258 ms	31.130.153.101
Sun, 25 Oct 2026 22:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1090 ms	31.130.153.101
Sun, 25 Oct 2026 21:12:05 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	807 ms	31.130.153.101
Sun, 25 Oct 2026 20:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1011 ms	31.130.153.101
Sun, 25 Oct 2026 19:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	615 ms	31.130.153.101
Sun, 25 Oct 2026 18:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1338 ms	31.130.153.101
Sun, 25 Oct 2026 17:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1739 ms	31.130.153.101
Sun, 25 Oct 2026 16:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1539 ms	31.130.153.101
Sun, 25 Oct 2026 15:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	692 ms	31.130.153.101

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

Verified protocol configuration attributes required for manual client profiles.

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

پورت 443

امنیت (Security) REALITY

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

شاخص SNI stats.vk-portal.net

کلید عمومی (pbk) 6eN2NciEaZis5J4muRRqpfLQ1OglI3A8lNSTmAGo6Do

شناسه کوتاه (sid) 3c6fc84d

جریان (Flow) xtls-rprx-vision

UUID 3cd95e58-9f0a-47e1-9937-64a58e949aa5

اثر انگشت TLS 19228189

🛡️

Perimeter-Defeating VLESS Node

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

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

The endpoint leverages cryptographic Reality camouflage over RAW / TCP to secure international internet access with an observed round-trip latency of 58 ms.

Network Port Analysis: Using port 443 minimizes transit packet loss and prevents artificial connection resetting on congested undersea fiber cables.

SNI Masking Analysis (stats.vk-portal.net): By steering clear of prominent corporate brands, domain stats.vk-portal.net maintains uninterrupted transit across heavily policed internet pipelines.

uTLS Handshake Security Analysis (19228189): Emulating 19228189 parameters provides adequate traffic camouflage across standard commercial broadband providers.

Flow Technology: Deploying "xtls-rprx-vision" ensures the encrypted session resists advanced machine-learning classification models at border gateways.

Client Handshake Masking (uTLS): Emulating 19228189 parameters provides adequate traffic camouflage across standard commercial broadband providers.

REALITY Cryptography: Server-pinned Reality key (6eN2NciEaZ...) coupled with session ID (3c6fc84d) guarantees zero-knowledge mutual authorization in Netherlands.

❓ Frequently Asked Questions for Node #19228189

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

The endpoint leverages cryptographic Reality camouflage over RAW / TCP to secure international internet access with an observed round-trip latency of 58 ms. 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? ▼

Using port 443 minimizes transit packet loss and prevents artificial connection resetting on congested undersea fiber cables. By steering clear of prominent corporate brands, domain stats.vk-portal.net maintains uninterrupted transit across heavily policed internet pipelines. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.

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

1. Exit IP & Autonomous System (Identity) 🇰🇿 KZ

Public Exit IPv4: 31.130.153.101

Network (ASN / Org): AS9123 · TimeWeb Ltd.

BGP Prefix / Subnet: —

Node Location: Almaty, Almaty — 🇰🇿 KZ

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

Address Class: 🖥️ Hosting / Datacenter

Risk Score:

20 / 100 (95% conf)

Detection Flags:

hosting

Operator / Provider: TimeWeb Ltd.

3. Geolocation Consensus (IPv4)

Providers tallied: 25

🇰🇿 KZ Kazakhstan

96% (24/25)

🇷🇺 RU Russia

4% (1/25)

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

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	● available	—	—	2612 ms
ChatGPT (app)	● available	—	—	2481 ms
YouTube Premium	● available	—	—	2394 ms
Netflix	● available	🇰🇿 KZ	full catalogue	4489 ms
Claude	○ error	🇰🇿 KZ	Cloudflare challenged the request, so availability was never tested	1397 ms
TikTok	● available	—	—	2510 ms
Gemini	● available	—	—	2407 ms
NotebookLM	● available	—	sign-in required	4715 ms

🤖 5. AI Model API Endpoints (Direct Probe)

AI Endpoint	Vendor	State	HTTP	Detail	RTT
OpenAI	OpenAI	● reachable	401	answered, credentials not supplied	2414 ms
Anthropic	Anthropic	● reachable	401	answered, credentials not supplied	2500 ms
Google Gemini	Google	● reachable	403	answered, credentials not supplied	2503 ms
DeepSeek	DeepSeek	● reachable	401	answered, credentials not supplied	2704 ms
Qwen (Singapore)	Alibaba	● reachable	401	answered, credentials not supplied	3025 ms
Qwen (Beijing)	Alibaba	● error	—	request failed	—
Kimi / Moonshot	Moonshot	● error	—	request failed	—
Zhipu GLM	Zhipu	● reachable	401	answered, credentials not supplied	2626 ms