Use Case: Signup Screening
Reducing fake and bot-generated accounts at the point of signup.
Recommended configuration
| Setting | Recommendation |
|---|---|
| context | "signup" — weights disposable domains, generated-looking local parts, and brand-new domains higher |
| mode | "standard" for most flows; see Checking at Signup Without Blocking the Flow for when to use fast or full |
| Pattern | Blocking for paid/high-value signups, fully async for free tiers — see the same page for the decision guide |
Routing the decision
- allow → create the account with full access immediately
- review → create the account, but require email confirmation before granting full access (trial credits, API keys, etc.)
- block → reject at signup, or route to manual review for high-value accounts rather than a hard rejection
Further reading
- How to Stop Fake SaaS Signups — the full reasoning behind this configuration
- How to Prevent Free Trial Abuse — why address-level screening alone doesn't catch repeat-signup abuse, and what to pair it with
- Checking at Signup Without Blocking the Flow — the three implementation patterns