disposable-email-domains/disposable-email-domains

a list of disposable email domains

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 37 minutes ago
Added to GitGenius on September 12th, 2026
Created on September 2nd, 2014
Open Issues & Pull Requests: 40 (-1)
GitHub issues: Enabled
Number of forks: 887
Total Stargazers: 5,488 (+0)
Total Subscribers: 91 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Disposable-email-domains is a blocklist of temporary and throwaway email domains used to prevent spam and abuse during account registration.

The project maintains a curated list of disposable email domain names that services can use to reject registration attempts from known temporary email providers. The list is stored in a configuration file format containing second-level domains, with validation against public suffix rules to handle edge cases where domains use public suffixes. The approach is straightforward: services integrate the list into their registration flows to deny accounts created with these domains. The project includes tooling to automatically normalize entries by converting to lowercase, removing duplicates, and sorting, while validating against public suffix rules.

Services that receive frequent spam registrations or need to enforce account quality policies should consider this list. It suits any application with user registration, from small projects to large platforms like PyPI, which uses it as part of their account security strategy. The list is available as a Python package for easy integration, with example implementations provided for multiple languages including PHP, Go, Ruby, Node.js, C#, bash, Java, Kotlin, Swift, and Elixir. The project accepts community contributions through pull requests, requiring submitters to provide evidence that a domain actively generates disposable email addresses.

The project operates with a small core maintenance team and accepts community contributions through a structured pull request process. Development activity centers on validating and adding new disposable domains to the blocklist, with contributors expected to demonstrate that domains they propose are actively used for generating temporary addresses. The tooling has evolved to include automated validation against public suffix lists, replacing earlier manual maintenance scripts.