Stop fake accounts and new account fraud at signup
{
"email": "new_user@tempmail.io",
"deliverability": "DELIVERABLE",
"quality_score": 0.01,
"is_valid_format": true,
"is_free_email": false,
"is_disposable_email": true,
"is_role_email": false,
"is_mx_found": true,
"is_smtp_valid": false
}
Score every new account against email, phone, and IP risk signals in real time, and stop fake signups before they reach your database.
.svg)
How fake account detection works
Why teams catch fake accounts at signup
More Abstract data tools
The best build
on Abstract
Fake account detection guides
Frequently asked questions
What is new account fraud?
New account fraud is when someone opens an account with fake, stolen, or disposable identity details to abuse your product. It covers bot signups, trial and promo abuse, and accounts created to launder activity. Catching it at signup protects your funnel, your metrics, and your margins.
How do you detect fake accounts at signup?
Score the identity a user submits before you create the account. Check whether the email is disposable or free, whether the phone is VOIP or unreachable, and whether the IP is a VPN, proxy, or data-center address. Together those signals flag most fake signups in real time.
Which signals identify a fake account?
The strongest signals are a disposable or newly registered email, a VOIP or invalid phone number, and an IP tied to a hosting provider, VPN, proxy, or Tor exit. Abstract returns each as a clear true or false flag, not one opaque score, so you write your own rules.
Can fake account detection run in real time without adding friction?
Yes. Each check is a single request that returns in well under a second, so you can score every signup silently in the background. Only accounts that cross your risk threshold get extra verification, so real users pass through untouched while suspicious ones are challenged.
Does blocking fake accounts hurt real signups?
It should not, if you score instead of hard-blocking. Weight the signals, challenge medium-risk signups with a verification step, and reserve outright blocks for the clearest cases. Tuning the threshold to your own tolerance keeps false positives low while still stopping most abuse.
What is the difference between fake account detection and bot detection?
Bot detection asks whether traffic is automated. Fake account detection asks whether the identity behind a signup is real. They overlap, since many fake accounts are bot-created, but identity signals like disposable email and VOIP phone catch fakes that a bot check alone would miss.
How do I add fake account detection to my signup flow?
Call Abstract's Email Validation, Phone Validation, and IP Intelligence APIs when a user submits your signup form, then combine the returned flags into a risk score before creating the account. Each is a single request, and you can start on the free tier with no credit card.
