29 services carry this tag in their source record. Tags come from the provider, not from us — a tag is a claim about what the service does, not proof that it does it well.
Run the mail configuration check (MX, SPF, DMARC) on up to 20 domains in one request. Results keep the input order, and items that fail for a technical reason come with a token for a free retry. Use when an agent must au...
IP intelligence. One call for everything about an IP address: its type (public, private, loopback, carrier-grade NAT), the registry record (holding organisation, network name and range, registration country, abuse contac...
WHOIS Lookup API. Retrieve domain registration data including registrar, WHOIS server, creation date, expiration date, updated date, nameservers, domain status, and privacy/redaction signals. Useful for agents, developer...
Reverse-resolve an IPv4 or IPv6 address to its PTR hostname(s). No PTR record returns an empty list. This is reverse DNS (PTR) — not ENS or onchain name resolution.
Check the TLS certificate a domain serves on port 443: whether it chains to a trusted root, matches the name (RFC 9525) and when it expires, with issuer, chain, key and signature algorithm, TLS version and coded findings...
Inspect a PDF without downloading the whole thing into your model: page count, title, author, subject, creator, producer, creation/modification dates, encryption flag, and byte size. Body: {"url":"https://…/file.pdf"}.
IP address owner and network (RDAP + reverse DNS): Who holds a public IPv4/IPv6 address, from the Regional Internet Registry RDAP record: network name, handle, CIDR, address range, country, holding organisation, abuse ma...
Reverse DNS (PTR) lookup: the hostname for an IPv4 or IPv6 address, with the arpa name and TTL. Identify servers, mail hosts and hosting providers from an IP. $0.01 per lookup.
Reverse DNS (PTR) of an IPv4 address as answered by Cloudflare 1.1.1.1: the hostname(s), TTL and response code, plus whether the PTR's forward A record points back (forward-confirmed reverse DNS). Compare resolvers for s...
Reverse DNS (PTR) of an IPv4 address as answered by Google 8.8.8.8: the hostname(s), TTL and response code, plus whether the PTR's forward A record points back (forward-confirmed reverse DNS). Compare resolvers for stale...
Reverse DNS (PTR) of an IPv4 address as answered by AliDNS 223.5.5.5: the hostname(s), TTL and response code, plus whether the PTR's forward A record points back (forward-confirmed reverse DNS). Compare resolvers for sta...
Reverse DNS (PTR) of an IPv4 address as answered by OpenDNS: the hostname(s), TTL and response code, plus whether the PTR's forward A record points back (forward-confirmed reverse DNS). Compare resolvers for stale or fil...
Reverse DNS (PTR) of an IPv4 address as answered by AdGuard DNS: the hostname(s), TTL and response code, plus whether the PTR's forward A record points back (forward-confirmed reverse DNS). Compare resolvers for stale or...
Reverse DNS (PTR) of an IPv4 address as answered by DNSPod (doh.pub): the hostname(s), TTL and response code, plus whether the PTR's forward A record points back (forward-confirmed reverse DNS). Compare resolvers for sta...
Reverse DNS (PTR) of an IPv4 address as answered by NextDNS: the hostname(s), TTL and response code, plus whether the PTR's forward A record points back (forward-confirmed reverse DNS). Compare resolvers for stale or fil...
Reverse DNS (PTR) of an IPv4 address as answered by Mullvad DNS: the hostname(s), TTL and response code, plus whether the PTR's forward A record points back (forward-confirmed reverse DNS). Compare resolvers for stale or...
Reverse DNS (PTR) of an IPv4 address as answered by DNS.SB: the hostname(s), TTL and response code, plus whether the PTR's forward A record points back (forward-confirmed reverse DNS). Compare resolvers for stale or filt...
Reverse DNS (PTR) of an IPv4 address as answered by CleanBrowsing (security filter): the hostname(s), TTL and response code, plus whether the PTR's forward A record points back (forward-confirmed reverse DNS). Compare re...
Change watch for reverse dns via cloudflare: runs the check, compares it with the result from your previous call for the same ip (kept 90 days) and returns the current answer, changed true/false, the fields that changed...
Change watch for reverse dns via google: runs the check, compares it with the result from your previous call for the same ip (kept 90 days) and returns the current answer, changed true/false, the fields that changed with...
Change watch for reverse dns via alidns: runs the check, compares it with the result from your previous call for the same ip (kept 90 days) and returns the current answer, changed true/false, the fields that changed with...
Change watch for reverse dns via opendns: runs the check, compares it with the result from your previous call for the same ip (kept 90 days) and returns the current answer, changed true/false, the fields that changed wit...
Change watch for reverse dns via adguard: runs the check, compares it with the result from your previous call for the same ip (kept 90 days) and returns the current answer, changed true/false, the fields that changed wit...
Change watch for reverse dns via dnspod: runs the check, compares it with the result from your previous call for the same ip (kept 90 days) and returns the current answer, changed true/false, the fields that changed with...