Your public IP identifies the internet connection used for this request. It may belong to your router, mobile carrier, VPN or corporate gateway rather than directly to your device.
See your public IP, IP version, HTTPS status and browser-reported connection type.
The check runs automatically on this page. The displayed address is not added to your local test history.
A shared or changing IP is normal. LumaProbe displays it for the current request and does not add it to the application’s stored test history. Hosting security logs remain subject to server policy.
When you request the check, the server reads the public source address associated with the HTTPS request. If the site is behind a recognised proxy, it considers common proxy headers and labels the source. It also reports whether HTTPS was detected and any network-type estimate exposed by the browser.
The address must be processed to return the page, as with any web request. LumaProbe does not add the displayed address to its local test-history feature or a central result-history database. Hosting and security logs may still process request information as described in the privacy policy.
The public address check runs automatically when the page opens. If you want a controlled comparison, note whether a VPN, privacy relay, corporate tunnel or mobile hotspot is active before refreshing. Those services can deliberately change the address seen by websites.
Do not post the complete address in public support messages. It is not a password, but it can reveal network information and is rarely necessary for an open forum. Use the copy button only when you know where the address will be pasted.
The public address is normally assigned by the provider, carrier or VPN exit service, not directly to one device. Several home devices can share one IPv4 address through NAT. Mobile and some broadband networks can also share provider-side addresses. IPv6 may give devices different public addresses while still belonging to the same connection.
An unexpected country or organisation can be caused by VPN use, provider routing or an inaccurate third-party geolocation database. This tool does not geolocate the address and cannot identify a person, account holder or precise physical location.
A public IP is a network routing identifier, not proof of identity or precise location. Residential connections can change addresses, several people can share one IPv4 exit and IPv6 privacy addressing can rotate device addresses. LumaProbe does not turn the displayed address into a location or person.
The browser may not expose a reliable physical connection type. A VPN can make an address appear to belong to another network, and proxy headers must be trusted only when they come from configured infrastructure. The result therefore describes this HTTPS request, not every route used by the device.
If the value is unexpected, check whether a VPN, corporate tunnel, privacy relay or mobile hotspot is active. Compare after reconnecting, without publishing the full address in a public support forum. A changed address is normal on many dynamic residential connections.
If you need a fixed public address for a service, ask the provider about its current options and security requirements. Do not expose router administration or internal services merely to make them reachable from the internet.
Read the complete LumaProbe test methodology and privacy notes →
No. It identifies a network route and may be shared or assigned dynamically. Location databases can be approximate and LumaProbe does not geolocate the displayed address.
Websites normally see the VPN exit address rather than the access connection’s public address. Corporate tunnels and privacy relays can have the same effect.
No. It is returned for the current request and is not added to the browser speed-test history or a public account. Normal hosting and security logs may still process request data.