What is an IP lookup?
An IP lookup (also called an IP address lookup or IP checker) asks databases what is known about one address. The answer names the network that owns it, roughly where that network uses it, and whether the address turns up on lists of VPNs, proxies, Tor exits, datacenters or abuse. The location part is IP geolocation.
It's not GPS. The data comes from regional internet registries, routing tables and the geolocation vendors' own measurements, and it describes a network, never the person using it. Countries are usually right, cities are approximate, and a street address is never in the data.
How to look up an IP address
-
01
Find the address
Your own is looked up as soon as this page opens. Someone else's comes from where they left it: the Received lines of an email header, your server or firewall log, a game or forum admin panel. For a website, resolve its domain to an address with a DNS lookup first.
-
02
Paste it and press Look up
Any public IPv4 address (8.8.8.8) or IPv6 address (2001:4860:4860::8888). Each address also has its own page, /ip-lookup/ followed by the address, which you can bookmark or share.
-
03
Read the card, then the details
The card answers first: owner, ASN, approximate location, the risk verdict and the VPN, proxy, Tor, relay, datacenter and bot flags. Below it: location, network, the registry record with its abuse contact, and the raw JSON.
The tools for step 1: the email header analyzer lists the servers a message passed through, and the DNS lookup turns a domain into its addresses. For a list of addresses, use the bulk IP lookup.
What a lookup shows, and where each answer comes from
None of it includes a name or a street address. Each part has its own source, named on the result too:
| Part | What you see | Where it comes from |
|---|---|---|
| Location | Country, region, city, postal code, time zone, coordinates, accuracy radius | MaxMind GeoLite2 City and DB-IP Lite, merged |
| Owner | ISP, organization, ASN and AS name, network block | MaxMind GeoLite2 ASN and DB-IP ASN Lite |
| Registry record | Network name, registered range, dates, abuse contact | The regional internet registry's RDAP service; the BGP prefix of an IPv4 address from Team Cymru |
| Hostname | The PTR name, if the owner set one | Reverse DNS |
| Risk | VPN, proxy, Tor, datacenter, verified bot, blocklists, a 0–100 score with each reason | Public and licensed lists, updated at least daily (data sources page) |
Every source, how often it is updated and its licence are on the data sources page. The owner's network has its own page too, with all its ranges: the ASN lookup.
IP checker: is this IP address risky?
The risk panel adds up points for what the address is and where it is listed, capped at 100: Low is 0–29, Medium 30–69 and High 70–100. A Tor exit or a netblock on Spamhaus DROP is High on its own; a datacenter or VPN address adds less, because plenty of honest traffic comes from both. Every point is listed with the list it came from, and what was checked and not found is listed too, so a Low score reads as checked, not unknown.
Verified search engine and monitoring bots (Googlebot, Bingbot and others, matched against the address ranges their operators publish) are marked as such and are not scored for their datacenter. The score describes the address, never the person behind it. For one list type in depth: the IP blacklist check, the VPN and proxy detector and the IP reputation check.
How does IP geolocation work?
Five layers feed the answer:
-
01
Your device makes a request
When you visit any website, your device sends its public IP address in the request headers — it has to, so the server knows where to deliver the response.
-
02
Registries provide the source of truth
Regional Internet Registries (ARIN, RIPE, APNIC, LACNIC, AFRINIC) assign IP blocks to ISPs and publish ownership records via WHOIS.
-
03
ISPs route through known infrastructure
Each ISP advertises its IP ranges via BGP (Border Gateway Protocol). Routing tables and announcements give clues about where a block is physically deployed.
-
04
Geolocation databases enrich the data
Vendors like MaxMind and DB-IP combine registry data with latency probes, user reports, mobile carrier mappings, and proprietary signals into geo-IP databases.
-
05
We combine two databases and return one answer
When you query MyIPHelp, we look up your IP in both MaxMind GeoLite2 and DB-IP Lite. MaxMind answers first and DB-IP fills its gaps; the city, region and coordinates always come together from one database, the one that names the country shown.
How accurate is an IP lookup?
Our two sources usually agree on the country: MaxMind and DB-IP named the same country for 96.2% of the addresses both placed, out of 1,000,000 random IPv4 addresses in our 2026 accuracy study. A city is an approximation. Anything narrower than a city is a guess.
Mobile networks, corporate VPNs, and shared NAT routinely break city-level accuracy. A phone on T-Mobile in Atlanta, for example, can appear to be in Tampa. That's not a bug in the geo database — it's how mobile carrier routing works.
That is also why two lookup sites can show different cities: each reads its own database, built from different measurements and updated on different days. The accuracy radius on the result says how wide the answer is. If the location of your own network is wrong, the database vendor takes corrections: MaxMind's correction form, for example.
IPv4 vs. IPv6
IPv4 uses 32-bit addresses like 8.8.8.8 — about 4.3 billion total. IPv6 uses 128-bit addresses like 2001:db8::1 — practically unlimited.
Both work with this tool: an IPv6 lookup gives the same fields as an IPv4 one (owner, location, risk). Most modern devices and ISPs run dual-stack, with an IPv4 and an IPv6 address at the same time.