Email Verification

Stop Bounces Before You Ever Send.

Nine checks per address: SMTP handshake, catch-all AI score, domain age, SPF, DKIM and DMARC.

Three steps

Drop a list in. Get a list you can send.

No agent to install and nothing to configure. Paste one address, upload a CSV, or call the API, and every row comes back with a verdict.

001INPUT

Upload or connect

Drop a CSV, Excel, TXT, or Parquet file, paste addresses directly, or wire the REST API into your signup flow. Lists of 100 or 10 million both work, with no formatting cleanup first.

002ENGINE

Nine checks per address

Syntax, domain and MX, SMTP handshake, disposable match, role detection, catch-all detection, AI-confidence scoring, domain age, and authentication run on every address.

003VERDICT

Act on tagged results

Every address comes back valid, invalid, or risky with a confidence score. Download the clean CSV, drop invalids, and decide on riskies with the score in front of you.

The 9-point engine

Nine checks, one verdict

The same nine-check engine our paid email verification API runs. Every email, every verification, every time.

  1. 01

    Syntax

    Every address runs a full RFC 5321 and RFC 5322 compliance pass before a single network call goes out. The engine catches what visual scanning misses, the double dot in alice@verifox..ai, the trailing period, the IDN homograph that looks valid but resolves to a different domain.

    Bundled typo suggestions let your form offer “did you mean alice@gmail.com?” instead of rejecting silently.

    /dashboard
    The Verifox dashboard verifying matthamnett@avencera.ai: the Syntax tile is ringed in the nine-check result dialog, above a card showing the parse of matthamnett @ avencera.ai against RFC 5321 and RFC 5322, verdict “Valid format”.
  2. 02

    Domain & MX

    Once syntax passes, the engine resolves the domain. We confirm the DNS records exist, fetch the MX record priority list in order, and verify at least one mail-exchange server is actively accepting connections right now.

    Misspelled domains like gmial.com, expired domains, and parked-for-sale domains all fail this gate before the engine wastes a single SMTP roundtrip.

    /dashboard
    The Verifox dashboard verifying matthamnett@avencera.ai: the MX Record tile is ringed in the nine-check result dialog, above a card showing the real MX 0 record avencera-ai.mail.protection.outlook.com on Microsoft 365, verdict “MX record found”.
  3. 03

    SMTP handshake

    The engine opens a TCP connection on port 25, performs the EHLO handshake, then negotiates MAIL FROM and RCPT TO. Every server response code (220, 250, 550, 552) is parsed deterministically against the IANA enhanced-status registry.

    This is the moment a mailbox proves it actually exists. No third-party guesses, no statistical heuristics, just the receiving server's own answer.

    /dashboard
    The Verifox dashboard verifying matthamnett@avencera.ai: the SMTP tile is ringed in the nine-check result dialog, above a card showing the EHLO → MAIL FROM → RCPT TO exchange and the server’s 250 2.1.5 Recipient OK reply, verdict “Mailbox proven”.
  4. 04

    Catch-all detection

    Some domains accept every email regardless of whether the mailbox exists, a setup known as a catch-all configuration. The engine sends a deterministic probe to a deliberately fake address (zzz9k7q@domain.com); if the server returns the same 250 OK it returned for the real address, the domain is catch-all.

    The verdict isn't dropped, it's flagged RISKY so you know the deliverability signal is degraded.

    /dashboard
    The Verifox dashboard verifying matthamnett@avencera.ai: the Catch-All tile is ringed in the nine-check result dialog, above a card comparing the real address (250 OK) with a deliberately fake probe (550 rejected), verdict “Validates recipients”.
  5. 05

    Disposable

    The engine maintains a curated registry of 10,247 disposable email providers, including Mailinator, Guerrilla Mail, 10MinuteMail, Tempmail, and the long tail of regional clones.

    Any address matching the blocklist is flagged INVALID. Deliverability to a mailbox that exists for 10 minutes and is never checked is functionally zero, regardless of whether the SMTP handshake passes.

    /dashboard
    The Verifox dashboard verifying matthamnett@avencera.ai: the Disposable tile is ringed in the nine-check result dialog, above a card showing the 10,247-provider throwaway blocklist and no match for avencera.ai, verdict “Legitimate domain”.
  6. 06

    Role address

    info@, support@, no-reply@, admin@, billing@. These are shared inboxes, not individuals.

    The engine extracts the local-part of every address, matches it against the known role-prefix registry, and tags the result with a reduced engagement score.

    You don't drop them automatically. The verdict flags them as roles so you can decide.

    /dashboard
    The Verifox dashboard verifying matthamnett@avencera.ai: the Role Address tile is ringed in the nine-check result dialog, above a card matching the local-part matthamnett against the info@ / support@ / no-reply@ / admin@ role registry with no match, verdict “Personal address”.
  7. 07

    Domain age

    Fresh-spam domains registered hours ago are the single biggest source of inbound abuse. The engine queries WHOIS and RDAP for every unique domain, extracts the registration date, and flags anything under 30 days old with a “fresh” warning.

    Domains aged 5+ years pick up a corresponding trust signal. The same heuristic spam filters have been using since the early 2000s, ported into the verdict.

    /dashboard
    The Verifox dashboard verifying matthamnett@avencera.ai: the Domain Age tile is ringed in the nine-check result dialog, above a card showing the WHOIS creation date 2025-07-10 against the 30-day fresh-spam threshold, verdict “1y old”.
  8. 08

    Email authentication

    SPF, DKIM, and DMARC together prove the sender is authorised to send from that domain.

    The engine reads each policy via DNS, validates SPF includes recursively, scans six common DKIM selectors, and confirms DMARC alignment with the From: header.

    A failing DMARC policy means the sender can be spoofed, so the verdict warns you before you reply.

    /dashboard
    The Verifox dashboard verifying matthamnett@avencera.ai: the Authentication tile is ringed in the nine-check result dialog, above a card showing the real SPF include, DKIM selector1/selector2 and DMARC p=reject records, verdict “Aligned & enforcing”.
  9. 09

    Mailbox state

    Beyond “exists vs doesn't exist”, the engine extracts the precise mailbox state from the SMTP server's response. Full inbox (552 / 522 quota), disabled mailbox (550 5.1.1), out-of-office autoresponder, frozen account.

    Each state maps to a specific retry policy. Full inbox retries in 6 hours. Disabled drops permanently. The verdict tells you which bucket the bounce belongs in so your retry logic doesn't waste cycles.

    /dashboard
    The Verifox dashboard verifying matthamnett@avencera.ai: the Inbox Exists tile is ringed in the nine-check result dialog, above a card showing the live 250 2.1.5 active reply against the full-inbox and disabled states that drive retry policy, verdict “Inbox confirmed”.
The honest answer

What is email verification?

The whole page in one paragraph: what each check does, what comes back, and where the limits honestly sit.

Email verification is the practice of confirming an address can actually receive mail before you send to it. Verifox runs nine checks per address — syntax against RFC 5321 and 5322, domain and MX records, an SMTP handshake that pings the specific mailbox without delivering anything, disposable and role detection, catch-all detection, AI confidence scoring, domain age, and published SPF, DKIM and DMARC — and returns one verdict. Every address comes back valid, invalid, or risky, carrying a 0–100 confidence score you can sort a spreadsheet by.

Before and after

Five catch-all addresses, resolved

What catch-all addresses look like coming out of a standard checker, a flag-only tool, and the AI-confidence engine: a verdict and a score per address instead of a column of unknowns.

★ The accurate checkerVerifox
Accept-all flag onlyCatch-all
Standard verifierUnknown
Accept-all flag onlyCatch-all
Standard verifierUnknown
Accept-all flag onlyCatch-all
Standard verifierUnknown
Accept-all flag onlyCatch-all
Standard verifierUnknown
Accept-all flag onlyCatch-all
Standard verifierUnknown
The Verifox engine

Nine checks, one verdict, every address

From one pasted address to a full CSV, every check runs the same nine-layer engine and hands back a verdict you can send on.

Single check

Verify one email in seconds

Paste an address and the checker runs all nine deliverability layers (syntax to live SMTP) and hands back a verdict, a 0-100 confidence score, and the full check-by-check breakdown. You send to a confirmed inbox, never a hopeful guess.

/dashboard
Verifox verification result: a status badge and confidence score above a grid of the nine deliverability checks for a single email.
Bulk & CSV

Verify a whole list at once

Upload a CSV or paste a list, and the checker works the entire batch (the same nine-check engine on every single row), then returns a clean file split into valid, risky, and invalid, ready to export.

/dashboard/lists
Verifox bulk verification results for a 2,000-address list: 1,665 valid, 140 invalid, 144 risky and 51 unknown above a table of verified email addresses.
API & MCP

Drop it into your stack

One REST call verifies an address and returns the verdict as JSON , with cURL, Node, and Python examples ready to copy. Wiring an AI agent instead? The same verification ships as a native MCP server.

/api-docs
Verifox API reference: the Verify Email (GET) endpoint with a copy-ready cURL request, tabs for Node.js, Python, Ruby and C++, and the JSON response.
Analytics

Watch your list health over time

Every check you run rolls up into one activity view: volume, valid rate, and risk trends across single checks, bulk jobs, and API calls, so you catch a decaying list before it dents your sender reputation.

/dashboard/verify
Verifox Bulk Verifier overview: total lists, total emails, safe-to-send and deliverability stat tiles above two completed list cards.
One engine, every address

Everything the engine verifies

Nine checks run on every address, in parallel, on the free tier and the paid API alike. Volume is capped; the depth of the check never is.

Verification engine
9

checks on every
address

The same nine-check pipeline as the paid API runs on every address, free or not.

Valid, invalid or risky

One verdict, a confidence score, and the full breakdown.

Check a whole list

Bulk CSV in, verified list out. Same checks on every plan.

9 checks per address

Syntax to SMTP to SPF, DKIM and DMARC, on every row.

0-100 catch-all score

Accept-all domains get a confidence number, not an unknown.

Credits never expire

1,000 free on signup. 2,500 with a work email. Pay as you go after.

Start free

Your lists are never sold

Used only to run the verification. GDPR · CCPA.

Pricing

Subscribe and save, or pay as you go

Verifox ONE adds 15,000 credits to your account every month, and the ones you don't use roll over instead of resetting. Rather pay once? Credit packs never expire.

FreeProve it on your own list before you spend anything.$0

forever

1,000credits on signup

No card required

2,500 with a work email

Free includes

  • All 9 checks included
  • Full API and bulk CSV
  • Catch-all confidence scoring
  • No card required
Recommended
Verifox ONEFresh credits every month, stacked on your balance.$79

per month

15,000credits a month

$0.0053 each, $0.0044 billed yearly

Up to 25% less per credit than the 10,000 pack

Everything in Free, plus

  • Unused credits roll over
  • Pay yearly, get 2 months free
  • Verify or find from one pool
  • Cancel anytime
Credit packsBuy once, spend whenever. Slide to price your list.$59

one time

10,000credits

$0.0059 eachSAVE 34%

Everything in Free, plus

  • Credits never expire
  • Verify or find from one pool
  • Up to 79% off at volume
  • No contract, no minimum

One credit verifies one address; a find costs 10, a company search 100 and an email reveal 50. All prices in USD, secure checkout via Dodo Payments.

Prices are before tax. Any VAT, GST or sales tax your country charges is added at checkout. Buying as a business? Enter your VAT or GST number there.

Trust & compliance

Your data stays yours

The addresses you submit are used only to run your verification. They are never sold, and nobody on your list hears from us.

  • Claymation Japanese hanko seal in amber clay with a twisted shimenawa rope rim, the words NEVER SOLD embossed in cream clay on its face.

    Never sold

    The addresses you submit are never sold or shared.

  • Claymation Japanese hanko seal in violet clay with a twisted shimenawa rope rim, the words NO EMAIL SENT embossed in cream clay on its face.

    No email sent

    We ask the mail server. Not one message is sent.

  • Claymation Japanese hanko seal in cobalt-blue clay with a twisted shimenawa rope rim, the word GDPR embossed in cream clay on its face.

    GDPR

    Full GDPR data-subject rights for everyone in the EU and UK.

  • Claymation Japanese hanko seal in rose-pink clay with a twisted shimenawa rope rim, the word CCPA embossed in cream clay on its face.

    CCPA

    California opt-out, do not sell and DSAR handling.

Free field manual

The Dead List

An investigation into the money leaking out of your list - and the nine checks that decide whether your email is read, or never arrives at all.

The Dead List field manual, held up by the Verifox fox
Get the free manual

57 pages, free PDF, no signup

Common questions

Verification, answered straight

What teams ask before trusting us with a list: how the checks work, what catch-all really means, and where the limits sit.

What does email verification actually check?

Nine things per address: syntax and format against RFC 5321 and 5322, domain existence with MX records, an SMTP handshake that pings the specific mailbox, disposable-domain match, role-address detection, catch-all detection, AI-confidence scoring on catch-all addresses, domain age, and email authentication records (SPF, DKIM, DMARC). You can watch all nine run on a single address in the free email checker.

What does Verifox email verification check?

Nine checks per address: syntax, domain and MX, a live SMTP handshake that pings the mailbox, disposable domains, role addresses, catch-all detection with a 0-100 confidence score, domain age, and SPF, DKIM, and DMARC. Catch-all domains get scored rather than skipped.

The free widget on this page, the single email verifier, and the paid API all run the exact same engine. Free tiers cap volume, never depth.

How fast can I verify a large email list?

It depends on the mail servers behind your list, because every address waits for a real answer. Upload the list and it runs as one bulk job. For pasting a batch by hand, the multiple email checker handles small lists without an upload.

What is a catch-all domain and why does it break most verifiers?

A catch-all domain accepts mail for every address, real or invented, so the standard SMTP question “does this mailbox exist?” always comes back yes. Most tools shrug and mark the whole domain “unknown.”

That gap matters: 20 to 40% of B2B lists fail at catch-all domains. Verifox scores those addresses individually with AI-confidence analysis. Test one yourself on the catch-all email checker.

Do you store or sell the emails I verify?

We never sell them. Addresses you verify are used only to run the verification and show you the result. The privacy policy and security page document exactly what we touch and what we never do.

How much email verification can I do for free?

Three free layers. The widget on this page and the free email checker allow 4 checks per day with no account at all.

Signing up adds 1,000 free credits, or 2,500 if you register with a work address. No card required, and paid credits on every plan never expire.

Can I verify email addresses in real time through an API?

Yes. The REST API returns a full nine-check verdict. Endpoints, SDKs, and a sandbox live in the API docs. AI agents can skip the glue code entirely with the native MCP server, and FoxGuard drops the same checks onto any web form as a widget.

How often should I re-verify my email list?

Before every major campaign, and monthly for lists you mail regularly. Addresses decay constantly as people change jobs and domains lapse, so a list verified a quarter ago is not a verified list. Between cleans, run sends through the email bounce checker and re-verify the moment bounces creep above 1%.

What is the difference between email verification and email validation?

In practice the words get used interchangeably, but validation often means format-only checks: does the string look like an email address. Verification goes further and talks to the receiving mail server to confirm the mailbox exists and can accept mail. Verifox does both on every check. Compare the free email validator and the email verifier to see the same engine framed for each job.

Why do verified lists still get a few bounces?

Because mailboxes die between the day you verify and the day you send. Greylisting, full inboxes, and sudden domain changes can also bounce a genuinely valid address. Expect a residual rate near 1% on a freshly cleaned list, not zero. If bounces stay high after cleaning, the problem is usually your sending domain's reputation; run it through the email blacklist check to rule that out.