Skip to Content
Platform.Ontology

Real IP behind a VPN

A page cannot learn your real IP if a VPN works properly.

Blocked for appsDevice detailsNetworkWeb browsersWhen the page loadsWhile you use it

In one line

Can't see your real IP address when your VPN works properly

A page cannot learn your real IP if a VPN works properly.

Servers see the VPN exit IP. Leaks come from WebRTC (local IPs now hidden by mDNS), DNS leaks outside the browser, IPv6 bypass and timezone or language mismatch. Browsers expose no 'real IP' API.

What it can and can't do

What the user does: Nothing. It happens when your device connects to the site

It can

  • See the VPN exit IP address
  • Spot leaks from IPv6, DNS, or a broken VPN setup
  • Notice if your time zone or language does not match the IP
  • Learn the area of the VPN server

It cannot

  • See your home IP while the VPN holds
  • See your local network IP; WebRTC now hides it
  • Ask the browser for your real IP; there is no way
  • Be sure about your location from the VPN IP

Browser support

Chromenot offered
Edgenot offered
Firefoxnot offered
Safarinot offered
iPhonenot offered
Androidnot offered
Samsungnot offered
BrowserStatusFirst versionNote
ChromeNot supportedNot availableNone
EdgeNot supportedNot availableNone
FirefoxNot supportedNot availableNone
SafariNot supportedNot availableNone
Safari on iPhoneNot supportedNot availableNone
Chrome on AndroidNot supportedNot availableNone
Samsung InternetNot supportedNot availableNone

How a site asks for it

APInone
How access is grantednot-exposed
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsread fresh on every page load; nothing stored
How to take it backnot applicable
Inside an iframeReadable from cross-origin iframes too (same values)

Typical flow

  1. Page script reads the value
  2. No prompt is shown

Data you get

Shape: none
How often: static per session

FieldTypeUnitRangePrecision
proxy: WebRTC STUN reflexive candidatestringNonecan show a public IP different from HTTP when VPN is partial (split tunnel)Not listed
proxy: timezone vs IP geostringNonemismatch is a VPN tellNot listed
proxy: Accept-LanguagestringNonereveals home languageNot listed

Technical limits

  • VPN user safety

The story

What it is

A page cannot learn your real internet address if your VPN works properly.

For you

Sites see the VPN's address instead of yours. If the VPN is set up well, nothing about your home connection leaks. Leaks happen outside the browser, such as DNS or IPv6.

For makers

The real address ties a visit to a place and a person. When a VPN hides it, sites fall back on language, clock time zone and fingerprints. Fraud teams use mismatches to guess a VPN is in use.

Where you see it

TypeExampleApps
videoA streaming site wanted your real country for rights and blocks known VPN addresses.Netflix, BBC iPlayer
gamesA game site wanted your region for matchmaking and uses server latency tests.None named
bankingA bank wanted your home address for fraud checks and treats VPN use as extra risk.None named
shoppingA shop wanted your real location for price tailoring and sees the VPN place.None named
securityA fraud team spots a timezone that does not match the VPN's country.None named
adsAn ad network wanted your true area for local ads and uses the exit region.None named
newsA news paywall wanted to enforce regional rules and uses the VPN location.None named

Risks

  • Leaks outside the browser can expose you
  • Time zone mismatch can flag VPN use

What the platform says

Good uses and abuse

Legitimate uses

  • None: the browser deliberately withholds it

Known abuse

  • Leak-based deanonymization

Scores

ScoreValueMeaning
Sensitivity5 of 5How revealing the data is
Utility2 of 5How useful it is to honest apps
Friction3 of 5How much the user has to do
Fingerprint bits0Rough identifying entropy, when known

Sources

How well checked: Based on official documentation.

On this page