IP Address Lookup
Look up any IPv4 or IPv6 address to inspect its network identity, registration, BGP route origin, reverse DNS and RPKI validation.
Ready for analysis
Enter an IPv4 or IPv6 address to build a network intelligence report.
Analyzing network evidence…
IP Intelligence Report
01
Network identity
Registration and routing are independent datasets, maintained by different organizations on different update schedules. They may name different organizations for the same address — treat an origin ASN as the network currently routing the prefix, not as ownership of it.
02
RDAP evidence
Registration
Registration data is not available for this address.
Registration details
03
BGP evidence
Routing
No current BGP route was observed for this address.
View collectors
Multiple origin ASNs observed. Multiple-origin routing can be legitimate; it needs context before being treated as a routing incident.
04
IPRevealed US1 — RPKI validation
Route security
No RPKI route validation applies to this address.
RPKI validates route-origin authorization only — it is not a measure of host security, content or reputation.
05
MaxMind GeoLite2 City · inferred evidence
Regional context
Approximate location is not available for this address. No usable IP-based geographic estimate was returned.
Location intelligence
This is an approximate network-based location and must not be interpreted as the physical location of a person or device.
06
IPRevealed US1 probe
Reverse DNS
07
Routing context
Origin network
Loading origin network details…
View sample prefixes
Origin network details are temporarily unavailable.
Understanding IP lookup
-
01
What does an IP address lookup show?
An IP address lookup connects an IPv4 or IPv6 address with public network information: the prefix it falls in, the origin ASN currently announcing that prefix in BGP, RDAP registration records, any reverse DNS hostname, and the RPKI route-validation state. IPRevealed queries each of these signals live and shows them side by side rather than treating a single database as definitive.
-
02
What is an ASN?
An Autonomous System Number (ASN) identifies a network that takes part in Internet routing. The origin ASN shown for a prefix is the network currently announcing that route — on its own it is not the legal owner of the address. Registration records describe how the block is allocated; the origin ASN describes how it is routed right now.
-
03
Who owns an IP address?
“Ownership” is usually an oversimplification. RDAP shows which organization an address block is registered or allocated to at a Regional Internet Registry. BGP shows which network currently originates the route for that prefix. These are frequently the same organization, but a block can legitimately be registered to one party and routed by another — through address leasing, multi-homing or recent reallocation.
-
04
IPv4 and IPv6 lookups
The tool accepts both IPv4 and IPv6 addresses through the same lookup path. How much registration, routing, reverse DNS and RPKI information comes back depends on address-family coverage and the public datasets involved, so an IPv6 address can return a different level of detail than an IPv4 address.
Analyst notes
How to read this report
The network identity summary at the top of the report gives the headline facts: whether the address is currently routed, which autonomous system originates that route, the announced prefix, and whether RPKI route validation passes. Each section below expands on one of those facts with its underlying evidence.
Registration and routing are shown separately on purpose — the organization an address block is registered to is not always the network currently routing traffic for it. Treat an ASN as the current route origin, not as ownership of the address.
Data provenance
Methodology & sources
- RIR RDAP
- Registration & allocation context, queried live from the relevant Regional Internet Registry.
- RIPE RIS
- Observed BGP routing, retrieved via the RIPEstat API from RIPE NCC's RIS route-collector network — the prefix and origin ASN currently visible in the global routing table.
- IPRevealed US1
- An independent reverse-DNS network probe operated by IPRevealed.
- IPRevealed US1 RPKI
- Route Origin Validation provided by IPRevealed's independent US1 validation service.
Registration data and routing data are independent datasets and may identify different organizations. IP geolocation, when used elsewhere on IPRevealed, is approximate and should not be treated as a precise physical location.
Checking your own connection?
Related network tools
Deterministic address-planning tools that pair well with an IP lookup. Browse all IP & network tools
- Subnet CalculatorInspect one IPv4 or IPv6 subnet in detail.
- VLSM CalculatorPlan variable-size subnets from host requirements.
- Subnet SplitterDivide a network into equal-size child subnets.
- CIDR & IP Range ConverterConvert between CIDR blocks and arbitrary IP ranges.
- Subnet Overlap CheckerCheck whether two networks conflict or one contains the other.
- Route Summarization CalculatorAggregate a list of routes down to the fewest exact prefixes.
Reference
Frequently asked questions
What can an IP lookup tell me?
It shows how an address block is registered (RDAP), whether it is currently routed on the Internet and by which autonomous system (BGP), whether that route is covered by a valid RPKI authorization, and any reverse DNS hostname associated with the address.
What is the difference between an IP owner and an origin ASN?
Registration (RDAP) describes who an address block is allocated to. The origin ASN describes which network is currently announcing that prefix in BGP. These are frequently the same organization, but not always — a block can be registered to one organization while routed by another, for entirely legitimate reasons.
What is reverse DNS?
Reverse DNS (PTR) maps an IP address back to a hostname, the reverse of a normal DNS lookup. A PTR record is naming context set by the network operator — it is not identity, not proof of ownership, and a missing PTR is normal rather than suspicious.
What does RPKI Valid mean?
It means the observed BGP origin for this prefix is covered by a matching Route Origin Authorization (ROA) — a cryptographic statement of which ASN is authorized to originate that route.
Does RPKI Valid mean an IP is safe?
No. RPKI validates route-origin authorization, not host security, content, or reputation. A route can be RPKI Valid and still belong to a compromised or malicious host, and vice versa.
What do RPKI Valid, Invalid and Not Found mean?
Valid — the observed BGP origin is covered by a matching Route Origin Authorization. Invalid — an ROA exists for the prefix but the observed origin ASN or prefix length does not match it, which is often a configuration issue rather than an attack. Not Found — no ROA covers the prefix, so RPKI has nothing to say about it; this still describes much of the routing table and is not a danger signal.
Why can registration and BGP information differ?
They come from independent datasets maintained by different organizations on different update schedules: RIR registries for RDAP, and route collectors for BGP. Legitimate reasons for a mismatch include address leasing, multi-homing and recent reallocation.
Can an IP lookup reveal someone's exact address?
No. RDAP and BGP data describe network infrastructure, not a physical street address. Where IPRevealed shows geolocation elsewhere, it is an approximate estimate, not a precise location.