Route origin validation calculator
Paste a route (prefix and origin AS) and the VRPs you have, and get its RFC 6811 state (Valid, Invalid or NotFound) with the reason VRP by VRP: which VRPs cover it, which match, and why the others fail. AS 0 and maxLength are handled as the RFCs state them, IPv4 and IPv6 alike, and nothing is fetched.
RangkaianEach line holds a prefix, an optional maxLength and the AS, in that order; the AS may be asplain (AS64496 or 64496) or asdot (AS1.10). The maxLength may also follow the prefix after a hyphen (203.0.113.0/24-26, as RFC 9319 writes it). Without a maxLength only the exact prefix is authorised. An AS written with its AS prefix may stand anywhere on the line (AS64496,192.0.2.0/24,24). A # starts a comment. You can also paste RFC 8416 SLURM JSON: its prefixAssertions are read as the VRPs.
Runs in your browser and fetches nothing: no RPKI repository, no validator, no route collector. The verdict holds for the VRPs you paste and for no other list.
The validation runs entirely in your browser on the route and the VRP list you supply: nothing is fetched from any RPKI repository, validator or route collector, so the verdict holds for that list only. It applies RFC 6811 section 2 word for word: a VRP covers the route when its prefix length is no longer than the route's and the two agree on every bit of the VRP's length, and matches when it also allows the route's length and names the route's origin; Valid means at least one VRP matches, Invalid that at least one covers and none matches, NotFound that none covers. AS 0 VRPs cover and never match (RFC 6811 section 2, RFC 6483 section 4), a route with origin AS 0 is refused as malformed (RFC 7607 section 2), and every VRP whose maxLength reaches past its own prefix is reported with the number of prefixes it authorises, the case RFC 9319 asks operators to avoid. Behaviour is pinned by 40 golden vectors.
- RFC 6811: BGP Prefix Origin ValidationCovered, Matched and the three states; NONE and AS 0 (section 2), read 2026-10-19
- RFC 9582: A Profile for Route Origin Authorizations (ROAs)maxLength's range and meaning (section 4.3.2.2) and the IPv6 example ROA (Appendix A); obsoletes RFC 6482, read 2026-10-19
- RFC 6483: Validation of Route Origination Using the Resource Certificate PKI and ROAsAS 0 ROAs as a disavowal of routing (section 4), read 2026-10-19
- RFC 7607: Codification of AS 0 ProcessingA route with AS 0 in its AS_PATH is malformed (section 2), read 2026-10-19
- RFC 9319: The Use of maxLength in the RPKIMinimal ROAs and the advice to avoid maxLength (section 5), read 2026-10-19
- RFC 8416: SLURMprefixAssertions as VRPs and the members a SLURM file may use (sections 3.1, 3.2, 3.4.1), read 2026-10-19
- RFC 5396: Textual Representation of AS Numbersasplain, asdot+ and asdot (section 2), read 2026-10-19