disposable-email-domains vs disposable-email-validator
Disposable email domain data and validation compared
Both projects help applications apply signup policies to disposable email addresses. disposable-email-domains provides a shared domain list for applications to consume, while disposable-email-validator is a TypeScript library with configurable validation rules, allowlists, and optional plus-addressing checks.

disposable-email-domains: Block Disposable Email Domains
A maintained blocklist of disposable and temporary email domains for teams that want to limit throwaway-account abuse. Use the plain-text list across languages, with validation tooling and a Python package available.

disposable-email-validator: Block Temporary Email Signups
A TypeScript library for rejecting disposable email domains and optionally blocking plus-addressed email addresses. It applies configurable rules by environment, making it useful when signup policies differ between development and production.
| disposable-email-domains | disposable-email-validator | |
|---|---|---|
| Language | Python | TypeScript |
| License | — | MIT |
| Stars | 5.7k | 120 |
| Forks | 904 | 5 |
| Last analyzed | Nov 6, 2026 | Oct 13, 2026 |
Key differences
- disposable-email-domains supplies a plain-text blocklist and examples; disposable-email-validator provides a TypeScript API that returns a success result or error message.
- disposable-email-domains leaves loading, updates, input validation, and matching to integrators; disposable-email-validator applies configured rules in application code.
- disposable-email-domains documents suffix matching that accounts for public suffixes; disposable-email-validator uses a built-in list and supports custom domains and allowlists.
- disposable-email-validator can optionally reject plus-addressed emails and set different rules for named environments; disposable-email-domains focuses on domain data.
- disposable-email-domains is listed with a NOASSERTION license, 5.5k stars, and 888 forks; disposable-email-validator is MIT-licensed, with 120 stars and 5 forks.
Choose disposable-email-domains if you…
- need a shared plain-text domain list to integrate into your own validation workflow.
- want examples for using domain data across multiple programming languages.
- need control over how the list is loaded, updated, and matched in your application.
Choose disposable-email-validator if you…
- want a TypeScript API to apply signup email rules in application code.
- need environment-specific rules, allowlists, or custom disposable domains.
- want the option to reject plus-addressed emails as well as disposable domains.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.