Bulk DNS Lookup, Tech Stack & Email Provider Checker avatar

Bulk DNS Lookup, Tech Stack & Email Provider Checker

Pricing

from $1.00 / 1,000 domain looked ups

Go to Apify Store
Bulk DNS Lookup, Tech Stack & Email Provider Checker

Bulk DNS Lookup, Tech Stack & Email Provider Checker

Check domains in bulk for availability and DNS records, plus each domain's email provider, email sending services, verified business tools and SPF/DMARC security. Built for lead enrichment and domain research.

Pricing

from $1.00 / 1,000 domain looked ups

Rating

0.0

(0)

Developer

Stego

Stego

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

19 days ago

Last modified

Features

Limited permissions

Share

Bulk DNS Lookup & Domain Availability Checker

Bulk DNS lookup and domain availability checker for any TLD, including .com, .net and .org. Paste one domain or up to 10,000 (plain domains, URLs or email addresses) and get one clean JSON row per domain with:

  • live DNS records: A, AAAA, MX, TXT (SPF, verification records) and NS
  • a tech stack summary from DNS (on by default): email provider (Google Workspace, Microsoft 365, Zoho, Proton…), email sending services from SPF (SendGrid, Mailchimp, Amazon SES, HubSpot, Salesforce, Zendesk…), services the domain has verified with TXT tokens (Google, Microsoft, Atlassian, Stripe, Facebook, DocuSign, Adobe, Apple…) and SPF / DMARC policy
  • a registered / likely-available hint (switch on Add availability hint)
  • clear statuses and a billable flag that scripts, spreadsheets and AI agents can rely on

What it is not: this is not a WHOIS scraper. Expect most rows to be DNS-only. Registrar, created/expiry dates, EPP status and DNSSEC come from the registry's official RDAP service and are returned only for 8 small TLDs whose registry terms we read and found no written ban on this use: .fi, .ec, .ht, .cv, .fj, .pg, .ss and .vi (details below). Almost every other registry, including Verisign (.com/.net), PIR (.org), Identity Digital, GoDaddy Registry, CentralNic, Nominet and Google Registry, bans automated or commercial use in writing, so it is never queried. Those domains (in practice, the large majority of what you will look up) get DNS data and the DNS-based availability hint only, with registry fields set to null.

No WHOIS scraping, no website scraping, no API key.

What can you use this DNS lookup tool for?

  • Check MX, TXT and NS records in bulk: see which domains in a list accept email (MX), which publish SPF or verification TXT records, and where their DNS is hosted (NS).
  • Tech stack / email provider lookup for lead lists: see which companies use Google Workspace or Microsoft 365, which send email through HubSpot, Salesforce or SendGrid, and which have SPF and DMARC set up, without ever loading their website.
  • Clean up a lead or customer list: paste website URLs or email addresses; each one is reduced to its domain, duplicates are merged, and domains that don't resolve stand out (dnsStatus: NXDOMAIN).
  • Brainstorm domain names: run a list of name ideas with the availability hint on to see at a glance which are clearly taken. Always confirm a "likely available" name with a registrar before buying.
  • Feed scripts and AI agents: one call, flat JSON, one date format, every input accounted for.

How to use it

  1. Open the Actor, paste domains, URLs or emails into Domains (the form is prefilled with a working example).
  2. Optionally turn on Add availability hint and pick which DNS record types you want.
  3. Click Start. Download results as JSON, CSV or Excel, or read them through the Apify API.

What it does

  • DNS records (on by default). A, AAAA, MX (priority and exchange), TXT (chunks joined) and NS, using standard DNS queries through the platform's resolver. Each row also gets a dnsStatus: NOERROR, NXDOMAIN, SERVFAIL or TIMEOUT.

  • Tech stack from DNS (detectTechStack, on by default, needs DNS on). Adds a techStack object built only from the domain's MX, TXT/SPF and _dmarc TXT records: emailProvider, emailProviders, emailSendingServices, verifiedServices (plus emailSendingServicesText and verifiedServicesText, the same lists as comma-separated strings) and emailSecurity (spfPresent, spfAllPolicy, dmarcPresent, dmarcPolicy). Security gateways (Proofpoint, Mimecast…) are listed in emailProviders but skipped for emailProvider when a mailbox provider is also visible. Only top-level SPF includes are read. A field is null when its DNS query failed. Limits: only services that leave a DNS trace are found; a verification token shows the domain was verified with a service at some point, not that it is still a customer; unknown MX hosts show as Other / self-hosted. No website is loaded and there is no extra charge.

  • Availability hint (switch on checkAvailability). Adds likelyAvailable, availabilityBasis (dns, rdap or rdap+dns) and a plain-English availabilityNote.

  • Registry RDAP data, supported TLDs only. Adds registrar, createdAt, updatedAt, expiresAt, daysUntilExpiry, statusCodes, nameservers and dnssec. The registry RDAP server is found through the official IANA RDAP bootstrap. Unsupported TLDs instead report rdapServer, registryOperator and registryTermsUrl, so you can see why.

  • Normalises messy input. Accepts:

    • plain domains, URLs (https://www.example.com/page) and emails (name@example.com)
    • IDNs (bücher.de) and punycode
    • subdomains, which are reduced to the registered domain with the Public Suffix List (shop.example.co.uk → example.co.uk)

    Duplicates are merged and charged once.

  • Never fails silently. Every input entry gets a row with a status, plus a readable error when relevant.

  • Crash-safe. Progress is saved after every batch of 25 results. If a run restarts, it never returns or charges a domain twice.

Polite to registries

  • One request at a time per registry server, at most 1 request per second by default (the maximum allowed is 2).
  • Retry-After is honoured on HTTP 429/503:
    • short waits: the Actor waits, retries and slows down
    • long waits: that server's remaining domains are returned as rate-limited and are not charged
  • A server that keeps failing is paused for the rest of the run.
  • Caching. Registry answers are reused, so a registry is not asked the same question twice:
    • within a run, each RDAP URL is requested at most once
    • across runs, answers are kept for cacheHours (default 24 h) in a key-value store named rdap-domain-lookup-cache on your Apify account
    • only non-contact fields are stored (registrar name, IANA ID and URL, dates, status codes, nameservers, DNSSEC). No contact data is stored at all, not even the registrar's abuse email or phone. A row served from the cache therefore has registrarAbuseEmail and registrarAbusePhone set to null; set cacheHours to 0 if you need them on every row.
    • "not found" answers are reused for at most 1 hour
    • rows served from the cache have rdapFromCache: true and rdapCachedAt
    • DNS is always live
  • Redirects are followed manually: HTTPS only, at most 3 hops, and every hop must also be a supported registry server. A refused redirect is never requested, and the row is returned as error and not charged.

Statuses

statusMeaningCharged?
registered / not-foundSupported TLD: the registry RDAP answered (record / HTTP 404)yes
excluded-by-registry-termsRegistry not queried: its RDAP terms restrict this use, or could not be confirmed. DNS fields are filled.yes, if DNS gave a clean answer
no-rdap-serverThe TLD has no RDAP service in the IANA bootstrap (e.g. .de, .io, .co). DNS fields are filled.yes, if DNS gave a clean answer
terms-not-reviewedA registry server added to IANA after our review; not queried. DNS fields are filled.yes, if DNS gave a clean answer
rate-limited / errorLookup failed (see error and retryAfterSeconds), including a registry redirect that was refused (non-HTTPS, too many hops, or pointing to a server that is not supported)no, never, even if DNS data is present
invalid-inputNot a usable domain (see error)no
not-processedThe run's max total charge was reached firstno

Each row has billable: true|false, so you can see exactly which rows were charged. A clean DNS answer means either every requested record type resolved (NOERROR) or the name does not exist (NXDOMAIN).

Availability caveat

  • DNS only (.com, .net, .org and most TLDs):
    • NOERROR: the name exists, so it is registered.
    • NXDOMAIN: a weak hint. Registered names with no nameservers, names on hold, and reserved or premium names also return NXDOMAIN.
  • With registry RDAP (supported TLDs): an HTTP 404 means the registry has no record, so the name is likely available. If DNS still shows the name, it is reported as probably registered (rdap+dns).
  • Neither is a guarantee. Always confirm with a registrar before buying.

Supported TLDs for registry data (review of 21 Oct 2026)

.cv, .ec, .fi, .fj, .ht, .pg, .ss and .vi. Second-level names under them, like .com.ec and .com.fj, are covered too. The .ss registry limits lookups to 15 per minute "to prevent 'data mining'", so .ss names are always paced at one request every 4 seconds.

Not supported (registry never queried; DNS data only), with the reason and quotes in TOS-NOTES.md:

  • .com, .net, .org, .info, .biz, .uk, .ca, .nl, .au, .br, .in, .pl, .ng and almost all new gTLDs: the registry bans the use in writing (on any channel: RDAP notice, WHOIS terms or website terms).
  • .ly, .zm, .ml, .lb, .gs, .nf, .cx, .gy, .rw, .uz, .hn, .as and .ke: also written bans, found in the October 2026 re-review.
  • .fr, .tz and .рус: the registry's terms could not be read or verified (site offline / terms document missing / claimed ban not locatable), so they are treated as not supported until confirmed.
  • .de, .io, .co: these TLDs have no RDAP service.

Input

FieldDefaultDescription
domainsrequiredDomains, URLs or emails; up to 10,000 per run
reduceToRegisteredDomaintrueSubdomain → registered domain. When off, subdomains are invalid-input.
includeDnstrueResolve DNS records
dnsRecordTypesall fiveAny of A, AAAA, MX, NS, TXT
detectTechStacktrueAdds the techStack object (needs includeDns)
checkAvailabilityfalseAdds the availability hint (see the caveat above)
requestsPerSecondPerServer1Pacing per supported registry server (0.1–2)
maxRetryWaitSecs30Longest Retry-After to wait for. Longer waits mark that server's domains as rate-limited.
requestTimeoutSecs20Per-request timeout for RDAP and DNS
maxConcurrency10Domains processed in parallel (per-server limits still apply)
cacheHours24How long registry answers are reused across runs (0 turns the cross-run cache off)

Example inputs:

{ "domains": ["apify.com", "https://www.bbc.co.uk/news", "support@traficom.fi"] }
{ "domains": ["my-startup-name.com", "my-startup-name.fi"], "checkAvailability": true }

Output (one item per unique domain)

See samples/output-sample.json for real output. Summary of the main fields:

  • DNS: aRecords, aaaaRecords, mxRecords, txtRecords, dnsNameservers, dnsStatus, dnsError
  • Tech stack: techStack.emailProvider, techStack.emailProviders, techStack.emailSendingServices, techStack.verifiedServices, techStack.emailSendingServicesText, techStack.verifiedServicesText, techStack.emailSecurity
  • Availability: likelyAvailable, availabilityBasis, availabilityNote
  • Registry (supported TLDs; null otherwise): registrar, registrarIanaId, registrarUrl, registrarAbuseEmail, registrarAbusePhone (live answers only, never cached), createdAt, updatedAt, expiresAt, daysUntilExpiry, statusCodes, eppStatusCodes, nameservers, dnssec, rdapUrl, rdapFromCache, rdapCachedAt
  • Why not: rdapServer, registryOperator, registryTermsUrl, error

Dates are always YYYY-MM-DDTHH:MM:SSZ (UTC). Fields you switch off (DNS, availability) are left out instead of being set to null.

A run summary is saved under the OUTPUT key. It includes byStatus, chargedLookups, rdapRequestsSent, rdapServersQueried, rdapCacheHits and bootstrapPublished.

Personal data

None. Registrant, admin and tech contacts are never returned or cached. The only contact data returned is the registrar's role-based abuse email and phone, when the registry publishes them, and only on live registry answers: they are never written to the cache.

Pricing

Pay per event, no subscription. The start fee is only $0.00005 per run ($0.05 per 1,000 runs):

EventPrice
Actor start$0.00005 per run
Domain looked up (billable rows only)$0.001 per domain ($1 per 1,000)
  • The per-domain fee is the same whether or not registry data is returned. For most domains (all .com, .net, .org and most other TLDs) a billable row contains DNS records and the DNS availability hint only. Registry data is a bonus for the 8 supported TLDs above.
  • A DNS-only row is charged only if DNS gave a clean answer (every record type NOERROR, or NXDOMAIN).
  • Free: error and rate-limited rows (including refused redirects), even when DNS data is present; invalid, duplicate and not-processed rows; DNS-only rows with a DNS failure. The run respects your "Max total charge" setting; domains beyond it are returned as not-processed.

Data sources and terms

  • IANA RDAP bootstrap registry: https://data.iana.org/rdap/dns.json (RFC 9224).
  • DNS: the public Domain Name System, using standard resolver queries.
  • Registry RDAP servers: only those whose terms or help text we read and found no written ban. Per-server reasoning and quotes are in TOS-NOTES.md and src/registry_terms.json.

Use it from code, Zapier, Make, n8n or an AI agent

  • API: start runs and read results through the Apify API or the Python and JavaScript API clients. The API tab on this page has ready-made code.
  • No-code integrations: connect the results to Zapier, Make, n8n, Google Sheets, Slack, email or a webhook with Apify's integrations.
  • AI agents (MCP): add this Actor as a tool through the Apify MCP server, e.g. https://mcp.apify.com?tools=stego-bot/rdap-domain-lookup. Input fields and output fields are fully described, so an agent can fill the input and read the results without guessing.
  • Schedules: add an Apify schedule (e.g. daily) to turn a saved input into a recurring job or alert.

FAQ

Can it tell me for sure whether a .com domain is available? No. For .com and most TLDs the hint is based on DNS only, and NXDOMAIN is a weak signal. Confirm with a registrar before buying.

Does it return WHOIS contact details? No. Registrant, admin and tech contacts are never returned or stored.

Do I need an API key? No.

More Actors from stego-bot