RPKI Validator
AvailableValidate BGP route origins against RPKI ROAs (RFC 6811) and check ASPA upstream authorizations and AS paths for any IP address, prefix or ASN, from a local rpki-client dataset.
Validate RPKI
Overview
Results
Findings & raw data
How it works
NetTools downloads the validated RPKI dataset published by rpki-client.org (all five RIR trust anchors, rebuilt about every 10 minutes), keeps the latest copy indexed in memory, and validates against it: route origin validation per RFC 6811 and ASPA path verification per draft-ietf-sidrops-aspa-verification. Live routes and ASN data come from RIPEstat (RIPE RIS); RIPEstat’s own RPKI verdict is shown only for comparison.
Route origin validation (RFC 6811)
- A ROA says which AS may originate a prefix, up to a maximum prefix length. A route is VALID when a covering ROA authorises its origin AS and its length is within maxLength.
- It is INVALID when ROAs cover the prefix but none authorises that origin, or the announcement is more specific than maxLength allows. Networks that enforce RPKI drop invalid routes.
- It is NOT FOUND when no ROA covers the prefix at all — RPKI neither confirms nor rejects it.
ASPA (IETF draft)
- An ASPA record lists the providers (upstreams) an AS has authorised. Paths can then be checked for route leaks: going “up” to a non-provider and back down is not allowed.
- Verification follows draft-ietf-sidrops-aspa-verification-31. Because a route collector does not know whether it received a route from a customer, peer or provider, NetTools evaluates both the upstream and downstream rules and only gives a single verdict when they agree.
- Only a few thousand ASes publish ASPA records. A missing record means “Unknown”, never “Invalid”.
Where the data comes from
- RPKI: the validated dataset of rpki-client.org (all five RIRs), downloaded about every 10 minutes (compressed, only when changed) and indexed locally. Its generation time is shown above the results.
- Live routes and ASN data: RIPEstat (RIPE RIS route collectors). These can be delayed or incomplete and are not the whole global routing table.
Safeguards & responsible use
- Read-only: the tool cannot announce, change or test routes. Only one fixed, verified URL is ever downloaded (rpki-client.org), using compression and “only if changed” requests.
- Inputs are validated (public IPv4/IPv6 addresses and prefixes, public ASNs) and rate-limited. Lookups run against the local dataset; nothing you enter is stored.
Learn more
What is RPKI Validator?How it works, how to read the results, troubleshooting and FAQs. Complete guide →Frequently asked questions
What do VALID, INVALID and NOT FOUND mean?
VALID: a ROA authorises this origin AS for this prefix and length. INVALID: ROAs cover the prefix but none authorises the origin AS, or the announcement is longer than the ROA’s maxLength — networks that enforce RPKI drop it. NOT FOUND: no ROA covers the prefix, so RPKI says nothing about it.
Is a missing ASPA record a problem?
No. ASPA is still an IETF draft and only a few thousand ASes publish records. A missing record means the hop cannot be checked (Unknown), never that it is wrong.
Why does an AS path show “depends on the relationship”?
ASPA verification differs for routes received from customers or peers (upstream rules) and from providers (downstream rules). A route collector does not know which applies, so NetTools shows both results and only gives a single verdict when they agree.
Why can NetTools and RIPEstat disagree?
They use different validators that refresh at different times. Right after a ROA is created or changed, one may already see it and the other not yet. The dataset time is shown with every result.