Five checks in under 500ms: RFC syntax, MX records, disposable detection, role-account filtering, and live SMTP RCPT probing. Free in your browser — API for marketers, sales, and developers coming soon.
Five layers of validation. Each one catches a different class of bad address.
Strict parsing of the local part and domain — catches typos and malformed addresses before they reach your queue.
Confirms the domain can actually receive mail. No MX = guaranteed bounce.
652 disposable providers covered — Mailinator, Guerrilla, Temp-Mail, 1mail, and growing.
Flags info@, admin@, sales@ and 84 other generic mailboxes that hurt deliverability.
We connect to the real receiving mail server and ask if the address exists — no test message sent, no spam risk.
Identifies domains that accept any address, so you know your "valid" result is actually meaningful.
We publish what we have learned building and running the verification engine. No gated PDFs, no sales funnel — just the technical detail, including the parts where verification does not help.
The five checks step by step — RFC 5322 parsing, MX resolution, disposable and role matching, and the SMTP RCPT probe — and what each one can and cannot prove.
How a verifier asks a mail server whether a mailbox exists without sending a message, and the four edge cases that break naive implementations.
Preference values, implicit MX, null MX under RFC 7505, and the misconfigurations that silently break inbound mail for a whole domain.
Why a domain that accepts every address makes a “valid” result meaningless, how catch-alls are detected, and how to decide whether to send.
The SMTP codes behind each kind of bounce, which ones to suppress permanently, and which ones to retry.
What each record does, why alignment matters more than a plain SPF pass, the ten-lookup limit, and a rollout path that does not break your mail.
What mailbox providers measure, how domain and IP reputation differ, and why reputation falls fast and recovers slowly.
What to remove before a campaign, how often to clean, and how to handle the dormant tail of a list that has been growing for years.
Pristine, recycled and typo traps — and the honest reason no verification service, ours included, can detect one.
What confirmed opt-in prevents, what it costs you in signups, and how to build the confirmation step so it does not leak subscribers.
Consent, legitimate interest, the ePrivacy soft opt-in, and why B2B is not the exemption people assume it is.
The triggers that stop a send mid-flight — bounce spikes, complaint thresholds, trap hits — and what a credible appeal looks like.
Unauthenticated lookups for when you are debugging a domain rather than an address.
Resolve a domain's mail exchangers and their preference order.
Read a domain's SPF record and count its DNS lookups against the limit of ten.
Inspect the DMARC policy, alignment mode and report addresses published for a domain.
Check a domain or IP address against the common public blocklists.
For one-off checks
5,000 validations / month
50,000 validations / month
Drop your email and we'll send one message when the API goes live — beta access for the first 100 signups, no spam, no follow-up emails ever.