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, HTTPS status and browser-reported connection type.
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.
Use one device and one browser for comparisons. Pause cloud backups, game downloads, streaming and large file transfers, then note whether the device is connected by Wi-Fi, Ethernet, mobile data or a VPN. Run the check at least three times instead of choosing a single unusually good or bad result.
Change only one condition at a time. For a Wi-Fi problem, compare beside the router with the affected room. For a suspected broadband fault, add an Ethernet result if practical. Record the time because congestion and provider work can make the same connection behave differently during the day.
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 browser sees the complete path from this device to LumaProbe, including the device, local network, provider route and test server. It cannot isolate the broadband line on its own. Browser scheduling, security software, VPNs, extensions and background activity can also influence a short test.
Treat the result as diagnostic evidence, not a contractual line measurement or a live provider-outage declaration. A provider can test a different network boundary and report a different valid number. The most useful conclusion usually comes from controlled comparisons and repeated observations.
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 browser test is exact. Device performance, browser limits, server distance and other network traffic affect the result. Compare repeated tests under the same conditions.
Test results are stored only in your browser when local storage is available. The public application does not create a user account or central result profile.
Repeat the test, pause other traffic and compare Wi-Fi with Ethernet. Change one condition at a time so the cause becomes clearer.