Email verification
Verify before sending. Preserve every suppression.
Check contact addresses before enrollment, keep risky records out of active sending, and use MailSequence verification or connect a supported provider you already pay for.
Built into the contact workflow·Platform or bring-your-own verification·Suppression-safe imports
Before the sequence
Make list quality part of every campaign.
Verify where contacts live
Run verification from the contact workflow instead of exporting a list, cleaning it elsewhere, and importing another version.
See usable outcomes
Separate valid, invalid, catch-all, unknown, and disposable results so operators can make an explicit sending decision.
Protect prior decisions
Imported suppressions stay suppressed. Verification and deduplication do not silently reactivate a contact that should not be mailed.
Provider choice
Use the default verifier or connect your provider.
Use MailSequence verification when the platform service is available. Teams with an existing provider account can connect its API key instead.
- Platform-default verification when configured
- Bring Clearout, Bouncify, NeverBounce, or MillionVerifier
- LeadMagic connection supports verification and enrichment
- Your active workspace provider takes precedence
What verification can prove
Verification reduces avoidable bounce risk. It cannot guarantee delivery.
A technically valid mailbox can still ignore, reject, filter, or complain about a message. Good verification belongs beside authentication, relevant targeting, conservative volume, suppression, and responsible copy.
What it helps prevent
Obvious invalid and disposable addresses entering active sending, duplicate cleanup work, and suppression loss during migration.
Limits of verification
Verification cannot confirm intent, relevance, engagement, domain reputation, inbox placement, or whether a catch-all server will accept a specific recipient.
Need to interpret delivery failures? Read the bounce rates and suppression guide.
FAQ
Frequently asked questions
Is email verification included?
MailSequence supports platform-default verification when it is configured for the service. If you connect your own provider, that vendor subscription and usage are billed by the provider separately.
Which verification providers can I connect?
Supported verification connections include Clearout, Bouncify, NeverBounce, MillionVerifier, and LeadMagic. Availability may depend on the provider account and API access you bring.
What happens to invalid or disposable addresses?
They can be kept out of active sending through suppression. Existing suppressions are preserved during supported imports and are never silently reversed by deduplication or verification.
Should I send to catch-all or unknown addresses?
Review these addresses before sending. A catch-all domain can accept mail broadly even when the individual mailbox does not exist. An unknown result may warrant review or a later retry.
Does verification guarantee inbox placement?
No. It reduces one source of bounce risk. Authentication, domain history, sending behavior, recipient response, content, and list relevance still affect delivery.
Clean the audience before the first send.
Verify contacts, preserve suppressions, and combine list hygiene with authenticated business inboxes.