Domain Enrichment — Email, DNS & Website Tech

Turn company domains into structured public DNS observations and optional homepage technology hints. Use the results to segment accounts by observed mail-provider signals, inspect published email-authentication records or add website context to a research table.

Get your first domain record

{
  "domains": ["apify.com"],
  "includeHttp": true
}

Open the dataset and inspect the raw mx, spf, dmarc and ns fields alongside the derived labels. The example is a valid input shape, not a statement about this domain's current configuration. Export JSON, CSV or Excel for downstream analysis.

Use includeHttp:false when you need DNS observations only. The homepage request is optional and adds time. Full URLs or email-style inputs are normalized to domains, and duplicate normalized domains are checked once.

What you receive

Field	Meaning
domain	Normalized input domain
mx, emailProvider	Mail-exchanger hosts and a provider label inferred from them
spf	Published SPF text when returned
dmarc, dmarcPolicy	DMARC text and parsed policy when returned
ns, dnsProvider	Nameservers and an inferred DNS provider
ipv4	Returned A-record addresses
httpStatus, finalUrl, title	Homepage response information when HTTP inspection is enabled
server, poweredBy, generator, tech	Available headers, generator tag and technology hints

Technology detection uses a limited set of patterns in headers and HTML. It can miss or mislabel technologies. A nameserver provider is not necessarily the website's hosting provider, and an MX provider can be an email gateway rather than the final mailbox service.

Pricing

This Actor uses an Actor-start event, charged per GB of allocated memory with a minimum of one event. It currently has no separate per-output-record event. The start fee can apply even if the run returns no usable records.

Open the Pricing tab for the active rate and any subscription-tier discounts, then check allocated memory in the run settings. Output limits cap collection; they do not guarantee results.

Interpreting missing data

The current implementation does not distinguish every DNS lookup failure from an absent record. Values such as none, missing, empty arrays or null must be treated as unavailable observations and checked before concluding that a domain lacks email authentication.

This Actor does not verify individual mailboxes, test inbox placement, check DKIM selectors, measure sender reputation or certify security/compliance. Inspecting a prospect's DNS does not establish that your messages will be delivered. No domain-registration or WHOIS record is collected.

Repeated research

Save the input as an Apify task and schedule it when you need fresh observations. Each run returns a snapshot; persistent change detection is not implemented. Homepage access may be blocked or unavailable. For a reproducible issue, share the run ID and public domain without credentials.