IP lookup

Look up any IP address. Free.

Who owns it, which network it belongs to, roughly where it sits, and what its reverse DNS says. Then the part most lookup tools leave out: whether anything about it should worry you.

Live IP intelligence
<1ms

Result

185.220.101.34

Brandenburg, Germany · TORSERVERS-NET · Data Center

Fraud score100critical
VPN · yesProxy · yesTor · yesDatacenter · yes
Tagsc2_serverbotnet_nodessh_brute_force+12 more
high confidenceopen full report →

Pre-filled with a known Tor exit node. Type any IPv4 or IPv6 address to look up your own.

Behind every check

19.8 million

IP addresses profiled

2.4 million

malicious domains tracked

208,000

disposable email domains

1.9 million

networks scored

Counts read live from the engine, not written into the page. The full dataset is published on GitHub under the MIT license and rebuilt every 30 minutes.

What the lookup returns

Network owner

The organisation the address is allocated to, and the internet provider actually serving it. These are frequently different, and the difference matters when you are working out who to contact.

Autonomous system

The AS number and the name behind it. This is the unit networks are actually routed in, and it is the right level to reason about when a whole range misbehaves rather than one address.

Reverse DNS

The PTR hostname, where one is published. Naming conventions in reverse DNS give away more than operators realise: pool and dyn strings mark consumer connections, provider prefixes mark hosting.

Approximate location

Country and region, with city where we hold it. Labelled approximate on purpose, because that is what it is.

WHOIS registration

The allocated range, the netname, the registry it came from, and the published abuse contact, so a complaint can reach someone who can act on it.

Connection type

Residential, business, mobile, datacenter, or anonymising infrastructure. This single field explains most of the difference in how sites treat one visitor versus another.

How accurate is IP geolocation, really

Less accurate than almost every map pin on the internet implies. Country is reliable. Region is usually right. City is frequently wrong, sometimes by hundreds of kilometres, because addresses are commonly registered against a provider's administrative address rather than where a customer sits, and because one mobile or carrier-grade NAT address can serve a whole region at once. Anyone showing you a precise pin on a street is dressing up a guess. We show what we hold and label it approximate, which is less impressive and considerably more honest.

Why look up an address at all

Something in your logs

An address hammering your login page. The lookup tells you whether it is a datacenter running automation or a residential line, which decides whether blocking it is safe or is about to catch real customers.

Working out who to complain to

The abuse contact from WHOIS is the address that actually reaches someone with the power to disconnect a customer.

Understanding your own connection

If sites keep challenging you, the reason is usually visible right here: a datacenter classification, a VPN endpoint, or a provider sharing one address among thousands of subscribers.

Questions people ask

Is this IP lookup tool free?

Yes, with no account and no cap on how many addresses you look up. The public API endpoint behind it is free and needs no key either, so you can call it from your own code without signing up for anything.

Can I find someone's exact address from their IP?

No, and neither can any other tool that claims to. IP geolocation gives you country reliably, region usually, and city approximately and often wrongly. The link between an address and a subscriber is held by the internet provider, and releasing it requires a legal process. Any service promising a street address from an IP is selling a guess dressed up as a fact.

What is an ASN and why does it matter?

An autonomous system number identifies the network that announces a block of addresses to the rest of the internet. It matters because abuse very often clusters at the network level rather than the address level. One bad address is an incident; a network whose observed traffic is overwhelmingly abusive is a pattern, and the two call for different responses.

Why does the lookup show a different city than I expect?

Because the databases behind every IP geolocation service map addresses to registration data, not to physical reality. Providers register large blocks against one administrative location, mobile carriers move addresses between regions freely, and VPNs deliberately place you somewhere else. A mismatch is normal and rarely means anything is wrong.

Do you log the addresses I look up?

Lookups are counted in aggregate so we can keep the service correctly sized. We do not build a profile of what you searched, and looking an address up does not report it. Reporting is a separate, deliberate action.

Do it in code.

The same answer from a free API endpoint, or download the whole database and never call an API at all. No card, no quota, no expiry.