Paste the address
Drop in any address you plan to send to. Gmail, Outlook, custom domains and role inboxes all accepted, one at a time or in bulk.
Free Spam Filter Test
See what a spam filter sees before it decides: blocklists, SPF, DKIM, DMARC and mailbox reality.See what a spam filter sees before it decides: mailbox reality, spam-trap risk, SPF, DKIM and DMARC on our 9-point engine. No signup.
Three steps, no signup, no card. Paste an address you plan to send to, let the nine-check engine score the signals spam filters weigh, read the verdict.
Drop in any address you plan to send to. Gmail, Outlook, custom domains and role inboxes all accepted, one at a time or in bulk.
Nine checks weigh the sender signals a filter reads, from authentication and blocklists to disposable domains and role aliases.
Inbox, spam folder or blocked, named with the exact signal that tripped and a 0-100 risk score.
A filter decides on the sender before it reads a word. These are the nine signals our engine scores, the same ones Gmail, Outlook and SpamAssassin weigh when they choose inbox or spam.
Every address runs a full RFC 5321 and RFC 5322 compliance pass before a single network call goes out. The engine catches what visual scanning misses, the double dot in alice@verifox..ai, the trailing period, the IDN homograph that looks valid but resolves to a different domain.
Bundled typo suggestions let your form offer “did you mean alice@gmail.com?” instead of rejecting silently.


Once syntax passes, the engine resolves the domain. We confirm the DNS records exist, fetch the MX record priority list in order, and verify at least one mail-exchange server is actively accepting connections right now.
Misspelled domains like gmial.com, expired domains, and parked-for-sale domains all fail this gate before the engine wastes a single SMTP roundtrip.


The engine opens a TCP connection on port 25, performs the EHLO handshake, then negotiates MAIL FROM and RCPT TO. Every server response code (220, 250, 550, 552) is parsed deterministically against the IANA enhanced-status registry.
This is the moment a mailbox proves it actually exists. No third-party guesses, no statistical heuristics, just the receiving server's own answer.


Some domains accept every email regardless of whether the mailbox exists, a setup known as a catch-all configuration. The engine sends a deterministic probe to a deliberately fake address (zzz9k7q@domain.com); if the server returns the same 250 OK it returned for the real address, the domain is catch-all.
The verdict isn't dropped, it's flagged RISKY so you know the deliverability signal is degraded.


The engine maintains a curated registry of 10,247 disposable email providers, including Mailinator, Guerrilla Mail, 10MinuteMail, Tempmail, and the long tail of regional clones.
Any address matching the blocklist is flagged INVALID. Deliverability to a mailbox that exists for 10 minutes and is never checked is functionally zero, regardless of whether the SMTP handshake passes.


info@, support@, no-reply@, admin@, billing@. These are shared inboxes, not individuals.
The engine extracts the local-part of every address, matches it against the known role-prefix registry, and tags the result with a reduced engagement score.
You don't drop them automatically. The verdict flags them as roles so you can decide.


Fresh-spam domains registered hours ago are the single biggest source of inbound abuse. The engine queries WHOIS and RDAP for every unique domain, extracts the registration date, and flags anything under 30 days old with a “fresh” warning.
Domains aged 5+ years pick up a corresponding trust signal. The same heuristic spam filters have been using since the early 2000s, ported into the verdict.


SPF, DKIM, and DMARC together prove the sender is authorised to send from that domain.
The engine reads each policy via DNS, validates SPF includes recursively, scans six common DKIM selectors, and confirms DMARC alignment with the From: header.
A failing DMARC policy means the sender can be spoofed, so the verdict warns you before you reply.


Beyond “exists vs doesn't exist”, the engine extracts the precise mailbox state from the SMTP server's response. Full inbox (552 / 522 quota), disabled mailbox (550 5.1.1), out-of-office autoresponder, frozen account.
Each state maps to a specific retry policy. Full inbox retries in 6 hours. Disabled drops permanently. The verdict tells you which bucket the bounce belongs in so your retry logic doesn't waste cycles.


Modern spam filtering is reputation-first. Most of your spam score comes from who is sending, not what the message says.
Every message you send gets interrogated before a human sees it. The anti-spam filter at Gmail, Microsoft, or a gateway running SpamAssassin assigns a spam score from hundreds of rules, and the surprising part is how little of it comes from your words. Modern spam filtering is reputation-first: who is sending, from which domain, with what authentication, to what kind of list. A sender with a clean record can write “FREE!!!” in the subject and reach the inbox; a sender with a dirty record gets junked on a plain-text note. Your subject line is not what scores your message content.
Filters decide on the sender long before the subject line. This test reads the same signals they weigh, and names the one that would have flagged you.
Every signal is checked live against DNS and the mailbox, never a cached guess.
Paste either and the engine screens the sender behind it.
Authentication, blocklists, catch-all, role, domain age.
Inbox, spam folder or blocked, with the signal that tripped.
On signup, 2,500 with a work email. Credits never expire.
Score your sending domain free before your next campaign goes out.
REST API, or drop the MCP server into your agent.
Mail-Tester and GlockApps score a test send. Verifox measures the signals filters actually weigh, on credits that never expire.
Verifox ONE adds 15,000 credits to your account every month, and the ones you don't use roll over instead of resetting. Rather pay once? Credit packs never expire.
forever
1,000credits on signup
No card required
2,500 with a work email
Free includes
per month
15,000credits a month
$0.0053 each, $0.0044 billed yearly
Up to 25% less per credit than the 10,000 pack
Everything in Free, plus
one time
10,000credits
$0.0059 eachSAVE 34%
Everything in Free, plus
One credit verifies one address; a find costs 10, a company search 100 and an email reveal 50. All prices in USD, secure checkout via Dodo Payments.
Prices are before tax. Any VAT, GST or sales tax your country charges is added at checkout. Buying as a business? Enter your VAT or GST number there.
The addresses you submit are used only to run your verification. They are never sold, and nobody on your list hears from us.

The addresses you submit are never sold or shared.

We ask the mail server. Not one message is sent.

Full GDPR data-subject rights for everyone in the EU and UK.

California opt-out, do not sell and DSAR handling.
An investigation into the money leaking out of your list - and the nine checks that decide whether your email is read, or never arrives at all.

57 pages, free PDF, no signup
Common questions
What teams ask us when their mail starts landing in spam: how filters score senders, what a spam score really means, and which signals are worth fixing first.
An anti-spam filter is the software a mailbox provider runs on every incoming message to decide its fate: inbox, spam folder, or outright rejection. Gmail, Microsoft, and open-source filters like SpamAssassin score hundreds of signals, including sender reputation, authentication records, bounce history, recipient engagement, and finally the message content. Most of that score is settled before your subject line is even read, which is why sender hygiene beats clever wording.
Test the inputs filters weigh heaviest, in order. First, verify every address you plan to send to; the checker above runs 9 checks per address.
Then run a full email deliverability test to watch a real send behave, confirm your SPF, DKIM, and DMARC records, and score your sending domain with the domain spam checker. Clean results on those four put you ahead of most senders.
Reputation, usually. Filters track your domain's bounce rate, spam-trap hits, blocklist listings, and complaint rate, and they keep punishing the pattern long after the offending campaign ends. Content triggers still exist but carry far less weight than they did a decade ago. Start with an email blacklist check to see if you are on a blocklist, then scrub the invalid addresses that caused the bounces in the first place.
There is no universal score. SpamAssassin, the most widely deployed open-source filter, adds points per matched rule and treats anything above 5.0 as spam by default, while Gmail and Microsoft use machine-learned scores they never publish. That is why Verifox reports the sender signals every filter agrees on, mailbox validity, spam-trap risk, authentication, and domain reputation, instead of one number that only applies to one filter.
Yes, and they are the entry ticket rather than a bonus. Gmail and Yahoo have required SPF, DKIM, and DMARC for bulk senders since February 2024, and mail that fails alignment gets filtered or rejected before content is even considered. Verifox checks email authentication as one of its 9 verification points, and the dedicated SPF, DKIM, and DMARC checker reads your records back in plain English so you can fix what fails.
No, and treat any tool that promises a bypass as a red flag. Filters are probabilistic, private, and retrained constantly; nobody outside Google can guarantee a Gmail inbox. What you can do is remove every negative signal you control: send only to verified addresses, hold your bounce rate near zero, authenticate your domain, and stay off blocklists. That is the work the Verifox verification engine automates on every address you check.
Direction. An anti-spam filter sits on the recipient's side and judges incoming mail. A spam checker works on your side, before you send, predicting how those filters will treat you. Verifox is the second kind: it scores the addresses you send to and the domain you send from. To test one address for spam-trap risk, use check email for spam; for your own domain's reputation, the domain spam checker runs the same engine.
More than any other factor you control. Mailbox providers read a high bounce rate as a bot or a bought list, and one spam-trap hit can hold a domain in the filter's penalty box for weeks. 20 to 40% of B2B lists fail at catch-all domains, the check most free tools skip. Scrub whole lists with the free email validator before any send; it runs the same 9-point pipeline as this page.
Yes. You get 4 verifications a day on this page with no account. Create a free account and you get 1,000 credits once you verify your email, or 2,500 if you sign up with a work address. No card required. Past that, credits are pay-as-you-go and never expire, with volume discounts on larger packs.
Yes. The REST API returns the same 9-point verdict on a single address or a bulk list.
AI agents can skip the glue code entirely: Verifox ships a native MCP server, so Claude, Cursor, or any MCP client can verify addresses directly. Custom SLAs are available on annual Volume contracts.