IP, Website, and Proxy Checking Tools
Check IP information, browser network paths, website reachability, and proxy health with focused tools and remote network probes.
Choose a tool
An IP address describes a network exit point, not a person. Read everything here as diagnostics.
Six tools for troubleshooting connectivity. Three look at addresses and paths, two test proxies, and one checks whether a site answers from outside your own network. Every one produces a snapshot: one moment, one path, one resolver. That is enough to locate a fault and not enough to make a claim about who is behind an address.
Three tools that look at addresses, and answer different questions
Use IP Address Information Lookup when you already hold an address, from a log line or an allowlist, and want the record a GeoIP and registry database holds for it: approximate country and city, the covering prefix, and the ASN with its registered organisation. It takes up to 100 addresses at once, so it also triages a list.
Use IPv4 & IPv6 Network Connectivity Check when the question is about this browser's own path rather than someone else's address. It compares whether both address families are reachable right now, which is what you want when a service works on one network and fails on another.
Use Browser IP, WebRTC & DNS Leak Check when a proxy or VPN appears configured but the traffic disagrees. It reports the public IP paths this browser exposes, the ICE candidates WebRTC gathers, and the resolver signals visible to the page.
One site checker and two proxy checkers
Website Availability & Latency Checker asks whether a host answers from several regions, with what HTTP status, through which redirect chain, and after how long. Reach for it first when a user reports a site is down and you cannot reproduce it, because it separates a fault on your path from a fault at the origin.
Batch Proxy Checker and Regional Proxy Exit Check divide by volume and depth. The batch checker takes a bounded list of HTTP, HTTPS, and SOCKS5 proxies and compares connectivity, authentication, and the target response, which is triage. Regional Proxy Exit Check runs one authorized proxy from a selected remote region and shows its target response and exit path, which answers whether a route lands where it should.
Normalize the list with Proxy List Formatter before a batch run so a failure means the proxy failed, not that a line could not be parsed. Test only destinations and proxies you own or have explicit authorization to use.
What these results are, and what they are not
A GeoIP result is a database claim about a network prefix, published with an accuracy radius, not a measurement of where a device is. The address itself usually belongs to a carrier NAT, an office gateway, a data centre range, or a proxy exit, so it describes where traffic leaves a network. It is not an identity, and these tools should not be used as though it were.
Nothing here is a verdict either. Routing changes, caches expire, and a target can rate-limit one probe and not another. Record the target, the time, the region, the status, and the stage at which the attempt failed, then take a second sample before acting on the first.
Before you rely on a result
- Record the timestamp, the region, and the exact target for every result. A check describes one path at one moment.
- Read a GeoIP location as a database claim about a network prefix, with its accuracy radius, not as a measured position or a person.
- Re-run from a second region or at a second time before concluding that a site or a proxy is down.
- Note the stage a failure occurred at, whether DNS, TCP, TLS, HTTP, or proxy authentication, because the fix differs at each.
- Test only hosts and proxies you own or are explicitly authorized to test, and keep private URLs, tokens, and credentials out of the input.
Frequently asked questions
Can these tools tell me who someone is?
No, and they are not built for that. An IP address identifies a network exit point, frequently shared by thousands of users behind a carrier NAT or a corporate gateway. The lookup returns a registry and GeoIP record for a prefix, never a person, a household, or a device.
Why does IP Info show the wrong city?
GeoIP databases map prefixes to locations using registration data and inference, so they are often accurate at country level and unreliable below it. Mobile carriers, VPN exits, and large hosting ranges are routinely placed at a provider's registered address instead of anywhere near the traffic.
A site is unreachable for me. Which tool should I start with?
Start with IPv4 & IPv6 Network Connectivity Check to confirm your own path is healthy, then use Website Availability & Latency Checker to see whether the host answers from other regions. If it answers elsewhere and not for you, the fault is between you and the origin.
My proxy passes the checker but my application still fails.
The checker and your application are different clients. Common causes are a scheme mismatch such as socks5 against socks5h, so hostnames resolve on the wrong side, an authentication method the library does not support, or a destination that rejects the proxy's exit range. Compare the failure stage in both.
Browse all developer tools or read the developer tool guides for worked examples.