Skip to content
← MailMaid Academy
Verification

What an email check can—and cannot—tell you

Short answer

Separate address formatting, mailbox evidence and inbox placement before making a send decision.

Start with the question#

An address can look correct while the mailbox is closed. A receiving server can accept a message and still put it in spam. Decide whether you are checking input quality, mailbox acceptance or message placement; each requires different evidence.

Keep the evidence visible#

MailMaid’s local checker identifies format issues, common domain typos and limited risk flags. It leaves plausible addresses unchecked. A configured provider adds its own verdict and reason. Keep that reason with the result instead of reducing every outcome to a green tick.

  • Review format failures.
  • Correct typos only after confirmation.
  • Keep unknown and risky records separate.

Use a result with context#

Before a campaign, combine the result with the contact’s source, permission and suppression status. Verification is one input to the decision. If the underlying mailbox was never checked, do not rename the local result “verified” in your CRM.

Keep reading

Verification

Disposable, role and free email: three different signals

Risk labels should explain a decision, not replace it.

2 min read
Verification

Why catch-all addresses belong in their own segment

A server accepting a recipient does not always establish that an individual mailbox exists.

2 min read
Bounces

Troubleshoot 4.4.2 without deleting the contact

A connection problem is different from evidence of a nonexistent mailbox.

2 min read