Calculadora de validação de origem de rota
Cole uma rota (prefixo e AS de origem) e os VRPs que você tem, e veja o estado definido pela RFC 6811 (Valid, Invalid ou NotFound) com o motivo VRP por VRP: quais VRPs cobrem a rota, quais dão match e por que os outros falham. AS 0 e maxLength são tratados como as RFCs dizem, em IPv4 e IPv6, e nada é buscado na rede.
RedesCada linha traz um prefixo, um maxLength opcional e o AS, nessa ordem; o AS pode vir em asplain (AS64496 ou 64496) ou em asdot (AS1.10). O maxLength também pode vir colado ao prefixo, depois de um hífen (203.0.113.0/24-26, como a RFC 9319 escreve). Sem maxLength, só o prefixo exato fica autorizado. Um AS escrito com o prefixo AS pode ficar em qualquer posição da linha (AS64496,192.0.2.0/24,24). Um # começa um comentário. Também dá para colar o JSON de um SLURM da RFC 8416: os prefixAssertions dele viram os VRPs.
Roda no seu navegador e não busca nada: nenhum repositório RPKI, nenhum validador, nenhum route collector. O veredito vale para os VRPs que você colou e para nenhuma outra lista.
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