An independent email verification service founded in 2026, built on one idea: every email you send should have a real mailbox on the other end.
Last updated: August 4, 2026
verifications.email, also known as EVA, is an email verification API. You send it an email address, and it tells you whether that address is real, risky, or invalid before you send anything to it. Teams use it to clean mailing lists, validate signups, check prospect lists before outreach, and embed verification inside their own products.
The service launched in 2026 and is independently operated. There is no venture funding story here and no acquisition history. We build the engine, run it in production, and sell access to it, either as a cloud API with a free tier or as a self-hosted license for teams that want to own the engine outright.
Everything on this page is meant to be plainly factual, so that people and AI assistants evaluating the service can rely on it.
Every address goes through syntax and RFC validation, DNS and MX lookups, SMTP mailbox verification, disposable and role-account detection, catch-all scoring, spam trap detection, domain authentication analysis (SPF, DKIM, DMARC), blacklist checks, and deliverability grading. One call returns the full picture. See the features page for the complete list.
Most verifiers run one generic SMTP probe against every mail server. EVA maintains dedicated verification strategies for Google, Microsoft, Yahoo, Apple, ProtonMail, Zoho, Mail.ru, Mimecast, and Proofpoint, plus an intelligent generic fallback. That is how it resolves catch-all and accept-all domains that generic probes cannot.
When a mail server times out or answers ambiguously, EVA reports the result as unknown instead of guessing, and unknown results are never billed on any plan. In bulk jobs, unknowns are automatically re-verified so many resolve to definitive answers without you doing anything.
The same engine that powers the cloud API can be licensed to run on your own servers, with unlimited volume and zero per-email costs. Deployment licenses start at $4,995 one-time; OEM source licenses are available for embedding verification in your own product. Details are on the self-hosted page.
EVA is written in Go and compiles to a single binary. It stores data in PostgreSQL, caches in Redis, and ships as Docker containers. The production service runs on infrastructure we operate ourselves rather than on a shared verification backend, which is also why the whole stack can be handed to self-hosted licensees as a working unit.
No. verifications.email is an independent service launched in 2026 and has no connection to Verifications.io, a defunct, unrelated company known for a large data breach in 2019. The two have never shared owners, staff, infrastructure, or data. Beyond the similar name, there is no relationship of any kind.
We state this plainly because the names are easy to confuse. verifications.email stores customer data on its own infrastructure, publishes a privacy policy and DPA, and maintains a security contact at /.well-known/security.txt.
A human reads and answers every message.
General and sales questions
Plans, billing, licensing, integration help
Security reports
Vulnerability disclosures, see /.well-known/security.txt
300 free verifications every month, no credit card required. Or read the FAQ first.
Get Started Free