IP 地址查询
任意 IPv4 或 IPv6 地址的路由、注册分配、反向 DNS 与网络类型。
An IP address identifies one endpoint on the internet. For any address you enter, this page reports which autonomous system announces a route to it, which registry allocated the block containing it and when, what reverse DNS name is published for it, and how the address is written in every other notation. Location is shown only where the network's operator published one.
What the lookup establishes
The origin AS is taken from our copy of the global BGP table, so it is the network actually announcing a path to this address right now, not a guess from a name. The delegation record — country, regional registry, allocation date and status — comes from the registry's own published file. Reverse DNS is resolved live, and we check whether that hostname resolves back to the same address, because a PTR record alone can say anything at all.
Where the answer stops
An address does not name a person, and nothing on this page attempts to. The country shown is the registry's country of record for the block, which is where the holder registered it and not necessarily where the machine sits — plenty of blocks registered in one country are deployed in another. Anything we cannot establish is marked as having no data rather than filled in with an estimate.
Reserved and special-purpose ranges
Some addresses are never routable: private ranges like 10.0.0.0/8 and 192.168.0.0/16, loopback, link-local, carrier-grade NAT space at 100.64.0.0/10, and the documentation ranges. When you enter one, the page names the range and the RFC that defines it instead of pretending to look up a holder that does not exist.
常见问题
What does the origin AS tell me?
It is the network that announces a route to this address in the global routing table — in practice, the operator that carries its traffic. For a home connection that is your ISP; for a server it is usually the hosting company.
Why is the country different from where the address actually is?
The country comes from the registry's allocation record, which reflects where the holder registered the block. Large operators register blocks in one country and deploy them across several, so the record and the reality can differ legitimately.
What is forward-confirmed reverse DNS?
A reverse DNS record can claim any hostname, because it is published by whoever controls the address. Forward confirmation checks that the claimed hostname resolves back to the same address, which is what makes the name worth anything. Mail servers use exactly this check.
Why is there no map for most addresses?
Because we only draw one when the network operator has published a geofeed under RFC 8805. That is a statement of fact by the party who actually knows. Everything else on the market is an estimate, and we would rather show nothing than draw a pin we cannot stand behind.