Public IP
The address your ISP or cloud provider routes to the internet. Remote servers typically see this endpoint.
203.0.113.45View your current public IP and approximate location/ISP context. Below we summarize IP types, how VPNs change visibility and common privacy risks.
YOUR PUBLIC IP ADDRESS
Looking up…
Location is approximate (often city-level). The lookup is performed from your browser via a third-party geo-IP service; Secunnix does not store results on our servers.
The address seen on the internet differs from your local LAN address; IPv4 and IPv6 are two protocol generations.
The address your ISP or cloud provider routes to the internet. Remote servers typically see this endpoint.
203.0.113.45An RFC1918 address valid only on your local network; not directly routed on the public internet.
192.168.1.xAn Internet Protocol (IP) address is a numerical identifier assigned to an endpoint on a network. When you browse the web, remote servers see your public IP to return responses.
Your public IP can reveal approximate geography (often city-level), ISP hints and connection context. That matters for privacy and realistic threat modeling.
| Aspect | IPv4 | IPv6 |
|---|---|---|
| Format | 32-bit dotted decimal (e.g. 192.0.2.1) | 128-bit hex (e.g. 2001:db8::1) |
| Address space | ~4.3B (effectively exhausted) | Very large address space |
| Adoption | Still dominant today | Growing with dual-stack transitions |
| Note | NAT and private ranges inside LANs | End-to-end addressing—policy and segmentation still required |
With a VPN or egress proxy, remote sites usually see the VPN exit’s public IP; your private IP stays behind the gateway.
A VPN sends traffic through an encrypted tunnel to an exit point; targets see that exit’s public IP. In enterprises, split tunneling, DNS and IPv6 leaks must be validated separately—“VPN on” alone is not proof of complete isolation.
Choose based on your threat model; technical options rather than vendor endorsements:
It is the routed address used to deliver packets on the internet. IPv4 and IPv6 are the main versions; your public IP is what remote servers usually observe.
Usually no—most services estimate city/region. Precise location typically needs additional data or ISP correlation; legal processes may map IPs to subscribers.
Remote systems see the VPN exit IP, but DNS, WebRTC or IPv6 leaks can still expose your real path. Validate with dedicated tests.
Static IPs stay the same for long periods (common on servers and B2B lines). Dynamic IPs rotate from ISP pools—typical for home users.
Dual-stack networks may expose both. If only one path is tunneled through a VPN, split traffic can leak.
No—this page shows your public egress IP. Private LAN addresses appear in your router or OS settings.
Assess your threat model: change egress (VPN/Tor), reduce exposure in gaming/P2P and follow corporate incident response if applicable.
No. This page is awareness and quick checks. Penetration testing and architecture reviews aligned to OWASP, PTES and your policies are still required.