For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Contact SalesGet Support
HomeGuidesAPI reference
HomeGuidesAPI reference
  • Get started
    • Quickstart—Verify a Business
    • Quickstart—Register an entity for payroll taxes
    • Learn how Middesk works
    • Security
    • Changelog
  • Build with Middesk
    • Get your API keys
    • Understand API changes
    • Status codes and errors reference
    • Implement webhooks
    • Secure webhooks
    • Use GraphQL
    • Connect MCP
  • Verify a business (KYB)
    • Verify TIN
    • Verify name and address
    • Verify Secretary of State status
    • Verify owners and officers
    • Screen for sanctions and watchlists
    • Search for adverse media
    • Search for Politically Exposed Persons
    • Implement KYC
    • Discover connections
    • Evaluate online presence
      • Analyze web presence
      • Verify business industry classification
      • Evaluate email risk
        • Email risk review tasks
    • Assess credit risk
    • Accelerate onboarding
    • Monitor business activity
    • Manage business entities
    • Work with agents
LogoLogo
Contact SalesGet Support
On this page
  • email_risk review task
  • Using email_risk in decisioning workflows
  • Recommended routing logic
  • Stricter decisioning for fraud-sensitive segments
Evaluate online presenceEvaluate email risk

Email risk review tasks

Was this page helpful?
Previous

Assess credit risk

Next
Built with

This page describes the email risk review task returned by the Middesk Email Risk API, which summarizes the overall risk of the email addresses submitted on a business.

email_risk review task

Summarize the overall risk of email addresses submitted on the business, based on indicators attached to each address.

statuslabelsub_label
SuccessEmail risk is lowLow
WarningEmail risk is moderateModerate
FailureEmail risk is highHigh

What each outcome signals:

  • Low. The submitted emails look clean; no elevated risk signals.
  • Moderate. Some risk signals detected; warrants attention but not automatically disqualifying (e.g. free email provider, data breach exposure, low account activity, etc.).
  • High. Strong risk signals; treat as a red flag in decisioning (e.g. disposable email, non-deliverable address, poor domain reputation, etc.).

Using email_risk in decisioning workflows

Use email_risk to drive routing in KYB onboarding, account opening, and ongoing monitoring workflows: separate businesses that can move through automated approval from those that need analyst review or stricter scrutiny.

Recommended routing logic

  • Automated approval. Treat the business as clear on email when the status is Success (Low).
  • Manual review queue. Route businesses with a Warning (Moderate) outcome to an analyst before approving.
  • Decline or step-up verification. Treat Failure (High) as a strong adverse signal. Combine it with other risk factors (business verification, watchlist hits, address risk) before a final decision rather than relying on email risk in isolation.

Stricter decisioning for fraud-sensitive segments

For high-risk MCCs, lending, or money movement, inspect the underlying email indicators directly. Signals like disposable email use, recent breach exposure, or low deliverability can each justify additional friction even when the rollup is Moderate rather than High.

Get a demo
Contact your account manager or contact sales to inquire about access.