Choose IP tools by the question
These IP tools cover browser connections, public network records, and local calculations. Start with the result you need rather than running every test in the directory.
If a support form asks for your current public address, open the homepage. If you already have an address from a log or message, IP lookup provides location estimates and network registration context. These are different tasks: looking up an entered address does not show that your device currently uses it.
For unexpected routing, outbound IP detection compares what named destinations observe from this browser. The IPv6 test instead checks separate IPv4-only and IPv6-only endpoints. Use the first to investigate destination differences and the second to investigate protocol reachability.
The cards above describe the remaining operations and their inputs. Before starting, check whether the measurement runs locally, in your browser, on our server, or at a remote probe. A remote ping cannot reproduce your own Wi-Fi path, and a subnet calculation does not discover connected devices.
Read the source behind network tools
A connection observation, registry record, and location estimate answer different questions. A registered organization is not necessarily the person using an address, and a city marker is not an exact physical location. Keep the field name and source with any value you quote.
Read unavailable and incomplete states as part of the result. A timed-out request does not by itself establish an outage. An undetected protocol is not proof that the device lacks support. Matching exit addresses cover the destinations that responded; they cannot establish every application's route or certify VPN safety.
Compare the same address family, destination, and measurement origin. Otherwise, two apparently conflicting results may simply describe different connections.
Build a network troubleshooting report
Record the expected behavior, actual failure, active network, VPN state, and observation time. Run the smallest relevant check, change one condition, then repeat it. Save both results so you can explain what changed.
For incoming IPv4 problems, follow the CGNAT checks before assuming a router rule is enough. For other tasks, use each tool's explanation below its interface. The methodology and data sources describe measurement boundaries and provider roles.
Review copied reports before sharing. Include the query, source, timestamp, and error needed to reproduce the issue; remove credentials and unrelated personal details.