bgp-registry-intel

Use the rpki_validate tool with both the prefix and the origin AS, since validation always applies to the pair. The result is valid, invalid with an AS or length reason, not-found, or validation-unavailable, each with a distinct operational meaning.

RPKI not-found means no ROA exists for the prefix, which is the normal case for most of the internet. It is not a hijack or misconfiguration and should not be reported as a security finding.

Use registry_abuse_contact on the address to get the published abuse contact from RDAP. If none is published, look up the covering allocation with registry_lookup or check peering_network for a technical contact.

No credentials are required. Every data source — the RIPE RPKI validator, RDAP, PeeringDB, RIPEstat, and RIPE Atlas — is a public unauthenticated API, and the skill is strictly read-only.

Use Globalping when you need active measurements, such as testing reachability from multiple countries. This skill only looks up registry and routing data; it does not run measurements or quick ASN/geolocation enrichment, which belong to gtrace.

Private and reserved addresses are rejected locally before any request is sent, because sending internal addressing to a public registry would disclose internal network information even if the lookup fails.