Guide / Email verification

Verify an email address without sending a single message

You can tell whether an address is worth keeping in one request. You cannot tell whether the mailbox exists. Knowing the difference is most of the work.

Why bad addresses cost money

A bounce is not free. Every hard bounce teaches the receiving provider that your sending domain is noisy, and those signals compound. Cleaning at signup is cheaper than cleaning later, and far cheaper than repairing a sending reputation.

What you can check without SMTP

  • Syntax: RFC length limits, quoted locals, illegal characters.
  • MX records: does the domain accept mail at all, and which provider handles it.
  • A/AAAA fallback: domains without MX sometimes inherit the A record.
  • Disposable domains: blocklists of throwaway providers.
  • Role accounts: support@, admin@, noreply@ never reach a human.
  • Typo distance: gmail.con is not gmail.com.

What you cannot check: whether one specific mailbox exists. That needs an SMTP conversation, and most providers now treat verification probes as hostile. Vendors that promise it are guessing or risking your IP reputation.

One request

Use the marketplace proxy URL with your key. The same call works from a browser, a worker or a script.

curl -s 'https://emailcheck.p.rapidapi.com/v1/verify?email=ayam.khan%40gmail.com' \
  -H 'X-RapidAPI-Key: YOUR_KEY' \
  -H 'X-RapidAPI-Host: emailcheck.p.rapidapi.com'
const res = await fetch('https://emailcheck.p.rapidapi.com/v1/verify?email=' + encodeURIComponent(email), {
  headers: { 'X-RapidAPI-Key': process.env.RAPIDAPI_KEY, 'X-RapidAPI-Host': 'emailcheck.p.rapidapi.com' }
});
const { score, deliverability, flags, didYouMean } = await res.json();

Reading the response

{
  "email": "ayam.khan@gmail.com",
  "canonical": "ayamkhan@gmail.com",
  "validFormat": true,
  "score": 88,
  "deliverability": "deliverable",
  "flags": {
    "disposable": false, "roleAccount": false, "freeProvider": true,
    "hasMx": true, "hasARecord": true, "nullMx": false, "possibleTypo": false
  },
  "provider": "Google Workspace / Gmail",
  "didYouMean": null
}
FieldWhat it meansHow to use it
score0-100, weighted by the checks that firedGate signup below a threshold, e.g. 60
deliverabilitydeliverable / risky / undeliverableLog risky, block undeliverable
flags.disposableknown throwaway providerBlock, or allow on a trial tier only
flags.roleAccountshared inbox, not a personReject for account signups, keep for B2B contact forms
didYouMeantypo suggestion, same TLD onlyOffer a correction UI instead of rejecting

Pitfalls worth knowing before you ship

  • Catch-all domains accept every address, so they look deliverable. The flag set will not save you here; treat catch-all as risky.
  • Score thresholds are policy, not truth. A 70 is fine for a newsletter and too low for a billing contact.
  • Typo suggestions are deliberately conservative: same TLD, edit distance of two or less. It will not suggest gmail.com for hotmail.com because those are different products.
  • Bulk is one call for up to 100 addresses. For a list, use /v1/bulk and keep the per-address reasons; do not loop the single endpoint 100 times.

If all you need is the blocklist itself, it is free: 10,400 disposable domains as plain text or JSON, no signup.

The bulk maths

One call to /v1/bulk verifies up to 100 addresses. Against a credit-pack vendor charging roughly half a cent per address, a bulk call works out about ten times cheaper per address. If you are checking a single signup, the per-call price is the wrong shape for you and a credit pack will be cheaper. The maths is laid out with sources on the pricing comparison page.

Where this fits

Run it on signup, on list import, and before any campaign send. Store the score, not just the boolean, so you can re-decide later without another request.

Try EmailCheck

Pay as you go at $0.05 a call, no monthly minimum. or a monthly plan from $25 once the volume justifies it.

Open the listing on RapidAPI