What Is My Private IP? Local IP Check

Your private IP address is the local address your router assigns to this device inside your own network. It usually looks like 192.168.1.x, 10.0.0.x or 172.16.x.x, ranges reserved specifically for private networks that never route across the public internet.

Modern browsers deliberately hide the private IP from web pages. It used to leak through a WebRTC quirk, which trackers abused, so browsers now mask it behind a randomised placeholder. That is a privacy win, and it is why a browser page (including this one) usually cannot show your true private IP.

To find your real private IP, check your device directly: on Windows run ipconfig, on macOS or Linux run ifconfig or ip addr, or look at the connection details in your system settings. Your router's admin page also lists every device and its private IP.

How a website reads this

This is the exact call a page makes. Nothing else is involved, and nothing is sent anywhere: the value is read in your browser and displayed to you.

not readable by a website

Deliberately blank. Reading a local address from a page used to be possible through an RTCPeerConnection side effect; browsers closed that hole by returning randomised mDNS hostnames instead of real local addresses. This page explains where to find yours rather than taking it.

Needs your permission: No, it is read silently
Can it be faked: No. Nothing to spoof from a webpage's point of view. Your local address is assigned by your own router, on your own network.
Contribution to a fingerprint: Not counted. Nothing to contribute: a website cannot read this value at all in a current browser. How we estimate this.

The three private address ranges, and where you will see them

RFC 1918 reserves three blocks that never route across the internet. Which one you are in tells you something about the equipment you are behind.

The three private address ranges, and where you will see them
Range	Addresses it covers	Where you normally meet it
10.0.0.0/8	10.0.0.0 to 10.255.255.255	Large corporate networks, VPNs, and some providers' internal infrastructure. Roomy enough for millions of devices.
172.16.0.0/12	172.16.0.0 to 172.31.255.255	Mid-sized networks, and the default for Docker's bridge network, which is why it turns up on developer machines.
192.168.0.0/16	192.168.0.0 to 192.168.255.255	Almost every home router. 192.168.0.1 and 192.168.1.1 are the two most common gateway addresses in the world.
169.254.0.0/16	169.254.0.0 to 169.254.255.255	Not RFC 1918, but worth recognising: a link-local address your device assigns itself when it cannot reach a DHCP server. Seeing one usually means the connection failed.
127.0.0.0/8	127.0.0.1 and neighbours	Also not RFC 1918: loopback, meaning this machine. It never leaves the device at all.

None of these are reachable from the internet, which is why the same 192.168.1.1 exists on millions of networks simultaneously without conflict.

How to find your private IP on each system

On Windows, open Settings, then Network and internet, then the properties of your active connection, and read the IPv4 address. From a terminal, ipconfig prints it under the adapter you are using.

On macOS, open System Settings, then Network, select your connection and open Details. From a terminal, ipconfig getifaddr en0 prints the wifi address directly.

On Linux, ip addr show lists every interface with its address; the one you want is on your active interface, not on lo. On Android, look under Settings, then the connected wifi network, then advanced details. On iOS, tap the information icon next to your wifi network.

Your router's own address, the gateway, appears in the same places and is the one you type into a browser to reach its admin page.

The WebRTC leak, and why this card is empty now

For several years a page could read your local address without asking, by starting an RTCPeerConnection and reading the ICE candidates it generated. Establishing a peer connection legitimately requires enumerating local network addresses, and the browser handed those to the page as a side effect. It needed no permission and worked in private browsing.

It mattered because a local address is a fingerprinting signal that survives everything else. It also revealed whether you were behind a VPN: the public address said one country while the local candidates described a different network.

Browsers closed it by replacing real local addresses in ICE candidates with randomised mDNS hostnames, meaningless outside your own network. Peer connections still work; the leak does not. This card is therefore blank by design, and a blank card here is the correct result rather than a broken one.

What you should know

Why sites collect it

Legitimately, your private IP is used only inside your network so devices can find each other and your router can direct traffic. Web pages have no good reason to need it, which is why browsers stopped exposing it.

Privacy implications

When it leaked, the private IP helped trackers tell devices apart even behind the same public IP, and could reveal your internal network layout. Browsers masking it is a clear privacy improvement, so if a site claims to show it, be sceptical.

How to change or hide it

You do not need to hide your private IP from the internet because it does not travel there. Keeping WebRTC IP handling set to its default (masked) prevents the old leak. You can change your private IP in your router's DHCP settings if you ever need to.

Frequently asked questions

Why can this page not show my private IP?

Browsers now mask the private IP that once leaked through WebRTC, to stop tracking. To see it, use your operating system's network tools instead.

Is my private IP a security risk?

By itself, no. It only works inside your network. Exposing it was mainly a tracking concern, which browsers have largely closed.

Sources

Browser behaviour changes and vendors cap these values differently, so the claims above that are not self-evident are checked against the specifications and vendor documentation below.