Pricing
$1.50 / 1,000 results
Email Domain Intelligence
DeprecatedGather email infrastructure intelligence for domains. Extract MX records, SPF, DMARC policies, and SSL certificate info. Perfect for sales lead qualification, security research, and compliance teams. Zero dedicated actors on Apify.
Pricing
$1.50 / 1,000 results
Rating
0.0
(0)
Developer
Actor stats
0
Bookmarked
1
Total users
0
Monthly active users
2 months ago
Last modified
Categories
Share
Look up email infrastructure data for any domain. Checks DNS records for MX, SPF, and DMARC configuration, plus SSL certificate details. No API keys or authentication required.
Features
- Extract MX records with priority levels and provider detection
- Parse SPF records into individual includes
- Retrieve DMARC policy (none, quarantine, reject)
- Check SSL certificate presence and issuer
- Detect mail providers: Google Workspace, Microsoft 365, Zoho, ProtonMail, custom
- Batch process hundreds of domains in one run
- Pure DNS-over-HTTPS via Cloudflare — no external dependencies
Use Cases
- Lead qualification: confirm a prospect domain has real email infrastructure before outreach
- Email deliverability checks: verify SPF and DMARC are configured before sending campaigns
- Domain security audits: find domains missing DMARC enforcement or with weak SPF
- Compliance verification: ensure partner domains meet your email authentication standards
- M&A due diligence: scan target company domains for email setup and SSL status
Input
| Field | Type | Required | Description | Default |
|---|---|---|---|---|
| domains | array of strings | Yes | Domain names to analyze | — |
| includeWhois | boolean | No | Include WHOIS registration data | true |
Example input:
{ "domains": ["acme.com", "example.org"], "includeWhois": true }
Output
One result per domain:
{ "domain": "acme.com", "mx_records": [ {"priority": 1, "host": "aspmx.l.google.com", "provider": "Google Workspace"}, {"priority": 5, "host": "alt1.aspmx.l.google.com", "provider": "Google Workspace"} ], "spf_record": "v=spf1 include:_spf.google.com ~all", "spf_includes": ["_spf.google.com"], "dmarc_record": "v=DMARC1; p=quarantine; rua=mailto:dmarc@acme.com", "dmarc_policy": "quarantine", "has_ssl": true, "ssl_issuer": "Let's Encrypt" }
| Field | Type | Description |
|---|---|---|
| domain | string | The domain that was analyzed |
| mx_records | array | MX entries with priority (int), host (string), provider (string) |
| spf_record | string | Raw SPF TXT record value |
| spf_includes | array | Domains included via SPF mechanisms |
| dmarc_record | string | Raw DMARC TXT record value |
| dmarc_policy | string | DMARC policy: none, quarantine, or reject |
| has_ssl | boolean | Whether a valid SSL certificate was found |
| ssl_issuer | string | Certificate authority name |
Pricing
$1.50 per 1,000 domain lookups ($0.0015 per result).
How It Works
Sends DNS-over-HTTPS queries to Cloudflare's resolver for MX, SPF, and DMARC TXT records. Then opens a TLS socket connection to port 443 to check the SSL certificate chain. No browsers, no headless Chrome, no external packages — pure Python stdlib.
FAQ
What mail providers are detected? Google Workspace, Microsoft 365, Zoho, ProtonMail, and custom/self-hosted setups. The actor matches MX hostnames against known provider patterns.
How fast is it? Around 1 second per domain. DNS resolution is fast; SSL checks add a small overhead.
Do I need an API key? No. DNS-over-HTTPS is free and unauthenticated. Same for SSL socket checks.
Does it work with subdomains? Yes. Pass any hostname — the actor resolves MX, SPF, and DMARC for whatever you give it.
Limits
- Timeout: 10 seconds per domain (covers slow DNS responses)
- Batch size: up to 500 domains per run
- DNS-over-HTTPS rate: Cloudflare's public resolver has soft limits (~1,000 queries/min)
- WHOIS lookups may fail for privacy-protected domains
