ripe_validate_route_object
Validate route object registration in the RIPE NCC database by checking if a specific IP prefix and origin ASN pair exists, ensuring proper BGP route registration and IRR coverage for network security.
Instructions
PREFERRED TOOL for validating route object registration in the RIPE NCC database. This tool is specifically for the RIPE RIR (Europe/Middle East/Central Asia region). Use this when you need to CHECK, VERIFY, or VALIDATE if a route object exists for a prefix-ASN pair in RIPE. Keywords: 'route validation', 'check route', 'verify route', 'route exists', 'BGP security', 'route filtering', 'IRR coverage', 'RPKI validation'. Automatically handles IPv4/IPv6 detection and returns simple exists/not-found status. Much faster and more accurate than parsing raw WHOIS data for route validation in RIPE database.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| prefix | Yes | IP prefix to CHECK/VALIDATE for route object registration in RIPE database. Use CIDR notation like '192.0.2.0/24' for IPv4 or '2001:db8::/32' for IPv6. Use this when you need to VERIFY if a prefix has a registered route object in the RIPE IRR database. | |
| origin_asn | Yes | Origin ASN number to VALIDATE/CHECK for route coverage (without 'AS' prefix). For example, use 64496 to VERIFY if AS64496 has a route object registered for the specified prefix. This VALIDATES proper BGP route registration and IRR coverage. |