Email MX Verifier

📧 Email MX verifier for clean email lists

Email MX Verifier checks email addresses before you upload them to a CRM, outreach tool, signup gate, or data pipeline. Paste a list of emails and get one row per checked address with syntax status, MX records, disposable-domain detection, role-address flags, free-provider detection, typo suggestions, confidence scores, and a clear send/review/suppress recommendation.

Use it as a bulk email verifier or email list cleaner when you already have the email addresses and need to know which ones are safe enough to keep. The Actor does not need user credentials, cookies, or third-party API keys. Standard mode uses public DNS checks and list-cleaning rules. Deep SMTP mode can optionally probe the target MX server without sending an email and reports ambiguous mailbox checks as unknown instead of failing the run.

For a small first run, keep the prefilled examples. They include a normal mailbox, a public developer contact, a disposable domain, a role address, a common typo, and an invalid string so you can see the full output shape quickly.

✅ What this bulk email verifier checks

• Email syntax and common formatting problems.
• Domain MX records and sorted MX host evidence.
• Known disposable or temporary email domains.
• Role-based addresses such as admin@, support@, sales@, and noreply@.
• Free email providers such as Gmail, Yahoo, Outlook, Proton Mail, Zoho, and Fastmail.
• Common domain typos such as gmai.com to gmail.com.
• Mail provider hints from MX hosts where they are recognizable.
• Optional SPF, DMARC, and common DKIM selector checks for domain health.
• Optional SMTP and catch-all probes in Deep SMTP mode.

The output is designed for filtering and exports. You can sort by status, riskLevel, confidenceScore, or recommendedDisposition, then send the dataset to CSV, Excel, Google Sheets, the Apify API, webhooks, schedules, or your own workflow.

📊 What data you get

Each dataset row represents one submitted email address after normalization and deduplication. Rows can include:

Field	Description
inputEmail	Original email string you entered.
normalizedEmail	Lowercased email when syntax is valid.
inputIndex	Position of the email in your submitted list.
status	valid, risky, invalid, or unknown.
isValid	true when the standard checks consider the address usable.
syntaxValid, syntaxErrors	Syntax verdict and specific format issues.
domain, hasMxRecords, mxRecords, mxProvider	MX record check and source evidence.
isDisposable, isRoleBased, roleType, isFreeProvider	List-cleaning signals for filtering and segmentation.
riskLevel, confidenceScore, recommendedDisposition	Practical decision fields for send, review, retry, or suppress workflows.
suggestedEmail	Suggested correction for supported typo domains.
domainHealth	SPF, DMARC, and common DKIM selector checks when enabled.
smtp, catchAll	Deep SMTP evidence when selected.
degradedReason, error, retryRecommended, checkedAt	Audit and follow-up context.

🚀 How to run it

1. Open the Actor input.
2. Add email addresses in Email addresses.
3. Keep Verification depth on Standard for a fast email MX check.
4. Use Deep SMTP only when mailbox-level evidence matters more than speed.
5. Start the Actor and open the dataset when the run finishes.

Standard mode is the best default for most list-cleaning work. Deep SMTP can be slower and some mail servers block or hide mailbox checks, especially large providers. When that happens, the row keeps the DNS evidence and marks the SMTP result as unknown with retryRecommended.

🧾 Input example

{
	"emails": [
		"user@gmail.com",
		"contact@github.com",
		"test@mailinator.com",
		"admin@microsoft.com",
		"user@gmai.com",
		"invalid-email"
	],
	"verificationDepth": "standard",
	"checkDomainHealth": true,
	"suggestTypos": true,
	"includeMxRecords": true
}

📤 Output example

{
	"inputEmail": "user@gmail.com",
	"normalizedEmail": "user@gmail.com",
	"inputIndex": 1,
	"status": "risky",
	"isValid": false,
	"syntaxValid": true,
	"syntaxErrors": [],
	"domain": "gmail.com",
	"hasMxRecords": true,
	"isDisposable": false,
	"isRoleBased": false,
	"roleType": null,
	"isFreeProvider": true,
	"mxProvider": "Google Workspace",
	"riskLevel": "medium",
	"confidenceScore": 64,
	"recommendedDisposition": "send_with_caution",
	"suggestedEmail": null,
	"retryRecommended": false,
	"checkedAt": "2026-06-01T22:35:38.822Z"
}

💰 Pricing

This Actor uses pay-per-event pricing. You are charged once per email address checked and there is no Actor-start fee in the local pricing artifact.

Current planned prices:

Apify plan	Price per 1,000 checked emails
Free	$0.80
Bronze	$0.70
Silver	$0.55
Gold	$0.40
Platinum	$0.25
Diamond	$0.20

The default prefilled run is small enough for a quick output check before you scale up to a larger list.

⚠️ Limits and caveats

• The Actor verifies emails you provide. It does not find new email addresses from names, domains, websites, or social profiles.
• MX records prove that a domain accepts email, not that a specific mailbox definitely exists.
• Deep SMTP never sends an email, but some mail servers time out, greylist, or hide mailbox existence. Those cases are marked as inconclusive.
• Disposable-domain and typo checks are rule-based and improve list hygiene, but they are not a legal or compliance decision by themselves.
• Invalid email strings are saved as useful list-cleaning rows so you can fix or suppress them downstream.

❓ FAQ

✉️ Does this Actor send emails?

No. Standard mode only checks syntax, DNS, and list-cleaning signals. Deep SMTP can connect to a mail server and issue probe commands, but it does not deliver a message body.

🔐 Do I need an API key or login?

No. Email MX Verifier does not need user credentials, cookies, or a paid external email-verification API.

🧪 Should I use Standard or Deep SMTP?

Use Standard for most bulk list cleaning. Use Deep SMTP when mailbox-level evidence is important and you accept that some mail servers will return unknown or time out.

📁 Can it upload a CSV directly?

Use the Apify Console list editor, API, integrations, or dataset tools to pass email arrays into the Actor. The public input contract is the emails list.

🔎 Is this an email finder?

No. It checks email addresses you already have. It does not guess patterns, enrich contacts, scrape websites, or find professional emails.

📝 Changelog

• 0.1: Initial release.

🆘 Support

For issues, questions, or feature requests, file a ticket and I'll fix or implement it in less than 24h 🫡

🔗 Other actors

• Website Emails Scraper ↗ - Find public contact emails on websites before verifying them.
• Gmail Username Checker ↗ - Check Gmail username availability for new address ideas.
• Business Address Scraper ↗ - Extract business addresses from company websites for lead data cleanup.
• Website URL Crawler ↗ - Build website link maps before contact or data extraction.
• Font Detector ↗ - Audit website fonts, font sources, and typography evidence.

Made with ❤️ by Maxime Dupré