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

Netherlands (NL) — VLESS TCP Node

Host: 31.41.249.50:443 • Tested: 11:12:04 PM

Checked Latency 482 ms

Est. Bandwidth 0.0 Mbps

24h Uptime SLA 96.2%

Exit Consensus NL (Verified)

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

vless://47171e1c-ee62-4f39-99bb-b77fe876095b@31.41.249.50:443?encryption=none&flow=xtls-rprx-vision&fp=firefox&pbk=AK6JtzO1bj1HM5YuKtCq0-xLWmxapYUXvKR2NKO-rkY&security=reality&sid=8fbefc33&sni=nlv1.refprov.online&type=tcp#%F0%9F%87%B3%F0%9F%87%B1NL-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: 96.2% (26 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Mon, 26 Oct 2026 23:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	482 ms	31.41.249.50
Mon, 26 Oct 2026 22:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	494 ms	31.41.249.50
Mon, 26 Oct 2026 21:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	521 ms	31.41.249.50
Mon, 26 Oct 2026 20:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1651 ms	31.41.249.50
Mon, 26 Oct 2026 19:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	274 ms	31.41.249.50
Mon, 26 Oct 2026 18:12:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	272 ms	31.41.249.50
Mon, 26 Oct 2026 17:12:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	267 ms	31.41.249.50
Mon, 26 Oct 2026 16:42:04 UTC	🇺🇸 US Main	🔴 Failed (timeout_or_captive_portal)	—	31.41.249.50
Mon, 26 Oct 2026 15:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1102 ms	31.41.249.50
Mon, 26 Oct 2026 14:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	391 ms	31.41.249.50
Mon, 26 Oct 2026 13:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	992 ms	31.41.249.50
Mon, 26 Oct 2026 12:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1939 ms	31.41.249.50
Mon, 26 Oct 2026 11:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	701 ms	31.41.249.50
Mon, 26 Oct 2026 10:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1828 ms	31.41.249.50
Mon, 26 Oct 2026 09:42:04 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	2900 ms	31.41.249.50

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

Verified protocol configuration attributes required for manual client profiles.

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

پورت 443

امنیت (Security) REALITY

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

شاخص SNI nlv1.refprov.online

کلید عمومی (pbk) AK6JtzO1bj1HM5YuKtCq0-xLWmxapYUXvKR2NKO-rkY

شناسه کوتاه (sid) 8fbefc33

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

UUID 47171e1c-ee62-4f39-99bb-b77fe876095b

اثر انگشت TLS 19762179

🛡️

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: 19762179 Custom Handshake (Active Cloaking)

This routing point in Netherlands pairs RAW / TCP transport with authenticated Reality masking to prevent active probing filters from flagging proxy handshakes.

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

SNI Masking Analysis (nlv1.refprov.online): By steering clear of prominent corporate brands, domain nlv1.refprov.online maintains uninterrupted transit across heavily policed internet pipelines.

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

Flow Technology: Vision padding ("xtls-rprx-vision") randomizes encrypted payload lengths, preventing DPI middleboxes from measuring TLS negotiation characteristics.

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

REALITY Cryptography: Node 31.41.***.*** authenticates incoming requests using pinned key (AK6JtzO1bj...), preventing unauthorized middlebox injection.

❓ Frequently Asked Questions for Node #19762179

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

This routing point in Netherlands pairs RAW / TCP transport with authenticated Reality masking to prevent active probing filters from flagging proxy handshakes. 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 nlv1.refprov.online 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.41.***.***) 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.18s

1. Exit IP & Autonomous System (Identity) 🇳🇱 NL

Public Exit IPv4: 31.41.249.50

Network (ASN / Org): AS206075 · Hollander & Jacobsen UG (haftungsbeschraenkt)

BGP Prefix / Subnet: —

Node Location: Amsterdam, North Holland — 🇳🇱 NL

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

Address Class: 🏠 Residential / ISP

Risk Score:

0 / 100 (95% conf)

Detection Flags:

clean

Operator / Provider: Hollander & Jacobsen UG (haftungsbeschraenkt)

3. Geolocation Consensus (IPv4)

Providers tallied: 23

🇳🇱 NL Netherlands

100% (23/23)

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

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	● available	—	—	1085 ms
ChatGPT (app)	● available	—	—	981 ms
YouTube Premium	● available	—	—	995 ms
Netflix	○ error	—	request failed	6000 ms
Claude	○ error	🇳🇱 NL	Cloudflare challenged the request, so availability was never tested	274 ms
TikTok	● available	—	—	1264 ms
Gemini	● available	—	—	1256 ms
NotebookLM	● available	—	sign-in required	2492 ms

🤖 5. AI Model API Endpoints (Direct Probe)

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