Domain Health Checker – Expiry, DNS, SPF/DMARC, SSL, HSTS
Pricing
from $3.20 / 1,000 domain checkeds
Domain Health Checker – Expiry, DNS, SPF/DMARC, SSL, HSTS
Bulk-check domains: expiry and registrar via RDAP (no WHOIS personal data), A/AAAA/MX/NS/CAA, SPF validity and lookup count, DMARC policy, common DKIM selectors, SSL certificate (issuer, days to expiry, hostname match, TLS version), HTTP→HTTPS redirect and HSTS. Health score 0–100 with fix codes.
Pricing
from $3.20 / 1,000 domain checkeds
Rating
0.0
(0)
Developer
Tesselyn
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a month ago
Last modified
Categories
Features
Share
Check the health of many domains at once: domain expiry and registrar (from the official RDAP registry data, no WHOIS personal data), DNS records, email authentication (SPF, DMARC, DKIM), the SSL/TLS certificate and HTTPS redirect and HSTS. Each domain gets a health score from 0 to 100, a grade, and a list of issues, each with a fix.
⚠️ Automated, informational results, provided "as is". Not legal, compliance or security advice. A good score does not guarantee email delivery, protection against spoofing or that a domain will not expire. See Terms of use.
What does the Domain Health Checker check?
| Area | What you get | Example issue codes |
|---|---|---|
| Registration (RDAP) | Registrar name and IANA ID, created / expiry / last-changed dates, days until expiry, registry status, nameservers, DNSSEC | DOMAIN_EXPIRED, DOMAIN_EXPIRES_30D, DNSSEC_NOT_SIGNED |
| DNS | A, AAAA, MX, NS and CAA records | DNS_NO_NS, DNS_SINGLE_NS, DNS_NO_ADDRESS, CAA_MISSING |
| SPF | The record, whether it is valid, number of DNS lookups (the 10-lookup limit, includes resolved recursively), the all qualifier, broken includes | SPF_MISSING, SPF_MULTIPLE_RECORDS, SPF_TOO_MANY_LOOKUPS, SPF_PASS_ALL, SPF_WEAK_ALL |
| DMARC | Policy (p), subdomain policy, pct, alignment, whether aggregate/forensic reports are set (inherited from the parent domain for subdomains) | DMARC_MISSING, DMARC_POLICY_NONE, DMARC_NO_REPORTING |
| DKIM | Keys found at 10 common selectors (optional) | DKIM_NOT_FOUND_COMMON (informational) |
| SSL/TLS | Issuer, valid from/to, days to expiry, hostname match, trusted chain, TLS version | TLS_CERT_EXPIRED, TLS_CERT_EXPIRES_14D, TLS_HOSTNAME_MISMATCH, TLS_UNTRUSTED, TLS_OLD_VERSION |
| HTTP | http → https redirect and the redirect chain, HTTPS status, HSTS (max-age, includeSubDomains, preload) | HTTP_NO_HTTPS_REDIRECT, HSTS_MISSING, HSTS_SHORT_MAX_AGE |
Scoring: the score starts at 100. Each issue subtracts points by severity: critical −25, high −12, medium −6, low −2, info 0. Grades: A ≥ 90, B ≥ 80, C ≥ 65, D ≥ 50, F below 50. A run-summary row adds the average score, the grade distribution and the most common issues across your list.
About DKIM: DKIM can't be fully checked without the selector your mail provider uses. We try common selectors (google, selector1, selector2, default, k1, s1, s2, dkim, mail, smtp). Not finding one is reported as information only and does not lower the score.
Use cases for the domain health checker
- Email deliverability: find missing or invalid SPF records, SPF records over the 10-lookup limit and DMARC policies stuck at
p=none. - Renewal monitoring: see days until domain expiry and SSL certificate expiry for a whole portfolio in one table.
- Website security basics: confirm http → https redirects, HSTS and a trusted, hostname-matching certificate.
- Agencies and IT teams: produce a scored health snapshot of client or company domains, with a fix for each issue.
- Due diligence and inventories: a structured snapshot of a domain list for security or M&A reviews, or for AI agents and automations (API, MCP, Make, Zapier or n8n).
Ready-made example tasks
Open one, check the input and click Try to run a copy in your own account:
- Check SPF, DMARC and DKIM records for a list of domains
- Monitor domain and SSL certificate expiry dates
- Audit HTTPS redirects, HSTS and SSL for websites
How to check domain health
- Paste your domains (or URLs; the domain is extracted and
www.is removed). The input is prefilled with example.com, wikipedia.org and apify.com, so the first run works right away. - Optionally switch off RDAP, the website checks or the DKIM selector probe.
- Run it, then open the Overview, Details or Run summary view, or download CSV, Excel or JSON.
Input example
{ "domains": ["example.com", "mycompany.io", "https://www.shop.example.net/"], "checkRdap": true, "checkWebsite": true }
Output example
One row per domain. This row is from a real run on the prefilled input (October 2026, shortened; results change as domains are updated):
{"type": "domain", "domain": "wikipedia.org", "healthScore": 98, "grade": "A","rdap": { "registrar": "MarkMonitor Inc.", "registrarIanaId": "292", "expires": "2027-01-13T00:12:14Z","expiresInDays": 84, "dnssecSigned": false, "nameservers": ["ns0.wikimedia.org", "ns1.wikimedia.org", "ns2.wikimedia.org"] },"dns": { "a": ["208.80.154.224"], "mx": ["10 mx-in1001.wikimedia.org", "10 mx-in2001.wikimedia.org"],"caa": ["0 issue \"letsencrypt.org\"", "0 issue \"pki.goog\""] },"email": { "spf": { "record": "v=spf1 include:_cidrs.wikimedia.org ~all", "valid": true, "lookupCount": 1, "allQualifier": "~" },"dmarc": { "present": true, "policy": "reject", "aggregateReports": true, "aggregateReportDomains": ["wikimedia.org"] },"dkim": { "foundSelectors": [] } },"ssl": { "issuer": "Let's Encrypt", "expiresInDays": 74, "hostnameMatch": true, "trusted": true, "tlsVersion": "TLSv1.3" },"http": { "httpRedirectsToHttps": true, "finalUrl": "https://www.wikipedia.org/","hsts": { "present": true, "includeSubDomains": true, "preload": true } },"issues": [{ "code": "DOMAIN_EXPIRES_90D", "severity": "low", "category": "domain", "fix": "Make sure auto-renew is on (expires within 90 days).", "detail": "84 days" },{ "code": "DNSSEC_NOT_SIGNED", "severity": "info", "category": "domain", "fix": "Consider enabling DNSSEC at your registrar and DNS host." },{ "code": "DKIM_NOT_FOUND_COMMON", "severity": "info", "category": "email", "fix": "No DKIM key at common selectors. This is not proof DKIM is missing; check your mail provider's selector." }],"charged": true}
In the same run, example.com scored 78 (C: no http → https redirect, no HSTS, no CAA record, no DMARC reporting) and apify.com scored 100 (A). The run also writes a run-summary row with the average score, the grade distribution and the most common issues.
How much does it cost to check domain health?
Pay per event: $0.004 per domain checked (domain-checked, = $4 per 1,000 domains), one event per domain that exists and got a full report. Domains that don't exist (NXDOMAIN), DNS failures, timeouts, input errors and the summary row are free. See the Pricing tab for the current price. Set the run's maximum charge to cap spend: the Actor stops starting new domains when the cap is reached.
Examples at the current price: 10 domains ≈ $0.04, 100 domains ≈ $0.40, 1,000 domains ≈ $4, plus the small per-run start fee. A weekly check of 50 domains costs about $0.20 per run.
Recommended schedule and monitoring
Domains, certificates and DNS records expire or change on their own schedule, so a regular check catches problems before users or mail servers do.
- Weekly suits most portfolios: save your domain list as a task and attach an Apify Schedule. A weekly run always falls inside the 14-day
TLS_CERT_EXPIRES_14Dwindow, so an expiring certificate is flagged at least once before it lapses. - Daily for domains where an outage is costly, or during a DNS or mail-provider migration.
- Add a webhook (email, Slack or your own endpoint) and alert on issue codes such as
DOMAIN_EXPIRES_30D,TLS_CERT_EXPIRES_14D,SPF_TOO_MANY_LOOKUPSor a drop inhealthScore.
Responsible use
- The Actor identifies itself as
TesselynDomainHealthBot/1.0 (+https://apify.com/tesselyn). - Per domain it makes DNS queries, one TLS handshake on port 443 and a few header-only HTTP requests to the home page (at most 5 redirects, with a pause between requests). It downloads no page content and does not crawl.
- RDAP servers are found through the official IANA bootstrap file. Each RDAP server gets at most one request at a time, with at least 1 s between requests.
- Only public hostnames are accepted. IP addresses,
localhost, internal names and hostnames that resolve to private, loopback or cloud-metadata addresses are refused. - No proxies, no IP rotation and no attempt to get around rate limits.
Terms of use
These terms add to the Apify Standard Actor Contract, which governs your use of this Actor; they do not replace it.
- Only check domains you own or manage, or have another legitimate interest and right to check. You are responsible for making sure your use of the Actor and its output complies with applicable laws, the RDAP registries' terms of service and the target websites' terms.
- Do not use the Actor to probe internal networks, to load-test servers or registries, or to get around access controls or rate limits. Abusive use may be blocked.
- Sanctions and restricted countries. You may not use this Actor if you are located in, ordinarily resident in, or acting on behalf of a person or organisation in a restricted country or region. Currently these are: Afghanistan, Belarus, Central African Republic, Cuba, Democratic Republic of the Congo, Haiti, Iran, Iraq, Lebanon, Libya, Mali, Myanmar, Nicaragua, North Korea, Russia, Somalia, South Sudan, Sudan, Syria, Venezuela, Yemen, Zimbabwe, Antarctica, and the Crimea, Sevastopol, Donetsk, Luhansk, Kherson and Zaporizhzhia regions of Ukraine. You also may not use it if you are on, or owned or controlled by someone on, any applicable sanctions list (including those of the United Nations, the United States (OFAC SDN), the European Union, the United Kingdom or Israel). We may block such use, and we may update this list when the law or our policy changes.
- Output is an automated, best-effort technical snapshot and is provided "as is". DNS, registry and certificate data change over time and can look different from other networks or locations. Registry RDAP data is not available for every TLD. Check results before relying on them for important decisions, such as letting a domain lapse.
- Informational only; no guarantee of outcomes. Output is not legal, regulatory, compliance, security, SEO or other professional advice, and using the Actor does not create an advisory relationship. Tesselyn does not promise any outcome, including email delivery, deliverability, security or domain renewal. You are responsible for checking results and for the changes and decisions you make based on them.
- No warranty; limitation of liability. To the maximum extent permitted by applicable law, the Actor and its output are provided "as is" and "as available", without warranties of any kind, express or implied (including accuracy, completeness, merchantability, fitness for a particular purpose and non-infringement), as set out in section 7 of the Apify Standard Actor Contract. The Actor creator (Tesselyn) is not liable for any indirect, incidental, special, consequential or punitive loss or damage, including lost domains, email delivery, traffic, revenue, profits or data, arising from use of or reliance on the Actor or its output. Any other liability is limited as set out in section 8 of that Contract, and nothing here limits liability that cannot be limited under applicable law. Output is for information only and is not security, legal or other professional advice.
Privacy notice
- What is processed: the domains you submit and public technical data about them: DNS records, registry facts from RDAP, certificate metadata and HTTP response headers.
- What is not collected: the Actor does not use WHOIS. From RDAP it keeps only the registrar's name and IANA ID and the registry dates, status, nameservers and DNSSEC. Registrant, administrative, technical and abuse contacts are never read into the output or stored. DMARC report addresses are reduced to their domain (
aggregateReportDomains), so mailbox names are not stored. Only SPF TXT records are kept: other TXT records, which may contain verification tokens, are discarded. The certificate subject is not stored, and no page content is downloaded. - Where it is stored: only in your own Apify run storage (default dataset,
OUTPUTrecord, run log and input), under your Apify account and Apify's retention settings. Apart from the DNS queries, RDAP lookups and HTTP/TLS requests needed for the checks, the Actor sends nothing to third parties. - Roles: for any personal data in your input or output, you are the controller and the Actor creator acts as processor, as set out in section 5 of the Apify Standard Actor Contract. Run logs contain only counts and error codes.
- Deletion: you can delete the run or dataset in Apify Console at any time. For questions or privacy requests, open an issue on the Actor's Issues tab.
FAQ
Why is there no expiry date for my domain?
Some country-code TLDs don't run an RDAP service, or don't publish expiry dates in it. You'll then see RDAP_UNAVAILABLE (informational), and the other checks still run. We deliberately don't fall back to WHOIS, to avoid processing registrant personal data.
My mail works. Why does it say DKIM wasn't found?
Your provider probably uses a selector outside our common list. That's why the issue is informational only and doesn't lower the score.
Does it check subdomains?
Yes. Enter mail.example.com and the DNS, SPF, TLS and HTTP checks run on that name. RDAP and the DMARC fallback use the registered domain.
Is a domain that doesn't exist charged?
No. NXDOMAIN, DNS failures and timeouts are free.
Related Actors on the Apify Store
- AI Crawler & llms.txt Checker: see which AI crawlers a site's robots.txt allows, check llms.txt and get a 0–100 GEO readiness score.
- Broken Link & Redirect Checker: crawl a site for broken links, redirect chains and missing #anchors.
- Bulk PageSpeed & Core Web Vitals Checker: Lighthouse scores, LCP, CLS, INP and TBT for many URLs on mobile and desktop, no API key needed.
- Sitemap Extractor: list every URL in a domain's sitemaps and check their status codes.
- Website Screenshot Generator: capture the home page of each domain, for example on the same schedule as this check.
- Google Search Results Scraper: see how a domain shows up in Google search results.
- See all Tesselyn Actors on the Apify Store.
Support
Built and maintained by Tesselyn (a brand of HevraBest Group Ltd). Found a bug or a wrong result, or need a feature? Open an issue on the Actor's Issues tab. That is our support channel and the route Apify uses for credit compensation.
Failed runs and unexpected charges. Rows that the "How much does it cost?" section lists as free are not charged. Apify's small per-run "Actor start" charge, when it is listed on the Pricing tab, still applies. If you think a run charged you for work it didn't deliver, open an issue with the run link. If we confirm the problem, we ask Apify to compensate you. Apify gives compensation as platform credits, not money. Apify's General Terms (section 7.9) require charge disputes to be sent to Apify in writing within 15 days of the charge or invoice date, so please report problems promptly.