IP address lookup
Type in an address, a prefix or an AS number. You get back the registry record, who is announcing the space, whether that announcement validates under RPKI, and where the geolocation databases think it is. These are the checks our brokers run before a block gets offered to anyone.
Try 8.8.8.0/24
or AS6206.
Bare numbers are read as AS numbers.
What this checks
Four questions, answered by four sources that do not talk to each other. Together they tell you most of what you need to know about a block's health.
Who holds it
Which RIR, which allocation it sits inside, and the organization recorded against it. Of the four answers on this page, this is the only one a registry actually asserts. Everything else is measured or inferred.
Whether it is announced, and by whom
Registered space that nobody announces is not reachable. That sounds obvious and it catches people out regularly, usually after a transfer where the paperwork completed and the routing never followed.
More than one origin announcing the same prefix is worth a second look. Sometimes it is a deliberate multi-origin setup. Sometimes it is a network announcing space it has no right to.
Whether the announcement validates
RPKI ties a prefix to the AS numbers allowed to originate it. When you see invalid, the announcement contradicts what the holder themselves published. A growing share of large networks simply drop those routes.
Where it claims to be
Geolocation is commercial guesswork. Providers disagree with each other constantly, and none of them is authoritative in the way a registry record is.
A block with the wrong location routes perfectly well. It also breaks streaming, payment and login flows for every customer using it, which is why this ends up in our inbox more than any other single complaint.