Donate

Support Center

Troubleshoot tool issues, understand your diagnostic results, and reach the team when you need help
Before contacting support

Start with the quick checks that solve most problems

IP Trackers provides free network diagnostics across IP lookup, DNS leak testing, WHOIS, ASN analysis, and proxy detection. Most issues come down to stale browser state, network filtering, or confusion about what a result actually means.

If your issue is not covered by the common cases below, use the contact form further down the page and include the tool URL, test input, timestamp, and the exact output you saw. That usually gives us enough context to separate a real bug from a network-environment issue.

Common issues and first fixes

Having trouble looking up an IP address?

Ensure you're entering a valid IPv4 address format (e.g., 192.168.1.1). Check your internet connection and try again.

IP geolocation showing wrong location?

IP geolocation is approximate and may not always be 100% accurate. Location data is based on ISP information and network routing.

Service taking too long to respond?

This may be due to network latency or high server load. Try refreshing the page or clearing your browser cache.

Not sure what the data means?

Visit our FAQ page for detailed explanations of each data field, including ISP, timezone, and coordinates.
What usually looks wrong

Understanding unexpected results

Our tools surface raw diagnostics such as IP addresses, ASN numbers, DNS resolver IPs, geolocation estimates, and detection flags. When a result looks surprising, it does not automatically mean the tool is broken. In many cases, the tool is correctly showing how your network is actually routed.

  • IP location seems wrong: IP geolocation is only an estimate and depends on database freshness. VPNs, mobile networks, and CGNAT can all shift your apparent city or region. See why IP location can be wrong.
  • VPN connected but IP unchanged: split tunneling, DNS leaks, or WebRTC leaks can keep exposing part of your original connection. Run the VPN verification check and compare it with the troubleshooting guide.
  • DNS leak test shows unexpected resolvers: your OS or browser may be using DNS-over-HTTPS outside the VPN path, so the leak is not always inside the VPN app itself.
  • Blacklist check shows a listing: most IP blacklists operate on shared ranges, not on you personally. Read how DNSBLs work before assuming the listing is tied to your individual activity.
  • ASN or ISP looks unfamiliar: mobile carriers, enterprise gateways, and VPN providers often show their own ASN rather than your home ISP. Learn more about ASN in networking.
Tool-specific troubleshooting

How to interpret each tool when results look odd

  • IP Lookup: shows your public IPv4 or IPv6 address plus location, ISP, and ASN context. A different nearby city is common on mobile, satellite, and shared-range connections.
  • DNS Leak Test: checks whether DNS requests are escaping your intended route. Ideally, a VPN setup should show only the resolver path you expect.
  • WebRTC Leak Test: detects whether the browser is exposing local or public IPs through WebRTC APIs despite the network path you thought you were using.
  • WHOIS Lookup: returns registration and allocation data from regional registries such as ARIN, RIPE, and APNIC. The result often points to the provider or block owner, not the end user.
  • Proxy or VPN Detection: compares your IP against known proxy, hosting, and VPN intelligence sources. Shared IPs, mobile gateways, and datacenter ranges can still produce false positives.
When you contact us

How to get a faster, more useful support response

The fastest support requests are reproducible. If you can show us the exact tool page, input, timestamp, and output, we can usually tell much faster whether the problem is a provider-side issue, stale data, browser interference, or a genuine bug.

If the problem only happens on one network, include that too. Many support issues turn out to be corporate filtering, VPN overlap, browser DNS settings, or mobile-carrier routing rather than a fault in the lookup itself.

Send us a Message