🇫🇷 VLESS REALITY Live Verified Node

France (FR) — VLESS TCP Node

Host: 9.247.23.209:443 • Tested: 12:24:14 AM

Checked Latency 759 ms

Est. Bandwidth 0.0 Mbps

24h Uptime SLA 100%

Exit Consensus FR (Verified)

⚡ Direct Connection URI (VLESS • France) Xray-core Verified • 100% Uptime

vless://b9bfa54d-bc44-4592-a6d6-89a9665d286f@9.247.23.209:443?flow=xtls-rprx-vision&fp=chrome&pbk=SbVKOEMjK0sIlbwg4akyBg5mL5KZwwB-ed4eEE7YnRc&security=reality&sni=mother-earth.fyi&type=tcp#%F0%9F%87%AB%F0%9F%87%B7FR-freevpnkeys.com-TG-%40yavpn_robot

1. Direct Single Key Copy the URI above into Happ, Incy, v2RayTun, or v2rayNG. Re-tested every 30 min.

2. Free Auto-Updating Subscription Auto-sync fresh working nodes every 30 min: https://freevpnkeys.com/sub/happ

3. Private 10 Gbps Anti-DPI Multi-Key Need zero congestion, 10 Gbps speed & strict ISP whitelist bypass? Get a private key in Telegram bot @yavpn_robot (~$0.05/day).

⚡ 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:

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: 100% (23 probes)

Probe Time	Probe Node	Verdict	Latency (RTT)	Exit IP
Wed, 04 Nov 2026 00:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	759 ms	51.255.37.164
Tue, 03 Nov 2026 23:24:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	618 ms	51.255.37.164
Tue, 03 Nov 2026 22:24:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	645 ms	51.255.37.164
Tue, 03 Nov 2026 21:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1154 ms	51.255.37.164
Tue, 03 Nov 2026 20:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	236 ms	51.255.37.164
Tue, 03 Nov 2026 19:24:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1860 ms	51.255.37.164
Tue, 03 Nov 2026 18:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1596 ms	51.255.37.164
Tue, 03 Nov 2026 17:24:15 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1698 ms	51.255.37.164
Tue, 03 Nov 2026 16:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	611 ms	51.255.37.164
Tue, 03 Nov 2026 15:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	785 ms	51.255.37.164
Tue, 03 Nov 2026 14:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	844 ms	51.255.37.164
Tue, 03 Nov 2026 13:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	1058 ms	51.255.37.164
Tue, 03 Nov 2026 12:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	588 ms	51.255.37.164
Tue, 03 Nov 2026 11:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	611 ms	51.255.37.164
Tue, 03 Nov 2026 10:24:14 UTC	🇺🇸 US Main	🟢 HTTP 204 OK	522 ms	51.255.37.164

⚙️ Protocol Parameter Specification

Verified protocol configuration attributes required for manual client profiles.

Host / Address 9.247.23.209

Port 443

Security Protocol REALITY

Transport Type TCP

SNI (Server Name Indication) mother-earth.fyi

Public Key (pbk) SbVKOEMjK0sIlbwg4akyBg5mL5KZwwB-ed4eEE7YnRc

Flow xtls-rprx-vision

UUID b9bfa54d-bc44-4592-a6d6-89a9665d286f

TLS Fingerprint 20486998

🛡️

VLESS Stealth Cloaking via RAW / TCP

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

SNI: Discreet Camouflage Host (Optimized for Evasion) Port 443 (Universal HTTPS Gateway) uTLS: 20486998 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: Port 443 functions as the bedrock gateway for encrypted web communications, making discriminatory packet drops virtually impossible without crippling nationwide commerce.

SNI Masking Analysis (mother-earth.fyi): Camouflaged behind neutral destination mother-earth.fyi, this node avoids heuristic scrutiny and active probe lists maintained by authoritarian firewalls.

uTLS Handshake Security Analysis (20486998): Applying custom 20486998 client parameters conceals underlying application identity during transport layer negotiations.

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

Client Handshake Masking (uTLS): Applying custom 20486998 client parameters conceals underlying application identity during transport layer negotiations.

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

❓ Frequently Asked Questions for Node #20486998

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? ▼

Port 443 functions as the bedrock gateway for encrypted web communications, making discriminatory packet drops virtually impossible without crippling nationwide commerce. Camouflaged behind neutral destination mother-earth.fyi, this node avoids heuristic scrutiny and active probe lists maintained by authoritarian firewalls. This architecture ensures dependable transit across restricted carriers such as MCI, Irancell, and China Telecom.

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

1. Exit IP & Autonomous System (Identity) 🇫🇷 FR

Public Exit IPv4: 51.255.37.164

Network (ASN / Org): AS16276 · OVH SAS

BGP Prefix / Subnet: —

Node Location: Roubaix, Hauts-de-France — 🇫🇷 FR

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

Address Class: 🖥️ Hosting / Datacenter

Risk Score:

20 / 100 (95% conf)

Detection Flags:

hosting

Operator / Provider: OVH SAS

3. Geolocation Consensus (IPv4)

Providers tallied: 10

🇫🇷 FR France

100% (10/10)

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

Service	Status	Region	Technical Detail	RTT
ChatGPT (web)	○ error	—	request failed	—
ChatGPT (app)	○ error	—	request failed	—
YouTube Premium	○ error	—	request failed	—
Netflix	○ error	—	request failed	1616 ms
Claude	○ error	🇫🇷 FR	request failed	—
TikTok	○ error	—	request failed	—
Gemini	○ error	—	request failed	—
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	● error	—	request failed	—
Google Gemini	Google	● error	—	request failed	—
DeepSeek	DeepSeek	● error	—	request failed	—
Qwen (Singapore)	Alibaba	● error	—	request failed	—
Qwen (Beijing)	Alibaba	● error	—	request failed	—
Kimi / Moonshot	Moonshot	● error	—	request failed	—
Zhipu GLM	Zhipu	● error	—	request failed	—