Verify a whole list of email addresses on Apify with the MailTester Ninja Email Verifier Actor: paste the addresses, add your key, click Start. Each address is checked in real time against the recipient's mail server and comes back valid, invalid or risky, in the order of your list, ready to export to CSV, Excel or JSON or to send to your CRM. Nothing is stored on our side.
Official Actor in the Apify Store
Published by MailTester Ninja. It runs on every Apify plan, the free plan included, and adds no charge of its own: you only pay the Apify usage of the run, which stays tiny.
What you need
- An Apify account. The free plan is enough to try it.
- A key: a free API token (50 checks a day, one every 30 seconds), or a paid key for full speed. Without a key, the Actor only checks its three sample addresses, so you can see the output first.
Verify a list in three steps
- Open the Actor and paste your addresses in Email addresses, one per line. Lines such as
Jane Doe <jane@example.com>and comma-separated lists work too; duplicates are checked once. - Paste your key in MailTester Ninja key, without the braces: a free token starts with
mtf_, a paid key withsub_. Apify stores it encrypted. - Click Start, follow the progress in the status line, then export the results or open them through the Apify API.
Read the results
| Result | Meaning | What to do |
|---|---|---|
valid | The mail server accepts the address | Keep the contact. |
invalid | Rejected, no mail server, disposable or full mailbox | Remove it before you send. |
risky | Uncertain, for example a catch-all domain that accepts every address | Decide by risk, or check again later for temporary answers. |
not_checked | No verdict: daily limit of the key reached, or no key | Check it again; never drop an address for this reason. |
Each row also gives the verdict code and label (ok Accepted, ko Rejected, mb Catch-All...), the domain and the mail server used. A summary of the run is saved in the key-value store under OUTPUT.
Speed and limits
A key allows its daily limit divided by 8,640 checks per 10 seconds, for all your tools together. The Actor reads the limit of your key and paces itself: about one check per second with the $6.99 plan, more with higher plans. If the daily limit is reached during a run, the remaining addresses come back as not_checked and the run ends cleanly.
Run it from your code or your automations
Apify runs the Actor from its API, on a schedule, or from Make, Zapier, n8n and other tools, and AI agents can call it through the Apify MCP server. A direct call that returns the results:
curl -X POST "https://api.apify.com/v2/acts/mailtester-ninja~email-verifier/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"emails": ["jane.doe@example.com"], "apiKey": "YOUR_MAILTESTER_KEY"}'
To check addresses one at a time inside your own code, call the MailTester Ninja API directly.
Questions
Why is the key free refused?
The keyless tier is counted per IP address, and Apify shares its IP addresses between users. Use a free API token instead.
Does the Actor send emails?
No. The check stops before any message is sent.
Is anything stored?
We keep no copy of the addresses you verify. The results stay in your own Apify storage, under your control.
Try it now
Get a free API token, or see the plans for up to 200,000 checks a day. Full reference: API documentation and OpenAPI specification. Back to all integrations.
