Email Deliverability Checker
Pricing
Pay per event
Email Deliverability Checker
This actor checks the email authentication configuration of any domain by querying DNS records. It validates MX records (mail server), SPF (sender authorization), DKIM (message signing), and DMARC (spoofing protection). Use it for email marketing audits, lead qualification, or monitoring...
Pricing
Pay per event
Rating
0.0
(0)
Developer

Stas Persiianenko
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Check email deliverability for any domain. Validates MX records, SPF, DKIM, and DMARC configuration. Returns a deliverability grade (A+ to F) with actionable findings.
What does Email Deliverability Checker do?
This actor checks the email authentication configuration of any domain by querying DNS records. It validates MX records (mail server), SPF (sender authorization), DKIM (message signing), and DMARC (spoofing protection). Each domain receives a deliverability grade from A+ to F based on its configuration. Use it for email marketing audits, lead qualification, or monitoring your own domain's email health.
Use cases
- Email marketers -- verify domain authentication before sending campaigns to maximize inbox placement and avoid spam folders
- Sales teams -- qualify leads by checking if prospect domains have valid email infrastructure that can actually receive your messages
- Security auditors -- identify domains vulnerable to email spoofing due to missing DMARC or SPF records
- Compliance officers -- verify DMARC enforcement for organizational domains to meet security policy requirements
- Domain administrators -- monitor your own domains to ensure email authentication stays properly configured over time
Why use Email Deliverability Checker?
- Comprehensive analysis -- checks all four pillars of email authentication: MX, SPF, DKIM, and DMARC in a single run
- Actionable grading -- each domain receives a letter grade (A+ to F) so you can quickly prioritize which domains need attention
- Provider detection -- identifies the email provider (Google Workspace, Microsoft 365, ProtonMail, etc.) from MX records
- DKIM multi-selector -- checks 11 common DKIM selectors (default, google, selector1, etc.) to find signing configurations
- Batch processing -- check hundreds of domains in one run with detailed results for each
- Pay-per-event pricing -- only $0.002 per domain, making it affordable for large-scale audits
What is checked
| Check | Weight | What it validates |
|---|---|---|
| MX Records | 25% | Domain can receive email, detects email provider |
| SPF | 25% | Authorized senders, policy enforcement |
| DKIM | 25% | Email signing (checks 11 common selectors) |
| DMARC | 25% | Spoofing protection policy and reporting |
Input parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
domains | array of strings | Yes | -- | List of domains to check email deliverability for. URLs are automatically cleaned to domain names. |
{"domains": ["google.com", "apify.com", "github.com"]}
Output example
{"domain": "google.com","grade": "A+","score": 100,"mx": {"exists": true,"records": [{ "priority": 10, "exchange": "smtp.google.com" }],"provider": "Google Workspace"},"spf": {"exists": true,"record": "v=spf1 include:_spf.google.com ~all","isValid": true,"mechanisms": [],"includes": ["_spf.google.com"],"policy": "~all","issues": []},"dmarc": {"exists": true,"record": "v=DMARC1; p=reject; rua=mailto:...","policy": "reject","subdomainPolicy": null,"percentage": null,"reportingEmail": "mailto:...","issues": []},"dkim": {"selectorsChecked": ["default", "google", "selector1", "..."],"found": [{ "selector": "google", "record": "v=DKIM1; k=rsa; p=..." }],"issues": []},"issues": [],"checkTimeMs": 234,"error": null,"checkedAt": "2026-03-01T12:00:00.000Z"}
Grading scale
| Grade | Score | Description |
|---|---|---|
| A+ | 90-100 | All email authentication properly configured |
| A | 80-89 | Strong configuration with minor gaps |
| B | 70-79 | Good but missing some authentication |
| C | 60-69 | Partial configuration, deliverability at risk |
| D | 40-59 | Significant gaps in email authentication |
| F | 0-39 | Critical email configuration missing |
How much does it cost?
| Event | Price | Description |
|---|---|---|
| Start | $0.035 | One-time per run |
| Domain checked | $0.002 | Per domain analyzed |
Example costs:
- 5 domains: $0.035 + 5 x $0.002 = $0.045
- 100 domains: $0.035 + 100 x $0.002 = $0.235
- 1,000 domains: $0.035 + 1,000 x $0.002 = $2.035
Using the Apify API
You can start Email Deliverability Checker programmatically from your own applications using the Apify API. The following examples show how to run the actor and retrieve results.
Node.js
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: 'YOUR_TOKEN' });const run = await client.actor('automation-lab/email-deliverability-checker').call({domains: ['google.com', 'apify.com'],});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
Python
from apify_client import ApifyClientclient = ApifyClient('YOUR_TOKEN')run = client.actor('automation-lab/email-deliverability-checker').call(run_input={'domains': ['google.com', 'apify.com'],})items = client.dataset(run['defaultDatasetId']).list_items().itemsprint(items)
Integrations
Email Deliverability Checker works with all major integration platforms supported by Apify. Connect it to Make (formerly Integromat), Zapier, n8n, or Slack to build automated email health monitoring workflows. Export results directly to Google Sheets for collaborative analysis or use webhooks to get notified when grades drop below a threshold. You can also chain this actor with the MX Record Checker for additional mail server details.
Tips and best practices
- Check your own domains first -- run this actor on all domains you send email from to ensure your authentication is properly configured before auditing others.
- Focus on grade F domains -- domains with an F grade are missing critical authentication and are highly vulnerable to spoofing. Prioritize fixing these.
- Monitor over time -- schedule regular runs with Apify Schedules to detect when email authentication degrades due to DNS changes or expired DKIM keys.
- Use for lead qualification -- domains with strong email authentication (A/A+) are more likely to be legitimate businesses with active email infrastructure.
- Pass URLs directly -- the actor automatically cleans URLs to domain names, so you can paste full URLs like
https://www.example.com/pageand it will extractexample.com.
FAQ
What do the grades mean for email deliverability? The grade reflects how well a domain's email authentication is configured. An A+ means all four checks (MX, SPF, DKIM, DMARC) pass, which maximizes inbox delivery. Lower grades mean missing authentication, which increases the chance of emails being marked as spam or rejected.
Does this actor send any emails? No. This actor only queries DNS records. It does not send emails, connect to mail servers, or verify individual email addresses. It checks the domain-level configuration that affects deliverability.
Why might a domain have a good grade but still land in spam? Email deliverability depends on more than just DNS authentication. Sender reputation, content quality, sending volume, and recipient engagement also play a role. This actor checks the DNS foundation, which is necessary but not sufficient for good deliverability.