Trace every address to the mailbox.
FazeVerify follows each address through six checks and hands back the verdict with the sentence that produced it. Nothing on your list is ever sent a message.
- Deliverable
- 43,870
- Risky
- 2,914
- Invalid
- 1,301
- Unknown
- 125
Every dot on this screen is an address. 91% came back deliverable.
It starts where the list already lives.
The address is taken apart before anything is asked.
We find the servers that actually take the mail.
We ask the mailbox, then hang up before delivery.
Four answers, and the reason for each one.
- Deliverable
- 43,870
- Risky
- 2,914
- Invalid
- 1,301
- Unknown
- 125
What leaves is the part you can send to.
Reads from where your list already is.
Verdicts are written back to the same place. No export, no re-import, and nothing to keep in step by hand.
Not listed? Tell us what you use — the API covers anything with an address in it.
Median bounce rate, either side of a first run
6.2%→0.4%
Twelve consecutive sends. The list was verified once, before the sixth.
Teams who send for a living, on what changed.
“Our bounce rate on the first send after a run. The part that sold the team was the reason column — we could see exactly what was wrong.”
“We wired the API into the signup form. Bad addresses never enter the database now, so there is nothing to clean up later.”
“Caught in a list we had been mailing for a year. That alone paid for it.”
“Unknown results are requeued instead of billed as invalid. That one decision is why the numbers match our own bounce logs.”
How many addresses a month?
verifications a month
For teams verifying continuously, in batches and on write.
- Unlimited verifications
- API and webhooks
- Trap and disposable detection
- Scheduled re-verification
- SSO and SAML
Unknown results are requeued and never billed.
How is an address actually checked?
We resolve the domain, look up its mail exchangers, open an SMTP conversation with the receiving server and ask whether the mailbox exists — then hang up before anything is delivered. Nothing on your list ever receives mail from us.
What does risky mean, and should I send to those?
Reachable, but with a reason to hesitate: a catch-all domain that accepts everything, a role account like info@, or a low-reputation host. Most senders keep them out of cold sends and include them in mail to people who asked to hear from you.
Can you detect spam traps?
Pristine and recycled traps, plus throwaway providers, reported separately from ordinary invalids — because the two need different handling. A trap is a reputation problem; an invalid is just a bounce.
What happens to my list after a run?
It is held for the retention window you set, or purged the moment the run completes if you choose that. Primary storage and backups are cleared on the same clock, and it is never pooled with anyone else's data.
Do I pay for results you could not determine?
No. When a server will not answer, the address comes back unknown, is requeued, and is never billed. Charging for a non-answer is how a verification bill stops matching your own bounce logs.
Can I verify at the point of signup instead of in batches?
Yes — one API call, about 300ms, fast enough to run inside a form submission. Most teams do both: on write so nothing bad gets in, and on a schedule because lists decay about 2% a month.
Run your list before it runs your reputation.
Upload one list free. Get a verdict and a reason for every address, and export the part you can send to.