An email risk checker scores how likely an email address is to be associated with fraud, abuse, or low-quality signups. Instead of returning a single yes/no answer, it produces a graded risk level (typically low, medium, or high) by combining many signals into one output.
The signals that feed risk scoring are familiar individually:
None of these signals is enough on its own. A real user might have an address on a free email provider with a random username. A fake user might have an address on an established domain that looks legitimate. The risk grade comes from how the signals combine, not from any single one.
When you submit an address, the lookup runs four steps:
The strongest individual signals for high-risk classification:
Disposable email providers. Mailinator, 10MinuteMail, and the long tail of throwaway services. By itself, this signal almost always lifts the grade.
Newly-registered domains. Domains under 30 days old are over-represented in fraud data. The combination of "new domain + non-disposable" is the most common pattern in coordinated fake-account attacks because operators register their own domains to evade disposable blocklists.
Suspicious username patterns. Random-character strings (h7k4j2qx@example.com) and high-entropy patterns are statistically unlikely to be human-chosen. Real users tend to pick name-shaped or word-based usernames.
Risky TLDs. Some top-level domains are over-represented in abuse data because they offer cheap bulk registration with weak abuse handling. The is_risky_tld flag captures the most extreme cases.
Breach history. An address that appears in recent large-scale breaches signals a real but compromised account. Risk scoring treats this as elevated for purposes of credential-stuffing detection but does not push individual signups to high-risk on the breach signal alone.
The grade is the combination, not any one of these on its own. A medium-risk grade means a few signals are firing but not enough for high-risk; a high-risk grade means several are stacked together.
Signup form gating: Block or step-up high-risk signups before they reach your user table. Route low-risk signups through the standard flow, medium-risk through additional verification (email confirmation, payment pre-auth, light identity check), and high-risk to manual review or outright block. This pattern catches most automated fake-signup waves without adding friction for real users.
Payment fraud prevention: Pair email risk with IP risk and behavioral signals at checkout. Email risk by itself is not enough to decline a transaction, but combined with mismatched billing/shipping IPs, brand-new accounts, or unusual cart patterns, it sharpens fraud detection without adding payment friction. Use the grade as one feature in a risk-scoring model, not as a hard gate.
Lead qualification and routing: For B2B SaaS with self-serve signup and an inside sales motion, email risk is a fast triage signal. Low-risk inbound leads from established domains get priority SDR outreach. Medium-risk signups go to automated nurture. High-risk signups (disposable, suspicious username, brand-new domain) are de-prioritized or filtered. This protects sales capacity for the leads most likely to convert.
Abuse pattern detection in existing accounts: Run risk scoring against accounts already in your database, not just at signup. Patterns shift; an address that looked low-risk a year ago can move to medium-risk if its domain hits abuse data later. Periodic re-scoring catches accounts created during a time when the operator's pattern was not yet recognized, and it surfaces clusters of suspicious accounts that signed up close in time with similar signal profiles.
curl --request GET \
--url https://emailreputation.abstractapi.com/v1{
"email_address": "benjamin.richard@abstractapi.com",
"email_deliverability": {
"status": "deliverable",
"status_detail": "valid_email",
"is_format_valid": true,
"is_smtp_valid": true,
"is_mx_valid": true,
"mx_records": [
"gmail-smtp-in.l.google.com",
"alt3.gmail-smtp-in.l.google.com",
"alt4.gmail-smtp-in.l.google.com",
"alt1.gmail-smtp-in.l.google.com",
"alt2.gmail-smtp-in.l.google.com"
]
},
"email_quality": {
"score": 0.8,
"is_free_email": false,
"is_username_suspicious": false,
"is_disposable": false,
"is_catchall": true,
"is_subaddress": false,
"is_role": false,
"is_dmarc_enforced": true,
"is_spf_strict": true,
"minimum_age": 1418
},
"email_sender": {
"first_name": "Benjamin",
"last_name": "Richard",
"email_provider_name": "Google",
"organization_name": "Abstract API",
"organization_type": "company"
},
"email_domain": {
"domain": "abstractapi.com",
"domain_age": 1418,
"is_live_site": true,
"registrar": "NAMECHEAP INC",
"registrar_url": "http://www.namecheap.com",
"date_registered": "2020-05-13",
"date_last_renewed": "2024-04-13",
"date_expires": "2025-05-13",
"is_risky_tld": false
},
"email_risk": {
"address_risk_status": "low",
"domain_risk_status": "low"
},
"email_breaches": {
"total_breaches": 2,
"date_first_breached": "2018-07-23T14:30:00Z",
"date_last_breached": "2019-05-24T14:30:00Z",
"breached_domains": [
{ "domain": "apollo.io", "date_breached": "2018-07-23T14:30:00Z" },
{ "domain": "canva.com", "date_breached": "2019-05-24T14:30:00Z" }
]
}
}An email risk checker scores how likely an email address is to be associated with fraud, abuse, or low-quality signups. Instead of returning a single yes/no answer, it produces a graded risk level (typically low, medium, or high) by combining many signals: whether the address is disposable, whether the domain is newly registered, whether the address appears in breach data, whether the domain accepts mail for any address, and whether the username pattern looks suspicious. The output is meant to feed risk-scoring systems, not to replace them.
Risk scoring combines multiple independent signals into a single grade. Each signal pulls the score in one direction. A disposable domain pushes risk up; an established domain pulls risk down. A randomly-generated username pushes risk up; a name-shaped username pulls it down. A domain registered last week pushes risk up; one registered ten years ago pulls it down. The Email Reputation API returns two grades: address_risk_status for the specific email, and domain_risk_status for the domain itself.
The strongest individual signals for high-risk classification are disposable provider domains, newly-registered domains (under 30 days), suspicious username patterns (random characters, high-entropy strings), known risky TLDs, and addresses that appear in recent breach data. No single signal is enough to mark an address high-risk on its own, but combinations are. A disposable address with a random username on a 7-day-old domain is almost certainly not a real user.
Yes. A low-risk grade means the obvious red flags are absent, not that the address is verified real. A patient fraud operator can register a domain, age it for a year, set up SPF and DMARC, and create human-looking aliases that score as low-risk on every automated check. Risk scoring catches the high-volume, low-effort attacks that make up most fraud. For high-stakes flows (payment, KYC, financial onboarding), pair email risk with IP risk, behavioral signals, and identity verification.
Disposable email detection answers one yes/no question: is this address from a known throwaway provider? Email risk scoring answers a broader question by combining the disposable signal with five or more others (breach history, domain age, catch-all status, role address, suspicious username, risky TLD). The risk grade is what most fraud and abuse systems actually want as input. The disposable flag is one feature inside the risk score, useful on its own only when you specifically want to gate by that single signal.
Accuracy depends on what you mean by accurate. The risk grade is calibrated to predict aggregate fraud rate, not individual outcomes. A medium-risk grade does not mean a specific address is 50% likely to be fraud; it means the population of medium-risk addresses converts to confirmed fraud at a measurably higher rate than low-risk and a lower rate than high-risk. Use the grade as one signal in a risk model, set thresholds based on your own conversion data, and revisit them as fraud patterns shift.