🔎 DNS Records Checker - Domain DNS Lookup Data

Look up public DNS records for domains and export A, AAAA, CNAME, MX, NS, TXT, SOA and CAA records as structured data. Export to JSON/CSV/Excel, run on a schedule, call via API, or connect to Make, Zapier or n8n.

What is the DNS Records Checker?

The DNS Records Checker turns public technical signals from domains and URLs into structured data. These checks are common in SEO audits, lead enrichment, deliverability reviews, site migrations, security reviews, and technical due diligence, but they are slow to repeat manually across large lists. This actor lets you paste domains or URLs and receive normalized rows that are ready for spreadsheets, CRM enrichment, dashboards, alerts, and API workflows.

The actor is designed for reliability first. It uses direct network requests, avoids browsers, keeps defaults small for Apify health checks, and returns one or more clear rows per target. That makes it useful both as a standalone audit tool and as a building block in larger automation stacks.

What data does it extract?

• Input domain or URL
• Final source URL where applicable
• HTTP status or DNS record type
• Parsed technical fields for this actor's check
• Raw values where useful for auditability
• Stable fields suitable for exports and joins
• A source marker for downstream pipelines

Input

Field	Type	Description
targets	array	Domains or URLs to check, depending on the actor.
maxResults	integer	Maximum rows to return per target.

Example input

{
  "targets": [
    "apify.com"
  ],
  "maxResults": 25
}

Output

{"domain": "apify.com", "record_type": "A", "value": "104.18.12.123", "source": "dns"}

Use cases

• SEO audits: check redirects, metadata, DNS and domain configuration at scale.
• Lead enrichment: add technical signals to company domains before outreach.
• Email deliverability: verify MX, SPF and DMARC setup for prospect or client domains.
• Site migration QA: confirm redirect paths, final URLs and public metadata.
• Technical due diligence: collect infrastructure details during website or business research.
• Monitoring: schedule recurring checks and alert when important values change.

Practical workflow

Start with a clean list of domains or URLs. For enrichment workflows, include one domain per target and keep maxResults small. For audit workflows, increase maxResults so all relevant records or redirect hops are captured. Export the dataset to CSV or Excel for manual review, or connect it to Make, Zapier, n8n, Airtable, Google Sheets, BigQuery, or a webhook.

For recurring monitoring, keep the same target list and run the actor on a schedule. Compare the latest dataset with the previous run using stable fields such as domain, URL, record type, hop index, or metadata key. This makes it easy to detect broken redirects, missing mail records, changed Open Graph previews, or DNS changes that could affect SEO, deliverability, analytics, or sales workflows.

Data quality notes

Technical website data is not always tidy. DNS providers return values in different forms, websites may redirect across hostnames, and pages can include incomplete social metadata. The actor keeps normalized fields where possible while preserving raw values that matter for audits. This is intentional: clean columns help automation, and raw values help humans verify edge cases without re-running the check.

The default target is chosen to return real data in a small Apify test run. In production, use your own domains or URLs. If a target fails, the actor logs the failure and continues with the rest of the list so one bad domain does not ruin the whole run.

For agency and sales workflows, use the output as a first-pass signal rather than a final verdict. A missing record can indicate a genuine configuration issue, but it can also mean the domain is parked, redirected, protected by a provider, or intentionally configured differently. The dataset gives you enough structured evidence to sort the list, identify likely problems, and decide which targets deserve a deeper manual review.

For technical teams, the same output works well as a regression snapshot. Store each scheduled run, compare the latest rows with the previous dataset, and flag records that changed. This is useful before and after migrations, DNS provider changes, domain launches, marketing campaign launches, email-platform changes, and website redesigns.

Reliability and performance

This actor does not use a browser, residential proxy, or paid unblocker. It performs public DNS lookups or HTTP requests that are expected to work from Apify's cloud environment. That keeps costs low and makes the actor suitable for daily auto-tests, scheduled audits, and larger domain lists.

FAQ

Does it require an account or API key? No. It uses public DNS or public webpage data.

Can I check multiple targets at once? Yes. Add multiple domains or URLs to the input list.

Can I schedule it? Yes. Use Apify schedules to run recurring checks.

Can I export to Excel? Yes. Apify datasets export to JSON, CSV, Excel, XML, and RSS.

Can I connect it to automations? Yes. Use Apify API, webhooks, Make, Zapier, n8n, or dataset integrations.

What happens when a target fails? The actor logs the failure and continues with the remaining targets.

Is it legal? The actor checks public technical data. You are responsible for respecting website terms, rate limits, privacy rules, and applicable laws.

How is billing calculated? Pay-per-event billing charges per result pushed to the dataset.

Why include raw values? Raw values make audits verifiable and preserve details that can matter in edge cases.

You might also like

• Website Status Checker
• HTTP Headers Checker
• SSL Certificate Checker
• Meta Tags Extractor
• Website Contact Extractor

Keywords: DNS records checker, DNS lookup scraper, domain DNS audit, MX lookup, TXT records, domain intelligence, website audit, technical SEO tool, domain intelligence, lead enrichment, Apify scraper, automation, monitoring, business data