Domain Inspector

Everything about a domain in one row. Give the Domain Inspector a list of domains and it returns each one's registrar, registration & expiry dates, status codes and nameservers, full DNS records, and SSL certificate details as clean JSON, CSV, Excel or XML. No login, no API key — fast and reliable for bulk domain checks.

What does the Domain Inspector do?

The Domain Inspector takes a list of domains (or URLs) and returns a single structured record per domain combining registration lifecycle data, live DNS records and TLS certificate details. Toggle each data source on or off and inspect thousands of domains in one run — ideal for portfolio monitoring, expiry alerting and security audits.

Features

• 🗂️ Registration data — registrar, creation/updated/expiry dates, EPP status codes and nameservers
• 🌐 Live DNS — A, AAAA, MX, NS, TXT and CNAME records resolved at run time
• 🔒 SSL certificate — issuer, subject, validity window, days to expiry and trust status
• ⚙️ Toggle sources — enable only RDAP, DNS or SSL as needed
• 📦 Bulk — inspect many domains in parallel, each time-capped so one slow lookup can't stall a run

What you get

One row per domain:

{
  "input": "google.com",
  "domain": "google.com",
  "registrableDomain": "google.com",
  "registrar": "MarkMonitor Inc.",
  "createdDate": "1997-09-15T04:00:00Z",
  "updatedDate": "2024-08-01T04:00:00Z",
  "expiryDate": "2028-09-14T04:00:00Z",
  "statuses": ["clientTransferProhibited"],
  "nameservers": ["ns1.google.com", "ns2.google.com"],
  "dns": { "a": ["142.250.72.14"], "mx": ["smtp.google.com"], "ns": ["ns1.google.com"], "txt": ["v=spf1 ..."] },
  "ssl": { "issuer": "Google Trust Services", "validTo": "2026-09-01T00:00:00.000Z", "daysToExpiry": 52, "authorized": true },
  "error": null
}

Output schema

Input

{
  "domains": ["google.com", "example.co.uk", "apify.com"],
  "includeRdap": true,
  "includeDns": true,
  "includeSsl": true
}

Use cases

• Portfolio monitoring — track registrar, expiry and nameservers across a domain estate.
• Expiry & SSL alerting — flag domains or certificates nearing expiry.
• Security audits — review DNS records, status codes and certificate trust in bulk.
• Due diligence — verify ownership signals and infrastructure for a list of domains.
• Lead enrichment — append registration and DNS data to a prospect list.

How to inspect domains

1. Add the Domain Inspector to your Apify account.
2. Paste your domains (one per line — URLs are accepted too).
3. Toggle includeRdap, includeDns and includeSsl as needed.
4. Click Run.
5. Export the dataset as JSON, CSV, Excel or XML, or pull it via the Apify API.

Need more web-diagnostics data?

• Bulk URL Status Checker — check thousands of links for status, redirects and SSL.
• Website Contact Scraper — extract emails, phones and social links from websites.
• Bulk Image Downloader — fetch and store images at scale from a URL list.

FAQ

Do I need an account or API key? No. There's no login or API key required — just paste your domains and run.

How many domains can I inspect per run? There's no fixed cap. maxConcurrency controls how many domains are looked up in parallel, and each domain is time-capped so one slow lookup can't stall a bulk run.

How does billing work? You pay only per domain you get, so small runs stay cheap. See the Pricing tab for current rates.

What's the output format? A dataset with one row per domain — registrar, lifecycle dates, statuses, nameservers, DNS records and SSL details — exportable as JSON, CSV, Excel or XML.

Can I choose which data to collect? Yes. Toggle includeRdap, includeDns and includeSsl to pick which sources to query, and use maxConcurrency to tune throughput.

Is this only public data? Yes. It collects only publicly available registration, DNS and certificate data.

Can I connect this to other tools? The Domain Inspector can be connected with almost any cloud service or web app thanks to integrations on the Apify platform. It works with Make, Zapier, Slack, Airbyte, GitHub, Google Drive and many more, plus the Apify API, JavaScript/Python clients and MCP. Or use webhooks to trigger an action whenever a run finishes.

Notes

Original clean-room implementation. Registration data comes from RDAP (the modern WHOIS); a few TLDs expose limited fields. Collects only publicly available registration, DNS and certificate data; you are responsible for compliance with the relevant terms.

You pay only for what the run returns. Set a maximum cost per run and it stops cleanly at that limit.