IP Information Lookup - Comprehensive Network Analysis

Check public IP prefix information with RIPE-backed data sources, including BGP visibility, RPKI status, geolocation, RIR context, and IRR records.

Up to 50 prefixes per search. Use network IDs rather than host addresses for the most accurate results.

Larger lists may take longer because the tool queries multiple external data sources.

This page is designed for the moment when you need to answer more than one question about the same prefix: who appears to hold it, whether it is visible in BGP, whether the origin is covered by RPKI or IRR data, and whether the routing story matches the registration story.

How To Use This Page In Practice

A useful pattern is to start with Prefix Overview or WHOIS Registration to establish basic context, then move to BGP Announcements and Routing History if you are validating reachability or checking whether an upstream change is visible. If you are reviewing policy hygiene, RPKI & IRR is usually the next stop because it gives you a quick signal on whether the public control-plane story is likely to line up with what the holder intended to publish.

What The Results Mean

Each button answers a slightly different operational question. Geolocation is about where a prefix is commonly mapped, not who owns it. WHOIS-style data is about registration context, not active routing. BGP views show what RIPE observers can currently see, not every path everywhere on the Internet. RPKI and IRR results help you judge whether a route is documented and cryptographically covered, but they do not guarantee that a deployment is correct or accepted by every network.

Common Pitfalls

The most common mistake is querying host IPs instead of network prefixes, which can make ownership and policy data harder to interpret. It is also important not to treat a missing route in public data as proof that a prefix is unused, or to treat geolocation as proof of network ownership. This page is best used as a fast triage surface before you move on to your own telemetry, vendor policy, or direct peering data.

IP Information Lookup

One-stop prefix intel: BGP visibility, RPKI, IRR, WHOIS, geo, routing history.

Category
lookup
Tags
bgp, rpki, irr, geolocation, whois

Inputs

  • One or more public prefixes, one per line, up to 50
  • Prefer network-ID (e.g. 8.8.8.0/24) over host addresses for accuracy

Outputs

  • BGP Announcements — visibility and announcement context
  • Geolocation — country / coarse location hints for the prefix
  • RPKI & IRR — ROA validation and route-object status
  • WHOIS Registration — registry records
  • Prefix Overview — consolidated summary
  • Routing History — how the prefix has moved over time

Use Cases

  • RPKI-invalid prefix triage
  • Confirming route-origin after a new announcement
  • Sanity-checking geo data before escalations
  • Looking up registry context without leaving the toolbox

Data Sources

  • RIPEstat Data API
  • RIPE Database REST API

Limitations

  • Public prefixes only; no private / RFC1918 intelligence
  • Large lists are slower because multiple data sources are queried
  • Subject to upstream RIPE API rate limits and availability

Example Input

8.8.8.0/24
1.1.1.0/24

Example Output

BGP Announcements: visible upstream, origin ASNs listed
RPKI & IRR:        ROA valid for each prefix, IRR route-objects present
Geolocation:       US / AU
(Full structured results shown per button in the UI)