How do I connect RDAP to Lodol?

Authenticate RDAP once from your workspace and every action and trigger it supports becomes available to drop into a workflow. There is no glue code to write or maintain.

All integrations

RDAP

UtilitiesCompliance & Security

Look up who owns a domain, an IP address or a network from a workflow, with no account and no API key. RDAP is the structured replacement for WHOIS that every domain registry and every regional internet registry now runs, so the answer comes back as fields you can branch on rather than text to parse. Read a domain's registrar, registrant, nameservers, DNSSEC keys, transfer locks and expiry date; check whether a name is taken; watch a portfolio of up to 50 domains in one step and see which expires soonest; turn an IP address or an AS number into the organisation behind it; and find the abuse address for any of them, ready to send an email to. Search a registry for domains, nameservers, contacts and organisations where it offers search. Read IANA's own directories to see which top-level domains publish RDAP and which server answers for each. Every action reads: RDAP has no route that changes anything.

Get Started Browse all integrations

20 actions

Actions

Steps your workflow can run in RDAP.

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.

Look up an AS numberLook up an autonomous system number and find the network operator behind it: the organisation's name, the country, the range the number sits in and where to report abuse. An AS number is how a network is identified on the public internet, so this is the step for turning a BGP route or a traffic report into a company you can contact. The right regional internet registry is found automatically. No API key required.

Look up a top-level domainLook up a top-level domain's own record in IANA's root zone: the organisation that runs it, when it was delegated and last changed, the nameservers that serve it and its DNSSEC keys. The step also says whether the registry behind it publishes RDAP, and where, so you can tell in one call whether a domain under it can be looked up at all. Every delegated top-level domain is in the list, not only the ones with an RDAP server. No API key required.

Find an abuse contactFind where to report abuse coming from a domain, an IP address or an autonomous system, and get the address as a plain field ready to send an email to. This is the question RDAP is asked most often and the hardest one to answer by hand: the abuse address is not on the object itself but on a contact nested inside its registrar or its network holder. The step walks to it, and falls back to the registrar's or the holder's own address when no abuse contact is published, saying which of the two it found. No API key required.

Search domains by nameSearch one registry for domains whose name matches a pattern, with at most one '*' in it: 'nic.fr' finds that exact domain, 'exam*.fr' finds every .fr domain starting 'exam'. The registry is worked out from the pattern's top-level domain unless you choose one. Search is optional in RDAP and most registries do not offer it - ICANN does not permit public domain search at gTLD registries at all - so the step reports 'this registry does not offer that search' as a result rather than an error, and a workflow can carry on. No API key required.

Search domains by nameserverSearch one registry for the domains it has delegated to a nameserver. Use it to see what a hosting provider's nameserver is serving inside a registry, or to find what else moves if a nameserver changes. Very few registries implement this search, so the step reports 'this registry does not offer that search' as a result rather than an error. No API key required.

Search domains by nameserver IP addressSearch one registry for the domains it has delegated to any nameserver answering at an IP address. Use it to find everything pointed at one server when that server is being retired or has been compromised. Very few registries implement this search, so the step reports 'this registry does not offer that search' as a result rather than an error. No API key required.

Search nameservers by nameSearch one registry for nameserver records whose host name matches a pattern, with at most one '*' in it. The registry is worked out from the pattern's top-level domain unless you choose one. Very few registries implement this search; to read one nameserver you already know the name of, use Look up a nameserver instead, which every registry answers. The step reports an unsupported search as a result rather than an error. No API key required.

Search nameservers by IP addressSearch one registry for the nameservers registered at an IP address. This is the reverse of a nameserver lookup: it turns a server's address into the host names the registry knows are answering on it, which is how to find every name a machine is serving under before decommissioning it. AFNIC's .fr registry answers this one; most others do not, and the step reports that as a result rather than an error. No API key required.

Search entities by nameSearch one registry for contacts and organisations by name, with at most one '*' standing for any trailing characters. This is the search that actually works across the internet: all five regional internet registries answer it, so searching ARIN for a company name returns every contact record it holds for them, each with an email address and a handle you can follow. Use it to find an organisation's network contacts without knowing a single one of its addresses. No API key required.

Search entities by handleSearch one registry for contacts and organisations whose handle matches a pattern, with at most one '*' standing for any trailing characters. Use it when you have part of a handle rather than all of it, or to list every handle a registry issued under a prefix. A tagged handle names its own registry, so the server field can be left empty for one of those. All five regional internet registries answer this search. No API key required.

Read a server's terms and capabilitiesRead one RDAP server's own help response: its terms of use, any rate limit it publishes, its copyright notice, and which optional extensions it implements. Every RDAP server has to serve this, and it is the only place a server states its own rules, so it is worth reading once before building against a registry you have not used. The extensions list is what says whether a server offers search, reverse search or history at all. No API key required.

Find the RDAP server for somethingSay which RDAP server is authoritative for a domain, an IP address, an AS number or an entity handle - and which of IANA's five directories said so, and on what. This is the routing every other action does before it asks anything, exposed on its own. Use it to check whether a top-level domain publishes RDAP before building a workflow around it, to see which regional registry an address belongs to without querying the registry, or to fill the server field of a search step. No API key required.

List top-level domains with RDAPList every top-level domain that publishes RDAP, with the server that answers for it, optionally filtered to the ones whose name contains a string. This is IANA's own directory, and it is what decides whether a domain can be looked up at all, so it is the honest way to check coverage before building a workflow over a list of domains whose top-level domains you do not control. The result carries the date IANA last published the directory. No API key required.

Read a bootstrap registryRead one of IANA's five RDAP directories whole: the top-level domains, the IPv4 and IPv6 address blocks, the autonomous system number ranges, or the entity handle suffixes - each with the servers that answer for them. This is where to see which regional registry holds which address ranges, or which operator runs RDAP for a group of top-level domains. The result carries the date IANA last published that directory, so a workflow can notice when it changes. No API key required.