Wayback Machine and RDAP

Wayback Machine

Actions

• Check if a page is archivedAsk the Wayback Machine whether it has a copy of a page, and get a link to the nearest one. Point it at a date to ask for the copy closest to that moment instead of the most recent. This is the quickest check to run before following a link that may be dead, or to decide whether the rest of a workflow has anything to work with. No API key required.
• Check several pages at onceRun the same archived-or-not check over a list of URLs and get one row per link, with a Wayback link for the ones that have a copy. Built for auditing the links in a page, a document or a spreadsheet: a URL the archive cannot answer for is reported as unarchived rather than failing the step. Up to 50 URLs. No API key required.
• Get a link to a page as it wasTurn a URL and a date into a link to that page as it looked then, so a message, a document or a citation can point at the archived copy rather than at a page that has since changed. The archive picks the capture nearest the date and says which one it chose. No API key required.
• Get a snapshot's detailsEverything the archive's index records about one capture: when it was taken, what the server said, what kind of file it was, how much was stored, and the content fingerprint that says whether two captures hold the same bytes. Ask for the first capture, the most recent one, or the one closest to a date. No API key required.
• List a page's snapshotsEvery capture of one page, newest first, narrowed to the dates, the kind of response and the kind of file you care about. A busy page is captured many times a day, so thin the list to one capture per day, month or year when you want a timeline rather than every crawl. No API key required.
• List a page's content changesOnly the captures where a page actually changed, with the thousands of identical captures in between left out. This is how you find when a policy was rewritten, when a price moved or when a claim disappeared, without reading every crawl. No API key required.

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.