The deepest possible check is not automatically the right check. A good verification workflow spends more only when the next decision needs stronger evidence.

Start with the decision, not the tier

Ask what will happen after the result. A signup form needs a fast opportunity to correct a typo. A major outbound campaign needs broader domain context. A high-value one-to-one send may justify mailbox evidence.

That difference is why the verification API exposes three depths instead of forcing every address through the same path.

Where each depth fits

Quick covers address structure, domain and MX availability, disposable and role-based detection, classification, TLD risk, and name signals. Standard adds domain trust and infrastructure context. Deepcheck adds SMTP mailbox and catch-all verification.

  • Quick: inline forms and broad first-pass screening
  • Standard: CRM cleanup and campaign preparation
  • Deepcheck: priority prospects and critical communications

Use a progressive workflow

For a large, mixed-quality dataset, screen broadly first and escalate only the addresses whose value and uncertainty justify it. This keeps your policy easy to explain and your credit usage aligned with business value.

Put the framework into practice.

Start with 100 credits and inspect your own verification results. No card required.

Start verifying