01
RIPE Database / IRR
Registry record and named parties
An inetnum, route, or route6 object records published information. It identifies the holder, maintainer, and fields recorded for that object.
SKNK · Network data notes
A lookup result has a source and a time.
A lookup for an ASN, prefix, or domain can return registry records, route observations, RPKI state, and DNS data. Each source records a different fact. Reading them separately keeps the conclusion tied to evidence.
Reviewed against public documentation: 2 August 2026
Separate the evidence
Four sources. Four distinct facts.
Every record has a scope. Its source determines the kind of conclusion it can support.
02
RIPEstat / RIS
Collector visibility at a specific time
A collector received the announcement through its own BGP sessions. The observation belongs to that collector and time.
03
RPKI / ROA
ROA match for prefix, origin, and length
A Valid result means the prefix, origin ASN, and maximum length match a published ROA in the validator's data set.
04
DNS / PeeringDB
Published names and interconnection context
Reverse DNS can return a name; a PeeringDB entry can list facilities, policy, and contacts. Both help you find context and a way to follow up.
Turn results into a record
A ticket-ready lookup note has three parts.
01
Exact object
A useful record names AS219361, 2001:db8::/48, or the complete domain. Prefix length belongs in the record.
02
Source and timestamp
Registry responses, RIS observations, and RPKI validations can differ because they come from distinct systems and update on different schedules. Their source and timestamp explain the difference.
03
Reachability from relevant paths
A reachability decision uses tests from the networks your users or upstreams actually use. Public lookup data provides context for that test.
Source notes
Public sources used by these lookups.
They update on different schedules, so the query time belongs with the result.
Registry and IRR records
RIPE Database
Whether a public object exists for this ASN or prefix, who it is registered to, and who maintains it.
Primary object documentationBGP routing observations
RIPEstat / RIS
Which collectors saw this route or prefix at a given time, and who the origin was.
RIPEstat Data APIRoute-origin authorisation
RPKI / ROA
Whether the announcer holds an authorisation — prefix, origin ASN, and maximum length matching.
RIPE NCC RPKI documentationPublic interconnection information
PeeringDB
What a network, facility, or exchange has published about interconnection and contacts.
PeeringDB documentationName and reverse-name lookups
DNS and reverse DNS
What the DNS or reverse-DNS lookup returned for this IP or domain at query time.
Reverse DNS toolNetwork lookup tools
An exact object makes a lookup useful.
An ASN, prefix, or domain is enough to begin. Every network tool here is read-only and leaves registry records unchanged.