Spam Check That Catches What Other Checkers Miss.

Yes. The widget above runs 4 spam-risk checks a day with no account and no card, and each one runs the full nine-point engine. Nothing is held back to upsell you.

Sign up free and you start with 1,000 credits, or 2,500 when your signup email is a work address. Credits are pay-as-you-go, never expire, and volume pricing is localized to your region.

Nine address-level signals, scored in parallel and rolled into one spam-risk verdict: syntax and format validation (RFC 5321 / 5322), domain existence and MX record presence, SMTP handshake and mailbox-exists ping, disposable-domain match (a top spam-trap source), role-address detection (info@, abuse@, postmaster@), catch-all domain detection, an AI-confidence pass on catch-all addresses, domain age scoring, and email authentication (SPF, DKIM, DMARC).

The catch-all resolution is the one most spam checkers skip, and it’s where 20 to 40 % of B2B email lists hide the risky addresses. If you just need to check one address at a time, the free email checker runs the very same engine.

We surface the strongest spam-trap signals: disposable and throwaway domains, role addresses, dead mailboxes that bounce, and catch-all domains that quietly accept everything. A high spam-risk verdict on any of those is your flag to drop the address before you send.

No tool can label a pristine spam trap with 100 % certainty from the address alone, because that is the whole point of a trap. What we can do is score the deliverability risk so the addresses most likely to be traps, recycled, or unreachable never make it onto your send list. That is how you protect sender reputation at scale.

An invalid address bounces, and the damage stops at your bounce rate. A spam trap accepts your mail and reports you. Recycled traps are abandoned mailboxes providers resurrect to catch senders with stale lists; pristine traps never belonged to a person at all and only exist to catch scraped or purchased data.

The check on this page flags the precursors of both: dead mailboxes before providers recycle them, and the disposable domains that feed trap networks. Re-run anything older than six months through the email verifier before a send.

Most mailbox providers start throttling senders above roughly a 2 % bounce rate, and Gmail and Yahoo’s bulk-sender rules require keeping spam complaints under 0.3 % to stay in the inbox. Spam-trap hits have no published threshold at all; a handful can sink a domain.

A pre-send check keeps you under every one of those lines. Strip the invalids so bounces stay near zero, and the trap-likely addresses so complaints never accrue. The free email validator cleans an entire list in one pass.

99.99 % on our 1,000-address benchmark, self-measured and including the catch-all domains where most checkers shrug. Accuracy matters more here than in plain validation: a false “safe” on a trap-adjacent address costs sender reputation, not just one bounce.

Free and paid run the identical pipeline; the free tier caps volume, never depth. The Email Verification API returns the same per-check breakdown, with an AI-confidence score on every catch-all verdict and volume pricing on the pricing page.

Yes. Upload a CSV and bulk processing scores roughly 10,000 emails per minute on the standard tier, flagging traps, disposables, and dead mailboxes row by row. Your 1,000 signup credits (2,500 with a work email) cover most small lists outright.

Lists decay, so re-check anything that has sat untouched for a quarter. For continuous screening, wire the REST API into your forms, or point an AI agent at the native MCP server and let it screen addresses without glue code.

No. Every address is checked in memory and gone the moment the verdict renders. We never log, retain, or resell what you paste, which matters when the list you’re screening is your customer data.

Verifox is SOC 2 Type II audited, and the privacy policy spells out exactly what touches disk. Spoiler: nothing you check on this page does.

No. This is an address-level spam check, not a message-content scanner. It tells you whether a given email address is risky to send to, a likely spam trap, disposable, or unreachable, not whether your subject line or body copy trips a spam filter.

The two work together: scan your copy with the spam content checker, and clean the recipient list here so your bounce and trap rates stay low. Good content sent to a dirty list still ends up in the junk folder, which is why the address check comes first.

Around 380 ms median for a single address, and under 50 ms when the result is cached. The verdict on this page lands inside two seconds end to end, including the SMTP handshake.

That speed is the point: a spam check only protects you if it can sit inline, screening a signup form or a CRM write before the bad address ever lands in your list. The API docs cover the real-time endpoint and its response shape.