Guide · quality flags

Understanding risky emails: accept-all, disposable, and role

How ValidReach quality flags work — and how to write a clear risk policy your product and marketing teams can share.

Flags

What each signal means

Flags appear alongside top-level results in the dashboard, list jobs, and API.

Disposable

Temporary inboxes designed to be abandoned. High abuse and bounce risk after capture. Most teams block or challenge.

Accept-all

Domain accepts any local part. The mailbox may or may not exist. Treat carefully — often mark as risky and apply policy.

Role

Addresses like info@, sales@, support@. Valid mailboxes, but often shared and lower engagement for marketing.

Free

Consumer free-mail providers. Not automatically bad — useful signal for B2B vs B2C policies.

Policy patterns

Block, challenge, or allow — deliberately

Block

Disposable and clear undeliverable at signup when abuse risk is high.

Challenge

Ask for a work email, double opt-in, or CAPTCHA when flags fire.

Allow with limits

Accept free or role addresses for product use, but exclude from paid promos.

Document once

Write the policy for product and marketing so API, lists, and UI stay aligned.

Encode policy in code

Same flags in UI, lists, and API

Start free. Unknown results never burn credits.