Typical home router
- Input
- 192.168.1.10
- Expected output
- private (192.168.0.0/16)
The private range most routers use.
Carregando ferramenta… / Loading tool…
find your local ip address
The block above shows your public IP, the one websites see. The local IP, your device address inside the home or office network, is known only to the operating system itself, and the way to read it is just below.
The private range most routers use.
The largest of the three private ranges, common in companies.
The default Docker bridge gateway on Linux falls here.
The block stops at 172.31: one step above is already a public IP.
A self-assigned address with no valid network: restart the router or renew the lease.
The nginx instance that receives your connection on jkit.tools knows your real IP and forwards it to the Next.js container via X-Real-IP. Our API reads that header and returns it. We do not use external APIs.
The local one identifies the device inside your network and is handed out by the router (DHCP). The public one identifies your connection on the internet, is what websites see and is the one the tool above shows.
The router lends the address for a period (the DHCP lease) and may hand out a different one when it expires or when the device reconnects. For a fixed IP, reserve the address in the router by the device MAC.
With current browsers, not in a useful way: WebRTC returns a random .local name instead of the address. Without an installed app, what a site sees is the public IP.
Your IP and headers come straight from our own server (behind our nginx). To automatically check the secondary protocol (IPv4 or IPv6), the browser queries a public IP-echo service; no other data is sent. We do not call fingerprinting APIs or geolocation providers.