Continuous Deliverability Watch

Deliverability Monitoring Catches Decay Before Bounces

The mail monitor for email deliverability that re-runs MX, SMTP, mailbox, and SPF, DKIM, DMARC checks on every address. Same 9-point engine as our paid API, 99.99% accuracy.

Free to try. No signup, no card.

Trusted by 500,000+ leading GTM teams of all sizes

Baseline, sweep, repeat

How email deliverability monitoring works

No signup, no card. Paste any address, get a deliverable or bounce verdict in seconds, and repeat on a cadence to catch list decay early.

001INPUT

Paste the address

Drop any email into the pill — Gmail, Outlook, custom domains, or role aliases like info@ and sales@. Verify one address free right now, or upload a CSV to check a whole list once you sign up.

002ENGINE

Run the 9-check engine

Nine checks fire in parallel: syntax, DNS, and MX records, a live SMTP handshake, catch-all and disposable detection, role and domain-age signals, mailbox state, and email authentication. The full verdict then lands in about two seconds.

003VERIFY

Verdict in 2 seconds

Every address comes back valid, invalid, or risky, with the format, address type, server status, and mailbox status called out on the page. The API returns the same verdict with a 0-100 confidence score and the full per-check breakdown.

The plain-English version

What Email Deliverability Services Monitor

Same nine checks as the one-off test, run on a schedule so decay never builds up silently.

Deliverability monitoring is the address side of list health, run on a schedule. Most monitoring tools cover blacklist status and sending reputation — the right first half, but they skip the addresses. Mailboxes decay constantly: people change jobs, inboxes get retired, and 20 to 40% of B2B lists quietly fail at catch-all domains that accept every probe. The nine-check sweep catches those before they bounce.

The 9-point engine

Nine checks, one verdict

The same nine-check engine our paid email verification API runs. Every email, every verification, every time.

  1. 01

    Syntax

    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 [email protected], 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 [email protected]?” instead of rejecting silently.

    /dashboard/verify
    The Verifox dashboard verifying matthamnett@avencera.ai: the Syntax tile is ringed in the nine-check result board, beside a card showing the parse of matthamnett @ avencera.ai against RFC 5321 and RFC 5322, verdict “Valid format”.
  2. 02

    Domain & MX

    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.

    /dashboard/verify
    The Verifox dashboard verifying matthamnett@avencera.ai: the MX Record tile is ringed in the result board, beside a card showing the real MX 0 record avencera-ai.mail.protection.outlook.com on Microsoft 365, verdict “MX record found”.
  3. 03

    SMTP handshake

    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.

    /dashboard/verify
    The Verifox dashboard verifying matthamnett@avencera.ai: the SMTP Connect tile is ringed in the result board, beside a card showing the EHLO → MAIL FROM → RCPT TO exchange and the server’s 250 2.1.5 Recipient OK reply, verdict “Mailbox proven”.
  4. 04

    Catch-all detection

    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 ([email protected]); 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.

    /dashboard/verify
    The Verifox dashboard verifying matthamnett@avencera.ai: the Catch-All tile is ringed in the result board, beside a card comparing the real address (250 OK) with a deliberately fake probe (550 rejected), verdict “Validates recipients”.
  5. 05

    Disposable

    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.

    /dashboard/verify
    The Verifox dashboard verifying matthamnett@avencera.ai: the Disposable tile is ringed in the result board, beside a card showing the 10,247-provider throwaway blocklist and no match for avencera.ai, verdict “Legitimate domain”.
  6. 06

    Role address

    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.

    /dashboard/verify
    The Verifox dashboard verifying matthamnett@avencera.ai: the Role Address tile is ringed in the result board, beside a card matching the local-part matthamnett against the info@ / support@ / no-reply@ / admin@ role registry with no match, verdict “Personal address”.
  7. 07

    Domain age

    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.

    /dashboard/verify
    The Verifox dashboard verifying matthamnett@avencera.ai: the Domain Age tile is ringed in the result board, beside a card showing the WHOIS creation date 2025-07-10 against the 30-day fresh-spam threshold, verdict “1y old”.
  8. 08

    Email authentication

    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.

    /dashboard/verify
    The Verifox dashboard verifying matthamnett@avencera.ai: the DMARC tile is ringed in the result board, beside a card showing the real SPF include, DKIM selector1/selector2 and DMARC p=reject records, verdict “Aligned & enforcing”.
  9. 09

    Mailbox state

    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.

    /dashboard/verify
    The Verifox dashboard verifying matthamnett@avencera.ai: the Inbox Exists tile is ringed in the result board, beside a card showing the live 250 2.1.5 active reply against the full-inbox and disabled states that drive retry policy, verdict “Inbox confirmed”.
What it tells you

What an MX lookup reveals about a domain

An MX lookup is a read-only window into how a domain receives email. In one query you learn who runs the mail, how it routes, and whether it can receive at all.

Verification engine
9

checks on every
address

The same DNS resolution the Verifox verification engine runs first on every address it checks.

Who runs the mail

The MX hosts name the provider — Google Workspace, Microsoft 365, Proofpoint, or a self-hosted server.

Routing and priority

Records return lowest-number-first, so you read the primary server and its fallbacks straight away.

A deliverability signal

No MX record, or a broken one, means mail bounces before it is ever sent.

The first deliverability step

An MX lookup starts the story; verifying the address confirms the mailbox itself is real.

Verify the mailbox itself

An MX lookup is only the first step. Verifying the address confirms the mailbox is real and deliverable.

Verify an address — free

Provider at a glance

The single most useful thing a mail exchanger lookup tells you — who to talk to about mail.

How we stack up

Verifox vs the
alternatives

Same nine-check pipeline, the highest published accuracy, credits that never expire, and an MCP server no competitor offers. Head-to-head with the two providers our buyers shortlist.

★ The complete monitorVerifox
NeverBounce99.0%
ZeroBounce99.6%
NeverBounceYes
ZeroBounceNever
NeverBounce1,000 / monthly
ZeroBounce100 / monthly
NeverBounce
ZeroBounce
NeverBounceFlagged only
ZeroBounceAI scoring
NeverBounce
ZeroBounce
NeverBounce
ZeroBounce
NeverBounce
ZeroBounce
NeverBounce
ZeroBounce
Pricing

Pay once, or not at all

Most tools reset your balance every month. Verifox sells credits that sit in your account until you spend them.

FreeProve it on your own list before you spend anything.$0

forever

1,000credits on signup

No card required

2,500 with a work email

Free includes

  • All 9 checks included
  • Full API and bulk CSV
  • Catch-all confidence scoring
  • No card required
Most popular
Credit packsBuy once, spend whenever. Slide to price your list.$59

one time

10,000credits

$0.0059 eachSAVE 34%

Everything in Free, plus

  • Credits never expire
  • Verify or find from one pool
  • Up to 79% off at volume
  • No contract, no minimum
Verifox ONECredits land monthly and stack on your balance.$79

per month

15,000credits a month

$0.0053 each

Unused credits roll over

Everything in packs, plus

  • Unused credits roll over
  • Our lowest per-email rate
  • 50 requests per second API
  • Cancel anytime

One credit verifies one address; a find costs 10. All prices in USD, checkout via Stripe.

What teams are saying

Built for the teams that ship outbound

Growth leads, marketers, and engineers running real campaigns on real lists, with a verified email on every byline.

Thomas George, GTM Lead at Stripe

90% lower bill, 0.4% bounces

We were paying ZeroBounce a four-figure monthly bill and still landing 3% bounces on cold campaigns. Switched the pipeline to Verifox, dropped to 0.4% bounces, and cut the bill by more than 90%.
Thomas G.GTM Lead, Stripe
Brittany King, GTM Lead at HubSpot

Catch-all finally has a verdict

Other tools flag 30% of our B2B list as 'risky catch-all' and leave the call to us. Verifox returns a real verdict on those addresses, with a confidence score. We send more, we send safer.
Brittany K.GTM Lead, HubSpot
Dale Micallef, GTM Lead at Slack

Reputation rebuilt in 6 weeks

We had a Gmail spam-folder problem after a bad list import. Verifox cleaned the list and the warmup ran on the same engine. Back in primary inbox in six weeks. One vendor, half the cost.
Dale M.GTM Lead, Slack
Erica Kovalkoski, GTM Lead at Discord

0.7% bounce on 50k

Ran a 50,000-address outbound list through Verifox before our quarterly campaign. Bounces landed at 0.7%, sender reputation didn't move, replies were up 22% over last quarter.
Erica K.GTM Lead, Discord
Greg Lindsay, GTM Lead at OpenAI

MCP in 10 minutes

Their MCP server let me wire email verification directly into our internal Claude agent in about ten minutes. Zero glue code. No other vendor in this space has thought about that workflow.
Greg L.GTM Lead, OpenAI
Rini Vasana, Product Manager at Vercel

10k/min held under 400ms

Tested Verifox at 10,000 verifications per minute on a Tuesday morning. Latency held under 400ms median, no soft failures, no rate-limit walls. The vendor we benched throttled at 2,000/min.
Rini V.Product Manager, Vercel
Jonathan Aharon, GTM Lead at MongoDB

Hygiene that doesn't break pipeline

Our SDRs were enriching from three tools and 14% of the emails were invalid before they hit the sequencer. Verifox sits in the pipeline now and the team stopped seeing 'undeliverable' replies the next week.
Jonathan A.GTM Lead, MongoDB
Emma Fox, GTM Lead at Linear

Bulk that actually ships

Bulk upload, sorted CSV back in twenty minutes, plug into our growth stack. The half-day list-hygiene project per cohort turned into something the marketing intern runs on autopilot.
Emma F.GTM Lead, Linear
David Hare, GTM Lead at Snowflake

Scores you can act on

Verifox returns a 0-100 confidence score per address, not just a label. We thresholded at 75 for the cold sequencer, 60 for nurture, and our deliverability team finally has a knob they can tune.
David H.GTM Lead, Snowflake
Trust & compliance

Enterprise-grade security and scale

Every layer of the stack carries a third-party attestation, so you can ship into regulated industries without rebuilding your compliance posture.

  • Claymation Japanese hanko seal in jade-green clay with a twisted shimenawa rope rim, the words SOC 2 TYPE II embossed in cream clay on its face.

    SOC 2 Type II

    Independently audited to the SOC 2 Type II standard.

  • Claymation Japanese hanko seal in cobalt-blue clay with a twisted shimenawa rope rim, the word GDPR embossed in cream clay on its face.

    GDPR

    Built for the EU with full GDPR data-subject rights.

  • Claymation Japanese hanko seal in rose-pink clay with a twisted shimenawa rope rim, the word CCPA embossed in cream clay on its face.

    CCPA

    California opt-out, do-not-sell, plus DSAR handling.

  • Claymation Japanese hanko seal in terracotta clay with a twisted shimenawa rope rim, the text ISO 27001 embossed in cream clay on its face.

    ISO 27001

    Information security held to the ISO 27001 standard.

  • Claymation Japanese hanko seal in lilac-purple clay with a twisted shimenawa rope rim, the text ISO 42001 embossed in cream clay on its face.

    ISO 42001

    AI governance aligned to the new ISO 42001 standard.

Free field manual

The Dead List

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.

The Dead List field manual, held up by the Verifox fox
Get the free manual

57 pages, free PDF, no signup

Common questions

Deliverability monitoring, answered.

Common questions about deliverability monitoring: what changes between checks, how often to run sweeps, and where monitoring fits alongside one-time verification.

What is email deliverability monitoring?

Email deliverability monitoring means re-checking, on a schedule, the signals that decide whether your mail gets accepted: live mailboxes, valid MX records, a passing SMTP handshake, and SPF, DKIM, and DMARC authentication. A one-time list scrub answers those questions for a single day; monitoring keeps answering them as mailboxes die, DNS records change, and forms collect new junk.

Verifox runs nine checks per address on every pass, the same pipeline behind our email verification service, so a monitoring sweep is a full verification, not a cached lookup.

Is Verifox a mail monitor for email deliverability?

For the address and authentication side, yes. Classic mail monitor services watch your sending domain: blacklist listings and inbox placement panels. Verifox monitors what those services assume is already fine, whether the mailboxes on your list still exist and whether your SPF, DKIM, and DMARC records still pass.

The two halves complete each other. Run your sweeps here, then cover the domain-reputation side with the email blacklist check and the domain reputation checker.

Is the deliverability monitoring free to start?

Yes. The scanner on this page gives you 4 checks per day with no account and no card. That is enough to spot-check your own address and your highest-value contacts daily.

Sign up free and 1,000 credits land instantly, 2,500 if you register with a work address. From there credits are pay-as-you-go with volume pricing localized to your region.

Which deliverability signals does each monitoring pass cover?

Every address goes through nine checks in parallel:

  • Syntax and format (RFC 5321 / 5322)
  • Domain existence and MX records
  • SMTP handshake and mailbox ping
  • Disposable-domain match
  • Role-address detection
  • Catch-all detection, with AI-confidence scoring
  • Domain age
  • SPF, DKIM, and DMARC authentication

The authentication leg is the one most list tools skip entirely. If you only need that piece, the standalone DMARC, DKIM and SPF check runs it on its own.

How often should I monitor my list's deliverability?

Before every meaningful send, and at least monthly for any list you mail regularly. Addresses decay constantly: people change jobs, companies migrate domains, and inboxes get retired without notice. A list that verified clean a quarter ago is a different list today.

The expensive failure mode hides at catch-all domains, where 20 to 40% of B2B email lists actually fail. Those domains accept every probe a basic checker sends, so only the catch-all resolution with AI scoring catches the dead ones between sends.

Can I automate deliverability monitoring with the API or an AI agent?

Yes, that is how most teams run it. A scheduled job hits the REST API, sweeps the list at roughly 10,000 emails per minute on the standard tier, and routes anything that flips to undeliverable back into your CRM. Single checks return in about 380 ms, sub-50 ms when cached.

AI agents get the same engine with zero glue code through the native MCP server: point Claude, Cursor, or a custom agent at the MCP URL and the monitoring tools are wired.

Does monitoring cover my DNS and authentication records too?

Yes. The ninth check validates SPF, DKIM, and DMARC on the sending domain, and the MX leg confirms mail routing still resolves. DNS edits are the classic silent killer: one rewritten TXT record turns a passing SPF into a SoftFail, and nothing tells you until open rates sag.

For deeper single-purpose digging, the MX lookup, DKIM tester, and SMTP test each isolate one layer of the same stack.

What happens to the addresses I run through the monitor?

They are processed in memory and discarded the instant the verdict returns. Verifox never stores, logs, or sells the addresses you monitor, which matters when the list you are sweeping is your customer base.

The operation is SOC 2 Type II audited, and the privacy policy spells out exactly what is touched in transit. More than 2.1B emails have been verified under that model.

What does ongoing monitoring cost at volume?

One credit per address per pass, and credits never expire, so a monthly cadence wastes nothing if a sweep slips a few weeks. Volume rates step down as usage grows; exact numbers are shown for your region on the pricing page.

Uptime is backed by a 99.9% SLA on Starter and 99.99% on annual Volume contracts, with live status at status.verifox.ai.

How is monitoring different from a one-time deliverability test?

Same engine, different posture. A one-time deliverability test answers “is this address good right now?” Monitoring asks that question again next week, because the answer changes. The verdicts themselves are identical: deliverable, undeliverable, or risky, with a confidence score and a per-check breakdown.

If you want a single composite grade for an address instead of a recurring sweep, the email health checker frames the same nine checks as a one-shot report card.