Most VPN tools ask what's wrong and give generic advice. This one scans your real IP, DNS resolvers, WebRTC exposure and timezone first — then combines those signals with live platform status and your symptom to estimate the most likely cause, not a generic guess.
🔍 Live scan — IP, DNS, WebRTC, IPv6, timezone🎯 Signal-based diagnosis — not a symptom checklist🔧 Step-by-step fix for your exact situation14 streaming platforms11 diagnostic branches150+ error codes
🔍 Quick VPN Leak CheckAdvanced
Not sure if your VPN is actually protecting you? Scan once without VPN to capture your real connection, then scan again with VPN on. We'll show you exactly what changed — IP, DNS, WebRTC, IPv6 — and give you a plain-English verdict on whether your VPN is doing its job.
1
Step 1 — Scan without VPN
Turn your VPN off completely. This captures your real connection — the baseline we'll compare against. Takes about 5 seconds.
IP address
Not scanned yet
DNS resolver
—
WebRTC
—
IPv6
—
Timezone
—
2
Step 2 — Scan with VPN on
Connect your VPN, wait 5–10 seconds for it to fully connect, then scan. We'll compare every signal against your Step 1 baseline and tell you what changed.
IP address
Scan baseline first
DNS resolver
—
WebRTC
—
IPv6
—
Timezone
—
🌐 Network layer
📱 Device / browser layer
🔧 What this means — and what to do
⚠️
Connect your VPN before running this diagnostic
This tool scans your current IP, DNS and WebRTC in real time.
If your VPN is off, the scan shows your real ISP connection — not your VPN.
Enable VPN first, wait 5–10 seconds for it to connect, then let the scan run.
Phase 1 — Scanning your connection
Collecting signals — this takes about 4–6 seconds…
Your visible IP
—
DNS resolver
—
WebRTC
—
Browser timezone
—
IPv6 exposure
—
Live platform feed
—
Phase 2 — Describe your problem
Select the platform, device, and closest symptom. The more context you add, the better the analysis.
1
Streaming platform
2
Device you're using
3
What's happening
4
Optional context (helps a lot)
— Select platform first —▼
—
—
Measured signals come first: IP, DNS, WebRTC, IPv6, timezone and live status. Device, account, licensing and session verdicts are best-fit hypotheses based on those signals plus your symptom.
—
—
🌐 Network layer IP address, routing, datacenter classification
🔌 DNS & privacy layer Resolver, WebRTC, IPv6 exposure
I build SmartAdvisorOnline around practical VPN diagnostics — not generic roundups. This tool exists because most VPN guides give the same 5 tips regardless of what's actually happening. The signal-first approach here is designed to give you a real answer based on your actual connection, not a symptom checklist. Read more on the author page.
Frequently asked questions
Because your description alone is not enough. Without real data, any diagnostic tool is just guessing. By scanning your IP, DNS resolver, WebRTC exposure and timezone first, we have measured signals before you even describe the problem. That means the diagnosis is based on what we can actually measure — not what you think might be happening.
Netflix, Hulu, Disney+, BBC iPlayer, Prime Video, Max, Apple TV+, Peacock, Paramount+, Crunchyroll, DAZN, Channel 4, Fubo TV and ESPN+. Each platform has its own error code database and specific diagnostic logic — for example, BBC iPlayer requires both the IP and DNS to resolve to UK, DAZN has one of the strictest VPN detection systems and requires residential IPs, and Fubo TV uses DMA-based geolocation for live sports channels.
Browser, Windows, macOS, iPhone/iPad, Android, Smart TV, Fire TV Stick, Apple TV, Roku, PlayStation, Xbox, Router VPN, and Chromecast/Google TV. Consoles and TV devices get specific guidance — for example, PlayStation and Xbox have no native VPN app support, so the tool explains router-level VPN setup rather than giving advice that doesn't apply to those devices.
There are 11 diagnostic branches: Server IP Blocked (VPN IP on platform's blocklist), DNS/IP Inconsistency (WebRTC, DNS or IPv6 leaking real location), Speed Bottleneck (throughput too low for streaming), Tunnel Instability (VPN dropping), App/Device Issue (session or device problem), Platform Congestion (service degraded, not your VPN), Browser DRM (Widevine/PlayReady failing), ISP Throttling (ISP targeting VPN traffic), Content Licensing (title not licensed in VPN server's country), Account Region Lock (account tied to different country), and Session Stuck (stale session data after VPN switch).
WebRTC is a browser API used for video calls. It can expose your IP address to websites directly — bypassing your VPN tunnel. This tool distinguishes between a real WebRTC leak (your non-VPN IP is exposed) and your VPN IP showing via WebRTC (normal, expected). If WebRTC is showing your VPN exit IP, that's fine. If it shows a different IP — especially your real ISP IP — streaming platforms can use that to detect and block your VPN.
Because not every streaming problem is a VPN problem. Browser DRM failures are caused by Widevine configuration issues — switching server won't help. Content licensing restrictions mean the title simply isn't licensed in your VPN server's country — no VPN will fix that without knowing which country has the license. Account region locks require the VPN to match your account's registration country, not just any server. Giving you the correct category saves time you'd waste on the wrong fix.
ISP throttling means your Internet provider is specifically reducing throughput for VPN traffic — not your whole connection. Signs: your non-VPN speed is fast, but any VPN connection is slow regardless of server or location. The fix is different from a slow server: obfuscated/stealth protocols disguise VPN traffic as regular HTTPS, making it much harder for ISPs to detect and throttle. Standard server-switching won't help.
No. All scanning runs in your browser. IP, DNS and WebRTC data is fetched from our diagnostic API for analysis. We do not intentionally store or associate this data with your identity. Standard server access logs may be retained for security and debugging. We do not use this data for advertising. Full details in our Privacy Policy.
Every scan reads your current connection in real time. If you switch VPN server, your IP and DNS change — but the tool still shows the old scan results. Click Re-scan to get fresh data that reflects your new server. The button appears in the top-right corner of the scan panel after the first scan completes.
Each platform has a database of known error codes — 150+ codes across 14 platforms. Selecting your error code tells the diagnostic engine the specific failure category (IP blocked, DRM, region, session, ISP throttle, residential IP required, etc.), which boosts accuracy of the verdict and surfaces the correct fix steps. If you don't see your code in the list, you can type it manually in the text field below.
CTA recommendations are conditional — they only appear when the diagnosis is one where a different provider would genuinely help. For Platform Congestion, Browser DRM, Content Licensing, Account Region Lock and Session Stuck, switching provider won't fix the underlying problem, so no recommendation is shown. For ISP Throttling, Server IP Blocked and Tunnel Instability, provider quality is genuinely relevant and recommendations appear.