RPKI Validation State Explainer
Explain the RFC 6811 Valid, Invalid, and NotFound origin-validation states and their operational limits offline.
This tool handles input and primary processing in your browser and is designed not to send the input to QuickKit’s server.
Router acceptance
The state alone does not decide acceptance; local routing policy does.
What this does not prove
It does not validate AS_PATH, route ownership, reachability, or legitimacy.
How it works
Explains Route Origin Validation states from already-produced validator output. Valid means at least one covering VRP authorizes both the origin ASN and route length. Invalid means the route is covered by VRP data but no covering VRP authorizes both. NotFound means no VRP covers the route. These states check route origin authorization only—not the AS_PATH, route legitimacy, reachability, or whether a router will accept it. This tool performs no network request, repository sync, ROA lookup, or live validation.