About ipcheckerpro
Who builds ipcheckerpro, where the IP, ASN, blocklist, and WHOIS data comes from, how the checks work, and how to report a wrong location.
What this site is
ipcheckerpro is a set of free network tools built around one question: what does the internet see when you connect? The tools show your public IP address and everything a website can infer from it, test whether a proxy or VPN leaks your real address through DNS, WebRTC, or IPv6, display the browser traits that make up a fingerprint, and provide the everyday utilities that developers and administrators reach for: DNS lookup and propagation, WHOIS, ASN lookup, blocklist checks, ping, traceroute, port checks, subnet math, and email header analysis.
Every tool is server-rendered with your data filled in, so the results work without JavaScript. Client-side scripts add the checks that only a browser can run, such as WebRTC candidate gathering and IPv6 reachability.
Who runs it
ipcheckerpro is an independent project built and maintained by a small team. It is not affiliated with any ISP, VPN, proxy, or hosting provider, and no provider pays to influence a result. The site is funded by clearly marked banner slots and partner listings; see the advertising page for how that works and what is and is not for sale.
How the checks work
IP lookup and classification. Your address, or the one you enter, is matched against a geolocation database for country, region, city, coordinates, and time zone, and against an ASN table for the network that announces it. The network name and a public datacenter list decide whether it is labeled a consumer ISP, mobile carrier, hosting provider, education or government network, or unknown. The rules are keyword-based and are shown on the result page rather than hidden.
Leak tests. The DNS leak test asks your browser to resolve unique hostnames that only our own name server can answer; the resolvers that ask are the ones your device really uses. The WebRTC leak test gathers connection candidates the same way any web page can. The IPv6 test fetches a resource from a host that has no IPv4 address.
Scoring. The anonymity score starts at 100 and subtracts a fixed number of points per signal. Every deduction is listed with its reason and a link to the glossary entry explaining it. There is no hidden model; the same inputs always produce the same score. The point values are documented in the glossary.
Lookups that go to third parties. WHOIS data is fetched from the responsible registry over RDAP. Blocklist checks query the list operators' DNS zones. DNS propagation queries public resolvers around the world. Ping, traceroute, and port scans run from our own measurement node. Results are cached for short periods so repeated queries do not hammer those services.
Data sources
We use free, openly licensed datasets and refresh them on a schedule. Each one is checked before it replaces the previous version, and the admin dashboard tracks when each dataset was last updated.
- IP geolocation: DB-IP Lite City and ASN databases, licensed under Creative Commons Attribution 4.0. Refreshed monthly. "IP geolocation by DB-IP" appears in our footer and is required of anyone who redistributes data from our API.
- ASN and prefixes: iptoasn.com, a public-domain table of announced ranges and their networks. Refreshed weekly.
- Datacenter ranges: the ipcat datacenter list (MIT license), combined with keyword rules on network names.
- Tor exit nodes: the Tor Project bulk exit list. Refreshed daily.
- Abuse ranges: the Spamhaus DROP list. Refreshed daily.
- DNS blocklists: live queries to Spamhaus ZEN, SpamCop, Barracuda, SORBS, UCEPROTECT level 1, PSBL, s5h.net, and DroneBL. Each operator's policy and removal process is linked from the result.
- Registration data: RDAP, using the IANA bootstrap registry to find the right regional or domain registry for each query.
- MAC address prefixes: the IEEE OUI registry. Refreshed monthly.
We are grateful to the maintainers of these datasets. None of them endorse this site.
Accuracy and limits
Country-level geolocation is reliable; city-level results are estimates and can be wrong, particularly for mobile ranges, recently transferred blocks, and VPN exits. Network classification is based on names and public lists, so an unusually named ISP can be labeled "unknown" and a hosting company with a plain name can slip through. The anonymity score reflects publicly checkable signals and does not predict how any particular website will treat you.
How to report a wrong location
If our result for an address is wrong, tell us through the contact page with the address, what we show, and what is correct, along with anything that supports it, such as a registry record or the provider's published range. We will check the registry and routing data and, when the geolocation database is at fault, forward the correction to DB-IP, which accepts corrections directly at db-ip.com. We do not hand-edit geolocation data, so a fix appears when the next monthly database edition includes it. For a wrong network type, we can adjust our classification rules, and those fixes take effect at the next refresh.
Contact
Questions, corrections, and partnership inquiries all go through the contact page. Our privacy policy describes exactly what the site records, and the terms describe acceptable use.