Every site and app you use
Each request carries your address, because it is where the reply has to go. The site, the company hosting it and any analytics or advertising scripts on the page all receive it.
This is the address every site you visit sees, and what a site can work out from it: roughly where you are, which provider you connect through, and which browser you use.
216.73.216.198
Columbus, Ohio, United States
Sent with the request for this page. Headers our network adds on the way in are left out.
Nothing on this card is saved. It is filled in for this one request, and the hostname comes from a reverse DNS lookup of your address.
In short: The address above is the public IP address every site you visit receives, filled in for this request and not saved. Its location and provider are an estimate for the address, not a reading of your device.
Your IP address is the number that identifies your connection on the internet. Every website, app and server you connect to receives it with each request, because it is the address the reply has to go back to. The one shown above is your public IP address: the one your internet provider gives your router or your phone’s connection. It is not the private address your router gives each device at home, which usually starts with 192.168 or 10 — ranges RFC 1918 sets aside for private networks.
From a public IP address a site can look up roughly where you are — usually a city, sometimes only a country — and which provider or company owns the network. It cannot find your street address from the IP address alone.
Each request carries your address, because it is where the reply has to go. The site, the company hosting it and any analytics or advertising scripts on the page all receive it.
It assigned the address, so it knows which subscriber holds it, and it can see which servers you connect to even when the content of the connection is encrypted.
Peer-to-peer apps, torrent clients and some games connect players and users to each other directly, and each side of a direct connection sees the other's address.
See what your address tells a site: roughly where you are, and which provider or company owns the network.
Confirm that a proxy or a VPN has really changed the address sites see, by reloading this page with it on.
Take them from the card while the proxy is off.
Or switch it on in a proxy extension.
Confirm all three are now the proxy’s.
They are what a site on the other end can notice.
This page sees only the browser that loaded it, and runs no DNS or WebRTC leak test.
| Proxy | VPN | Reconnecting | |
|---|---|---|---|
| Address sites see | The proxy's | The VPN server's | A new one, only if your provider assigns addresses dynamically |
| Location and provider sites see | The proxy's | The VPN server's | Usually the same country and provider; a new range can place you in another city |
| Traffic it covers | The browser or app you set it in | Usually everything on the device | Everything on that connection |
A proxy forwards your traffic, so sites see its address and its location instead of yours. You can set one for a browser or a single app, and a static ISP proxy keeps the same residential address for as long as you use it.
A VPN sends everything your device does through its server, and sites see the server's address. A site that looks that address up also sees which network it belongs to, so it can tell a hosting company's address from a home provider's.
Many home and mobile connections are given a new address when they reconnect to the provider. It changes the IP address, but not the country or the provider a site sees.
No. Locating an IP address works from databases that map ranges of addresses to places, and the result is an estimate for the whole range: a city or a region, sometimes only a country, and a postal code that covers an area rather than a building. Which subscriber held an address at a given time is known to your internet provider, which does not publish it, though it can be required by law to disclose it.
The location belongs to the range your address is in, not to your device, and a geolocation database places a whole range at one point. A provider can serve a wide area from one range, so the city shown may be a place nearby rather than yours. With a VPN or a proxy turned on, the location is the server's.
They are two formats of address. IPv4 looks like 203.0.113.42, an address reserved for examples, and there are too few of them, so one is usually shared by every device on a home network. IPv6 is longer, written in hexadecimal with colons, and has enough addresses for each device. A connection can have both; this page shows the one your browser used to load it.
No. Private browsing stops your browser from keeping history and cookies once you close the window. Every site you visit still receives your IP address, exactly as it does in a normal window.
Sometimes from the headers alone. A transparent proxy adds X-Forwarded-For, Via or Forwarded to every request, and X-Forwarded-For usually carries the address you had before the proxy, so a site sees both. An anonymous proxy leaves those headers out. The card above says whether your request carried one and shows which. Sites can also look the address itself up in IP-reputation and proxy-detection databases, and no header setting changes what those say.
Set the proxy in your browser and reload this page. If the IP address, location and provider change to the proxy's, your browser's traffic is going through it. This page sees only your browser, so an app set up with a proxy separately needs a check of its own.
It is the name the owner of your address range has published for it in reverse DNS, and it often contains the provider's domain. Not every address has one, and then the card shows a dash.
No. The card is filled in for your request and nothing on it is saved. To show the hostname, the address's reverse DNS name is looked up with Cloudflare's public resolver. The site's analytics are a separate matter, and they load only if you accept cookies.