Waitlist Health & Fraud Risk Auditor
Audit an existing waitlist CSV locally in the browser for disposable domains, plus-alias duplicates, and velocity spikes.
Select a subscriber CSV file
Active file: sample-waitlist-25-rows.csv (recognizes email, created_at, verified, referred_by)
Waitlist Health Score
13/100
Grade F
Clean deliverable
60%
15 of 25
Disposable domains
4
Burner inboxes
Alias & burst flags
9
Self-referral / velocity
Recommended anti-fraud posture
STRICT fraud mode recommended- Remove 4 disposable-domain address(es) before broadcasting to avoid hard bounces.
- Deduplicate 3 canonical/plus-alias collision(s); Waitlyze normalizes Gmail dot/+aliases automatically.
- Enable Waitlyze STRICT fraud posture: detected 6 signups inside tight referral velocity bursts.
Ready to turn this into a live waitlist?
Free to start · No credit card · Draft stays private until you publish
Build and run your waitlist in Waitlyze, free up to 100 signups
Hosted launch page or embed, verified referral links, consent-aware email, and audience analytics. No credit card required.
How list health and fraud risk are calculated
The Waitlist Health & Fraud Risk Auditor inspects your subscriber CSV completely inside your browser so zero raw email addresses ever leave your device, or evaluates manual aggregate metrics. It detects disposable domains, Gmail dot/plus-alias self-referral collisions, role accounts, unverified decay, and signup velocity spikes, then exports a cleaned CSV.
- 1
Canonical Plus/Dot Alias Deduplication
Maps john.doe+1@gmail.com and johndoe@gmail.com to one canonical identity using the same normalization rule Waitlyze enforces at signup.
- 2
Disposable & Burner Domain Detection
Flags known temporary inbox providers (mailinator, guerrillamail, yopmail, 10minutemail, tempmail, etc.) that bounce or farm rewards.
- 3
Role Accounts & Velocity Spikes
Identifies generic addresses (admin@, info@, test@) and flags bursts of rapid signups sharing a referral code inside tight 2-minute windows.
Formula & scoring model
Health Score (0–100) = 100 − (Invalid% × 1.6) − (Disposable% × 1.8) − (Normalized Duplicates% × 1.5) − (Role% × 0.6) − Decay & Velocity Penalties
Reuses Waitlyze's exact canonical email normalization (folding Gmail dots and +aliases) alongside disposable-provider lists, role-address checks, and timestamp velocity windows.
Worked example
Sample CSV audit: 500 imported pre-launch signups
Mixed export from a legacy form without double opt-in: 412 clean, 38 disposable domains, 24 Gmail plus-alias duplicates, 16 role/invalid rows, 10 burst velocity signups.
- Waitlist Health Score
- 74 / 100 (Needs cleanup)
- Safe deliverable rows
- 412 (82.4%)
- Flagged risky rows
- 88 (17.6%)
- Recommended Waitlyze posture
- STRICT fraud mode + Double Opt-In
How to interpret your result
85–100 (Clean list)
Safe to import and warm up. Maintain double opt-in verification before launching any referral reward tiers.
60–84 (Moderate pollution)
Download the cleaned CSV with disposable and duplicate alias rows stripped before sending your launch announcement to protect sender reputation.
Below 60 (High bounce / abuse risk)
Do not blast this list from your primary domain. Clean risky rows first, enable Waitlyze Strict fraud controls, and send a small re-confirmation batch.
Methodology & privacy
Zero-upload guarantee: CSV files are parsed strictly in browser memory via JavaScript. No email addresses or file contents are uploaded to Waitlyze servers or analytics.
- Author
- Waitlyze Product Team
- Reviewed by
- Falak Gala
- Last materially updated
- Version
- v1.0
Sources & changelog
- Waitlyze canonical email normalizer (src/lib/normalize-email.mjs)
- Waitlyze IP & velocity fraud posture rules (src/lib/fraud/gates.mjs)
v1.0: Zero-upload browser CSV auditor with cleaned CSV download and aggregate metrics fallback.
Frequently asked questions
Are the email addresses in my CSV uploaded to Waitlyze?
No. Parsing, deduplication, disposable-domain checks, and cleaned CSV generation run 100% locally in your browser. Zero subscriber rows leave your computer during the audit.
What columns does the CSV auditor recognize?
It automatically detects email columns (email, email_address, subscriber), plus optional timestamp (created_at, date), verified status, and referral_code columns.
Why are Gmail plus-aliases flagged as potential fraud?
Legitimate users occasionally use +tags for inbox filtering, but multiple +alias variations signing up on the same waitlist, especially under the same referral code, is the #1 self-referral farming pattern.
Continue your launch setup
Guide
Common Waitlist Mistakes That Kill Launch Momentum
The mistakes that quietly ruin a waitlist, from silent lists to fake scarcity, and how to avoid each one before launch day.
Guide
How a Referral Waitlist Works (and Stays Fair)
How referral waitlists turn subscribers into sharers, what counts as a real referral, and how to keep fake signups from distorting your campaign.
Recommended template
Free SaaS Beta Waitlist Landing Page Template
A screenshot-led beta page with proof and answers.