All integrationsMonitoring
RIPEstat
Look up any IP address, prefix or AS number with the RIPE NCC's public Internet data: who holds it and their abuse contact, WHOIS records, where it is registered and where it is used, how it is routed and how much of the Internet sees it, its RPKI status, its BGP neighbours and routes, its DNS names and whether it is on a spam blocklist.
- actions
- 20
Actions
Steps a workflow can run in RIPEstat.
- Find abuse contactFind the email address to report abuse from an IP address, prefix or AS number to (spam, attacks, scanning), and the regional registry responsible for it. When none is on record the step still succeeds, with found set to false. No API key required.
- Look up WHOISRead the WHOIS records for an IP address, prefix or AS number from whichever regional registry holds it (RIPE NCC, ARIN, APNIC, LACNIC or AFRINIC), with the name, description, country, organisation, status and dates picked out, every line of each record, and matching route objects from routing registries. No API key required.
- Get ASN overviewFind out who holds an AS number, whether it announces any prefixes, and which IANA block it comes from. An AS number nobody holds comes back with registered set to false. No API key required.
- Find where a resource is registeredFind the country an IP address, prefix or AS number is registered to, from the regional registries' own statistics, on any day since 2005. This is the holder's country on paper; use Geolocate for where the addresses are used. No API key required.
- Get address space hierarchySee the RIPE Database address blocks around an address, prefix or range: the record matching it, the block directly above it (usually the provider's allocation) and the blocks directly below it (the assignments inside), each with its name, status, country and maintainers. Covers address space the RIPE NCC manages (Europe, the Middle East and Central Asia). No API key required.
- Get network for an IP addressFind the routed prefix an IP address belongs to and the AS number announcing it, from RIPE's BGP route collectors. An address nobody routes (a private one, say) comes back with routed set to false. No API key required.
- Get prefix overviewFind out whether a prefix is announced, which AS numbers announce it and who holds them, the prefixes related to it, and the IANA block it comes from. An IP address, or a prefix not announced on its own, is answered for the announced prefix covering it. No API key required.
- List prefixes an ASN announcesList every IPv4 and IPv6 prefix an AS number announced in a time window (the last two weeks unless you set one), with when each was first and last seen. Run on a schedule, it shows when a network starts or stops announcing address space. No API key required.
- List ASN neighboursList the AS numbers seen next to an AS number in BGP paths (its upstreams, peers and customers), busiest first, with how many paths show each one. No API key required.
- Get routing statusGet how a prefix or AS number is routed: when it was first and last seen in BGP, how many of RIPE's BGP peers see it, the AS numbers originating a prefix and whether route objects back them, the prefixes around it, and for an AS number how much address space it announces. No API key required.
- Look up BGP routesSee the live BGP routes RIPE's route collectors hold for a prefix (a looking glass): each peer's AS path, origin, next hop and communities, collector by collector, plus every origin AS number seen. Near real time. No API key required.
- Check visibilityCheck how much of the Internet sees a prefix or AS number: how many of RIPE's full-table BGP peers see it, in IPv4 and IPv6, collector by collector, and which peers do not. A drop is the first sign of an outage or a hijack. No API key required.
- List related prefixesList the routed prefixes that overlap an address, prefix or range (larger or smaller ones) or sit right next to it, with the AS number announcing each. No API key required.
- Check RPKI validityCheck whether RPKI allows an AS number to announce a prefix: valid, invalid (wrong AS number or too specific) or unknown (no ROA), with the ROAs that decide it. Networks that check RPKI drop invalid announcements. No API key required.
- GeolocateFind where an IP address or prefix is used: country, city and coordinates, from MaxMind's GeoLite2 data, with the share of a prefix at each location. Publishing the results outside your organisation falls under MaxMind's GeoLite2 licence. No API key required.
- Look up DNSResolve a hostname to its IP addresses, following any aliases, or an IP address to its hostnames (reverse DNS), checking whether the hostname points back to the address as mail servers expect. No API key required.
- Check blocklistsCheck whether an IP address is on the DNS blocklists RIPEstat asks (Spamhaus, Abusix, SpamRATS and SPFBL), for spam, malware or abuse. The lookups take up to a minute or two; the step waits for them and says which blocklists did not answer. No API key required.
- List a country's resourcesList the AS numbers and the IPv4 and IPv6 address space registered to a country, from the regional registries' statistics, today or on a past day, with how many there are of each. No API key required.
- Count a country's ASNsCount the AS numbers registered to a country and how many of them are routed (seen announcing anything), now or at a past moment, optionally listing both groups. No API key required.
- Search RIPEstatFind AS numbers, prefixes, domains and related resources by a name or part of one, such as a company name or the start of an address. Each result's value can go straight into another RIPEstat step. No API key required.
No actions match that.
Automate RIPEstat with Lodol.
Connect RIPEstat and ask your AI for your first workflow.
Free plan, no credit card