Identify disposable email signals before accepting an address
Review disposable-domain indicators together with syntax, domain checks, and risk recommendations. Decide whether a temporary address fits your product’s policy.
Signals for a decision you control
`DISPOSABLE_DOMAIN` comes with the rest of the evidence — domain age when on record, mail setup, and typo suggestions — so you can tell a throwaway provider from an unfamiliar but real one.
Disposable-domain signals
Use known disposable-domain classifications as one input to your acceptance policy. Coverage can change as services and domains change.
Context for uncertain addresses
Inspect domain and mail-routing signals rather than assuming every unfamiliar provider is abusive.
Clear user decisions
Explain your permanent-address requirement when rejecting a signup. Offer review or further verification when evidence is uncertain.
A recommendation with the reasons behind it
Use the score and supporting signals to decide what your application should do next. Risk scores and recommendations do not prove mailbox ownership, human identity, or successful delivery.
Fewer detected concerns in the evaluated signals. Use mailbox ownership verification when your workflow requires it.
Review the reasons and choose an appropriate check, such as confirmation by email. An unusual address is not itself proof of abuse.
Significant concerns such as malformed syntax or disposable-domain signals. Your application owns the final decision and any appeal path.
Recommendations describe observed risk signals. Choose the next action for your workflow; an allow result does not confirm mailbox ownership or successful delivery.
Practical questions
Does a disposable address prove abuse?
No. Temporary addresses can be used for privacy or testing. Decide whether they meet your product’s requirements.
Is a forwarding service the same as a disposable mailbox?
No. Privacy forwarding and aliases can be legitimate long-term choices. Review provider classifications and your own requirements rather than treating all forwarding as abuse.
Will every new disposable provider be detected?
No coverage guarantee is implied. New domains and changing provider infrastructure can affect detection; evaluate representative examples and review uncertain cases.
See the signals before choosing a policy
Inspect the result and its reasons, then connect the workflow that fits your application.