Why does this tool make a network request?

Your public IP is assigned by the network path, so it can only be observed by an external endpoint. The browser calls a lookup API; Utill.net does not receive or store the address from that call.

Why might IPv6 be missing or match IPv4?

Many networks are IPv4-only or hide IPv6 behind CGNAT/VPN. The dual-stack lookup may fall back to the same IPv4 when no IPv6 path is exposed.

Can this show my private LAN IP (192.168.x.x)?

No. It shows the public address visible to the lookup service, not router or Wi‑Fi local addresses.

Why does this IP differ from what my server logs show?

CDNs, reverse proxies, load balancers, and corporate egress can present a different client address to your origin than the one a public lookup sees from your browser.

Utill.net

What Is My IP

Show Public IPv4/IPv6 Instantly

See the public IPv4 and IPv6 addresses visible from your network. Instant lookup for VPN checks, allowlists, and support tickets.

Lookup runs from your browser via a third-party IP endpoint. Utill.net does not store the address.

Your public address as seen by the internet — useful for VPN and allowlist checks.

IPv4

IPv6

What is this tool?

This public IP lookup shows the IPv4 address—and IPv6 when your path exposes it—that remote services usually see for your current browser connection. That is the address that appears in allowlists, VPN checks, rate-limit logs, and many support tickets.

A public IP is not a private LAN address such as 192.168.x.x or 10.x.x.x. NAT, carrier-grade NAT (CGNAT), VPNs, corporate proxies, and IPv6 privacy extensions can all change what an external endpoint observes.

Unlike most tools here, this page must contact a third-party lookup endpoint because only the network side can report your egress address. Utill.net does not store the result.

Common use cases

Confirm a VPN or proxy is active by comparing the address before and after connect
Copy a public IPv4 for a firewall allowlist, cloud security group, or support ticket
Check whether the current path exposes IPv6 (or only falls back to IPv4)

How to use

Open the page and wait for the IPv4 hero result (skeleton while loading).
Copy IPv4, or open the IPv6 section if you need the dual-stack address.
After changing VPN, hotspot, or network, click Refresh and compare.
If a lookup fails, use Retry. Missing IPv6 usually means the path does not expose it.

Examples

Situation	Typical result	Notes
Home broadband, VPN off	ISP public IPv4 (e.g. `203.0.113.40`)	Address your ISP assigns to the CPE or CGNAT pool.
Same machine, commercial VPN on	VPN exit IPv4 (different from ISP)	Remote allowlists see the VPN, not your home IP.
Dual-stack network with IPv6	Distinct IPv6 in the collapsed section	api64-style lookup returns a real `:` address.
IPv4-only or CGNAT mobile	IPv6 section shows fallback / unavailable	Shared public IPv4 is common; not unique per device.

Practical pitfalls

VPN / CGNAT: The “your IP” value may be a shared carrier address or a VPN exit shared by many users—do not treat it as a stable personal identifier.
Server-side IP can differ: A CDN or reverse proxy may log X-Forwarded-For or an edge address that is not the same string this browser lookup returns.
Refresh after network changes; cached UI without Refresh can show a stale address.

References

Last reviewed: 2026-07-27

Frequently asked questions

Why does this tool make a network request?: Your public IP is assigned by the network path, so it can only be observed by an external endpoint. The browser calls a lookup API; Utill.net does not receive or store the address from that call.
Why might IPv6 be missing or match IPv4?: Many networks are IPv4-only or hide IPv6 behind CGNAT/VPN. The dual-stack lookup may fall back to the same IPv4 when no IPv6 path is exposed.
Can this show my private LAN IP (192.168.x.x)?: No. It shows the public address visible to the lookup service, not router or Wi‑Fi local addresses.
Why does this IP differ from what my server logs show?: CDNs, reverse proxies, load balancers, and corporate egress can present a different client address to your origin than the one a public lookup sees from your browser.