What a verified business email actually tells you

Unknown is not invalid

Some providers cannot determine whether an address accepts mail. Catch-all domains can accept many addresses without confirming a specific person. Treat these states as uncertainty, not as evidence that an address is real or fake.

Read each status as a different decision

Hunter distinguishes valid, invalid, accept-all, disposable, and unknown results. “Valid” means the address passed its checks, but its own FAQ notes that verification is not a permanent guarantee because mailboxes and server behavior can change. “Invalid” is a negative result. “Accept-all” means the domain accepts many addresses, so the specific mailbox may still be uncertain. “Unknown” means a check could not reach a conclusion.

For a small, high-relevance campaign, this suggests a clear policy: use an exact recently verified address when available; do not equate unknown with invalid; do not promote accept-all to “verified”; and leave an unavailable address out rather than inventing one. The policy should be visible at the recipient level, not hidden in an aggregate list-health percentage.

Research: Hunter verification statuses · Hunter verification FAQs

Other checks matter

• Syntax: is the address structurally valid?
• Domain: does the domain accept mail?
• Disposable and role accounts: does the address represent a person you intend to reach?
• Suppression: has this person or company already opted out or been excluded?

Do not guess missing addresses

Generating an email pattern from a name and domain is not verification. If no exact verified address is available, stop at the contact record rather than presenting a guessed address as a finding.

Quality is per contact

A single campaign percentage hides the risk in individual rows. Show each recipient’s state and source beside the company reason so the workflow can make the right decision for that person.

Verification is not sender authentication

Even an accurate recipient address will not rescue a poorly configured sending domain. Google’s sender guidance requires SPF or DKIM for all senders and SPF, DKIM, and DMARC for bulk senders to personal Gmail accounts. It also recommends respecting recipient preferences and avoiding unwanted messages. Those are sender-side controls; they answer a different question from whether an address exists.

Treat the three layers separately: is this company relevant, is this the right person and address, and is the sending system configured and operated responsibly? A green status on one layer should not be used to imply the other two are solved.

Research: Google email sender guidelines

Permission, suppression, and legal obligations still apply

Verification does not create consent. Commercial-email rules depend on jurisdiction, message purpose, and audience. In the United States, the FTC states that CAN-SPAM has no business-to-business exception and requires, among other things, accurate headers, a way to opt out, and honoring opt-out requests. Teams operating elsewhere should check the rules that apply to their recipients and sending organization.

Keep an organization-wide suppression record separate from address verification. An address can be technically valid and still be prohibited from your campaign because the person opted out or the account is excluded.

Research: FTC CAN-SPAM guide