Fake Signups
Some miscreant fills out your signup form with "asdf jkl;" and a guerrillamail address. Another one uses a random name generator and a throwaway inbox. Your database fills up with garbage accounts that will never convert, never engage, and never come back. Some are bots, others are real humans just smashing the keyboard. Either way, they're wrecking your data and filling your database with garbage.
The Junk Signup Problem
Every product with a signup form attracts the riffraff. Some of it's automated, like bots creating accounts to spam, scrape, or stockpile credentials for later abuse. But a surprising amount comes from real people: tire-kickers who mash the keyboard to get past your form, uncommitted users who don't trust you with real data, and people who just want to peek behind the login wall without any commitment.
Either way, the result is the same. Your user table fills up with accounts that have no real identity behind them. Names like "test test" and "aaa bbb". Email addresses from disposable providers that will bounce within the hour. Profanities. Data that passes form validation but is completely meaningless.
The usual defenses don't solve this.
Fake signups are hard to prevent at the door because they come in many forms. They're usually a sign of bad behavior to come. To deal with the problem, you need a system that evaluates the quality and authenticity of each signup, not just its format.
Fake Signups Have Real Costs
Junk accounts aren't just clutter — they actively degrade your operations, your outreach, and your ability to understand what's actually happening in your product.
Polluted database
Fake accounts mix in with real users, making it harder to query, segment, and maintain clean data. Every downstream system that touches your user table inherits the noise — from analytics to billing to support tooling.Wasted outreach
Marketing emails sent to fake addresses bounce, hurting your sender reputation and deliverability scores. Your onboarding sequences, drip campaigns, and re-engagement efforts burn cycles on accounts that were never even real.Misleading metrics
Your signup numbers look healthy, but conversion is terrible. Product decisions based on these metrics lead you in the wrong direction. You'll think you have a conversion problem when you actually have a quality problem.How Dregs Detects Fake Signups
Fake signups are fundamentally a data quality problem. The account looks structurally valid but lacks basis in reality. Dregs evaluates the quality and plausibility of each signup at the moment of submission, catching the junk that form validation can't.
Authenticity Score
This is the primary signal for junk detection. The Authenticity score evaluates whether the submitted data looks like it belongs to a real person. Keyboard-mashed names ("asdf"), disposable email domains, names that don't resemble the email address, nonsensical character sequences, and data that's syntactically valid but semantically empty all drive the score down.
Human Junk vs. Bot Junk
Not all junk is created equal. A human who mashes the keyboard to bypass your form is annoying but probably not malicious. A bot creating hundreds of accounts to stockpile credentials is a different threat entirely. The Humanity score tells you which kind you're dealing with so you can respond proportionally, with added friction for lazy humans and hard blocks for aggressive automation.
Signup Flow Analysis
Real users browse before signing up. They read your pricing page, check out features, maybe visit the docs. Junk signups typically skip all of that — they land on the form, fill it out in seconds, and either leave or immediately start abusing the account. The Behavior score measures the depth of this engagement.
Serial Junk Detection
When the same person (or bot) is creating junk accounts one after another, they're typically using the same device. The Uniqueness score catches this pattern — even across different email addresses, names, and browsing sessions. One junk signup is a data quality issue. Five junk signups from the same device is a pattern you can act on decisively.
Example: Catching a Junk Signup
Here's what it looks like in practice:
No manual review needed... the junk signup is caught and handled within seconds of submission.
Quarantining Fake Signups
Detection is only half the story. How you handle junk signups depends on your product and your tolerance for false positives. Dregs gives you the scoring data to automate whichever approach fits.
Rejection
You could accept the signup on the surface but not actually provision the account. No onboarding email, no trial resources, no database clutter. The bogus user sees a confirmation page but nothing else works and they move on.
Verification
Require an additional verification step — phone number, real email confirmation, or payment method — for signups with low Authenticity scores. Legitimate users pass easily. Junk signers abandon when the friction increases.
Escalation
Route low-scoring signups to a manual review queue instead of rejecting them outright. Your team can check flagged accounts and approve the legitimate ones. Good for when false positives are costly, to err on the side of caution.
Cleanup
Let all signups through, but run periodic sweeps to purge accounts that scored below your thresholds and never engaged. This lighter touch approach keeps your database clean and fake usage under control without blocking signups.
The best time to deal with a fake signup is before it reaches your onboarding flow. Dregs webhooks deliver scores to your application instantly, so you can silently reject, quarantine, or flag junk accounts without wasting a single onboarding email or support cycle.
Fake signups are often a precursor to other abuse. If the junk accounts come from bots, see bot detection. If they're humans cycling through disposable emails, see free trial abuse.
Stop fake signups from polluting your data.
Dregs evaluates every signup for authenticity, humanity, and behavioral signals from the moment the form is submitted. Install the tracking script and junk accounts get flagged before they ever hit your onboarding flow.
Schedule a Demo