RDAP and IPWHOIS.io

RDAP

Actions

• Look up a domainLook up everything a domain's registry publishes about it: who registered it, through which registrar, when it was registered and when it expires, which nameservers it uses, whether it is signed with DNSSEC, whether it is locked against transfer, and where to report abuse. This is WHOIS's replacement, so the answer is structured fields rather than text to parse, and the days remaining until expiry are worked out for you. The right registry is found automatically from IANA's own directory, so any of the roughly 1,200 top-level domains that publish RDAP will answer. A whole URL or a host name works as it stands: no registry holds a record for 'www.example.com', so the step walks up to the name that is registered and says it did. No account or API key required.
• Check whether a domain is registeredAnswer one question about a domain: is it taken? Returns a true or false a condition can branch on, and when the domain is taken it also says when it expires, how many days that is, and whether its status says it is on its way back onto the market. Use it to screen a list of names, to watch for a competitor's domain lapsing, or in a condition before the rest of a workflow runs. RDAP answers whether the registry holds a record, which is not quite the same as whether you can buy the name, and the step says so. No API key required.
• Look up domains in bulkLook up many domains in one step and get one row per domain: whether it is registered, its registrar, its expiry date, how many days that is, its status and its nameservers. The step also names the domain expiring soonest, which is the whole answer for a renewal reminder. Use it for a portfolio, a spreadsheet column, or a list of names you are considering buying. RDAP publishes no bulk route, so this is one request per domain - but the registry directory is read once for the whole list, the requests are paced, and a domain that fails is reported on its own row instead of stopping the step. Up to 50 domains at a time. No API key required.
• Look up a nameserverLook up a nameserver as the registry holds it, including the glue addresses it is registered at and whether it is locked against change. This is the registry's record rather than what DNS answers today, which is exactly what you want when checking that a delegation was set up correctly. A nameserver only exists as a record of its own where it has glue, so a working nameserver can legitimately have none, and the step says so rather than failing. No API key required.
• Look up an entityLook up a contact, an organisation or a registrar by its handle, and get its name, email address, phone number and postal address as plain fields rather than as the nested jCard array RDAP sends them in. Handles come back on every other lookup - a domain's registrar, a network's abuse contact - so this is how a workflow follows one to the organisation behind it. The handle's own suffix says which registry to ask, so nothing else is needed for a tagged handle. No API key required.
• Look up an IP addressFind out who an IP address is registered to. Returns the network the address falls inside, its CIDR range, the organisation that holds it, what kind of allocation it is, and where to report abuse from it. This is the step for turning an address out of a server log into an owner: an attacker's address into a network operator to report, or a visitor's address into the company behind it. The right regional internet registry - ARIN, RIPE NCC, APNIC, LACNIC or AFRINIC - is found automatically. IPv4 and IPv6 both work. No API key required.

IPWHOIS.io

Actions

• Look up an IP addressGeolocate an IP address: the continent, country, region and city it is in, its coordinates, postal code and time zone, the network that runs it, and the country reference data that comes with it - capital, dialling code, flag and EU membership.
• Look up this workflow's IP addressLook up the address your workflow's requests go out from, and where it is, which is what you need when a third-party API asks you to allow-list the address your calls arrive from.
• Look up several IP addressesGeolocate a list of addresses in one step and get a row for each with where it is and who runs it. Addresses that cannot be located are reported alongside the ones that can, so one private address in the list does not fail the step.
• Check whether an IP address can be locatedAnswer whether an address can be located at all, and say why not when it cannot: a typo, or an address in a range reserved by the IANA such as a private network or a loopback. It answers no rather than failing.
• Check an IP address's countryAnswer whether an address is in one of the countries you name, the check behind sending someone to the right regional site, gating a feature by market, or flagging a sign-up from outside the countries you sell in.
• Check whether an IP address is in the EUAnswer whether an address is in the European Union, the check behind showing a cookie banner, applying VAT, or choosing where to store someone's data. IPWHOIS.io keeps the membership list itself, so your workflow does not have to.