Verifyre
Sign inStart free

Real-time verification

A full SMTP check in under two seconds.

Type an address, watch Verifyre resolve the domain, find the mail exchangers and ask the real mail server whether the mailbox exists. One credit, one honest answer, with the transcript to prove it.

Verify an email See pricing

1.4s median

Syntax, DNS and list checks run in parallel while the SMTP conversation opens. Most answers land well under two seconds.

The transcript, shown

EHLO, MAIL FROM, RCPT TO and every reply code. You see exactly what the server said instead of trusting a label.

A score, not just a label

Every signal rolls into a 0 to 100 score so you can set your own threshold for risky addresses.

Did you mean

Misspelt providers (gmai.com, hotmal.com) are caught and the corrected address is one click away.

Domain cache

MX, SPF, DMARC and catch-all facts are cached per domain so repeat checks at the same company are instant.

Same engine everywhere

The dashboard, the API, the form widget and the free tools all call the same verifier with the same verdicts.

What you see

The chamber: every stage settles in front of you.

Verifyre does not hide the work behind a spinner. Each pipeline stage reports as it finishes, the SMTP dialogue scrolls by live, and the verdict arrives with the reason spelt out.

  • Five stages, five answersSyntax, domain and MX, reputation lists, SMTP handshake and verdict each turn green, amber or red with a one-line explanation.
  • Nothing is ever sentThe conversation stops at RCPT TO. No DATA command, no message, nothing in the recipient's inbox.
  • Reason codes you can act onmailbox_not_found, catch_all, greylisted, disposable, role_based and more, each with plain-language copy and a status.
@sara.khan@lumenretail.comVerify
96
Deliverable
The mail server confirmed this mailbox exists and accepts mail.
deliverableGoogle Workspace
✓SyntaxRFC 5321 ok
✓Domain & MX2 exchangers
✓Reputationno flags
✓SMTP250 2.1.5 OK
✓Catch-allrejects unknown
0.00s·Connecting to aspmx.l.google.com:25
0.21s←220 mx.google.com ESMTP
0.22s→EHLO verifyre.co
0.43s←250-mx.google.com at your service
0.44s→MAIL FROM:<verify@verifyre.co>
0.65s←250 2.1.0 OK
0.66s→RCPT TO:<sara.khan@lumenretail.com>
0.91s←250 2.1.5 OK
0.92s→RCPT TO:<q7hd2kx9mzp4@lumenretail.com>
1.14s←550 5.1.1 The email account does not exist
1.15s→QUIT

How it works

Six questions, asked of the real mail server.

A database can only tell you what was true when it was built. Verifyre asks the server that would receive the message, right now.

  1. 01

    Syntax and normalisation

    RFC 5321 rules, provider-aware canonical form (dots and plus tags on Gmail) and typo detection against popular providers.

  2. 02

    Domain and MX

    Does the domain resolve, which hosts accept its mail, and in what priority? SPF and DMARC are read at the same time.

  3. 03

    Reputation lists

    10,000+ disposable providers, free mailbox providers and role prefixes such as info@ and sales@ are flagged.

  4. 04

    SMTP handshake

    Connect to the best MX on port 25, EHLO, MAIL FROM, RCPT TO. A 250 means the mailbox exists, 550 5.1.1 means it does not.

  5. 05

    Catch-all probe

    A random name at the same domain is tried. If the server accepts it too, the domain hides its mailboxes and the result is scored as risky.

  6. 06

    Score and verdict

    Every signal is weighed into a 0 to 100 score and one of four verdicts: deliverable, risky, undeliverable or unknown.

1.4smedian check time
676M+addresses verified
98%fewer bounces, typical
0emails sent during a check

FAQ

Real-time verification, explained

Visit the help centre
Does a real-time check send an email to the address?
No. Verifyre opens an SMTP session and issues RCPT TO, which asks the server whether it would accept mail for that mailbox. It then disconnects before any message is sent. The recipient never sees anything.
Why do some addresses come back as unknown?
Some providers refuse to confirm individual mailboxes (Yahoo blocks RCPT verification, for example) and some servers greylist unknown senders with a 450 reply. Verifyre reports exactly which happened instead of guessing, and a greylisted address can be re-checked a few hours later.
How is a real-time check different from the bulk cleaner?
Same engine, same verdicts. The real-time check verifies one address and streams the stages and the SMTP transcript to you; the bulk cleaner runs thousands in parallel with polite per-domain limits and gives you downloadable segments.
Can I call it from my own code?
Yes. The verification API returns the same status, reason, score, MX, provider and catch-all fields as JSON, at 120 requests a minute by default. Snippets for eight languages are on the developers page.
What does one real-time check cost?
One credit per live check. Results served from a fresh cache are free, and every account starts with 100 credits that never expire.

Related features

One request, every signal as JSON.

A REST API that returns status, reason, score, MX records, provider, catch-all and did-you-mean for any address.

Email verification API

Every address gets a 0 to 100 score, not a shrug.

Catch-all domains, greylisting, full mailboxes, role accounts and free providers all leave a trace.

Catch-all detection and risk scoring

Stop fake sign-ups at the source.

One script tag adds live validation to any form on any site.

Form validation widget

Try it on one address now.

No account needed for the first checks. Watch the SMTP conversation live on the homepage.

Verify an email See pricing