Quick Summary
This guide reviews the top GitHub lists for disposable email domains, explains their strengths and limitations, and shows how Mailsniper provides a faster, more reliable alternative with real-time detection and API-first integration.
Disposable email addresses create real problems for SaaS, e-commerce, and other online businesses. They inflate signup metrics, enable free trial abuse, and waste sales and marketing effort on leads that will never convert. If you want to block fake signups at the source, you need a list of disposable domains that stays fresh.
GitHub is a great starting point for these lists. The catch is that static or semi-automated lists can lag while new domains appear every day. That delay is exactly when abuse slips through.
How to Use This Guide
- Start with one or two repositories that fit your risk tolerance and maintenance preference.
- Combine lists only if you can handle deduplication and false positives.
- Revisit this page periodically or automate pulls directly from the repositories that support it.
Top GitHub lists for Disposable Email Domains
The summaries below combine each project's documentation, current activity, and practical deployment considerations.
1. 7c/fakefilter
Repo: github.com/7c/fakefilter
Update
frequency: Daily, automated
Approx. size: ~5,000 domains
What it
is: Fully automated system that monitors known disposable email providers in real time and
commits updates daily.
2. disposable/disposable
Repo: github.com/disposable/disposable
Update
frequency: Daily, automated
Approx. size: ~100,000 domains
What it
is: Large aggregate that pulls from many external sources and scrapers with a 24-hour
regeneration cycle.
3. disposable-email-domains/disposable-email-domains
Repo: github.com/disposable-email-domains/disposable-email-domains
Update
frequency: Multiple times per week
Approx. size: ~4,000 domains
What it
is: Community-maintained list with rigorous validation. New domains typically require
screenshot evidence before merge.
4. amieiro/disposable-email-domains
Repo: github.com/amieiro/disposable-email-domains
Update
frequency: Every 15 minutes, automated
Approx. size: Variable
What it
is: Frequently regenerated deny and allow lists in TXT and JSON formats.
5. wesbos/burner-email-providers
Repo: github.com/wesbos/burner-email-providers
Update
frequency: Weekly to monthly
Approx. size: ~5,000 domains
What it
is: Long-running community list that many developers already know and use.
6. unkn0w/disposable-email-domain-list
Repo: github.com/unkn0w/disposable-email-domain-list
Update
frequency: Irregular, community-driven
Approx. size: Variable
What it
is: Project aimed at newsletter operators that filter temporary addresses, available in
simple formats.
7. ivolo/disposable-email-domains
Repo: github.com/ivolo/disposable-email-domains
Update
frequency: Not maintained
Approx. size: Legacy list
What it is: A
once-popular dataset that many projects still reference.
Static Lists: The Good and The Bad
Strengths
- • Open and transparent: Source code and data are publicly available for review
- • Easy to adopt: Simple TXT or JSON formats integrate with CI/CD pipelines
- • No cost: Free to use with no API limits or subscription fees
- • Community-driven: Benefit from collective knowledge and contributions
- • Full control: You own the data and can modify it as needed
Limitations
- • Outdated instantly: Lists are stale the moment they're published
- • Manual maintenance: You must regularly pull updates and handle deployments
- • Coverage gaps: Community updates are sporadic, missing new threats
- • False positives: Stale entries can block legitimate domains
- • Infrastructure overhead: Requires storage, cron jobs, and version control
- • Timing vulnerability: New disposable domains slip through between updates
The Reality of the Market
Major disposable email services create more than 10 new domains every single day. Even the best-maintained static lists struggle to keep up with this volume, creating windows of vulnerability where abuse can slip through undetected.
Mailsniper vs. Static Lists: Side-by-Side Comparison
| Feature |
❌
Static GitHub Lists
|
✅
Mailsniper
|
|---|---|---|
| Update Frequency | Daily to weekly (manual) | Real-time, continuous |
| Sources Monitored | Limited, manual additions | 100+ sources daily |
| New Domain Detection | Days to weeks delay | Same day detection |
| Maintenance Required | Manual pulls, cron jobs, storage | Zero maintenance |
| Integration Method | Download + file parsing | Single API call |
| Coverage Gap Risk | High (between updates) | Minimal |
| False Positive Management | Manual list editing | Automated validation |
| Keeps Pace with Market | No (10+ daily domains) | Yes |
| Public Email Detection | Not included | Detects Gmail, Yahoo, Outlook |
| Additional Validation | Domain list only | Active domain validation, MX checks |
| Sender Deliverability Support | No impact | Improves sender reputation |
| Setup Time | Hours (CI/CD integration) | Minutes |
FAQs
Should I Combine Multiple GitHub Lists?
You can, but more entries can increase false positives. Start with one well-maintained list, then add a second only if you see clear gaps.
Do I Still Need a List if I Use Mailsniper?
No. The API checks your signups against a live, continuously updated database. Many teams move away from static lists once the API is in place.
How Often Should I Refresh a Static List?
Daily at minimum if your risk is high. Be prepared for domains that appear between refreshes.
What's the Advantage of the API Approach?
Zero maintenance, real-time updates, comprehensive validation (disposable detection, MX checks, spam flagging), and immediate access to new threats. View our documentation to see how easy integration can be.
How Does Pricing Work?
Mailsniper is currently in beta. All users get 10,000 free API calls to thoroughly test the service. View pricing details or contact us at [email protected] for additional calls during evaluation.
How Does Better Email Validation Improve My Sender Deliverability?
When you send emails to invalid domains, email providers notice. High bounce rates and spam complaints damage your sender reputation, which means your legitimate emails are more likely to land in spam folders. By validating emails before adding them to your database, you maintain a clean contact list, reduce bounce rates, and protect your domain's reputation with major email providers. This means better inbox placement for all your emails.