A pull request that adds one domain to a disposable email domains list looks trivial until you have reviewed a few dozen of them. The maintainer sees the same three failure modes over and over: a duplicate that slipped in under a different case or subdomain, a domain that has never issued a throwaway inbox, and a diff that ignores the repo’s contribution rules. Run through the checks below before you hit “Compare & pull request” and your patch has a real chance of being merged the same day.

Confirm the domain is new, in every form it could already exist

Duplicate checks fail most often because contributors search for exactly the string they typed. If you found mailinator.example in a spam trap and the list already contains example, a naive search returns nothing and you open a PR that adds a subdomain of an entry that is already blocked. Search for the registrable domain first, then the full hostname. Many lists store parent domains only, on the theory that blocking example covers every subdomain a provider spins up later.

Case is the second trap. Domain names are case-insensitive, but text files and grep are not. A list that contains TempMail.Example will not match a search for tempmail.example, and the maintainer will close your PR with a link to the existing line. Lowercase your candidate before you search, and search case-insensitively: grep -i on a clone of the repo takes a second and saves a review cycle. The same applies to trailing dots and to punycode. If the domain has non-ASCII characters, check both the Unicode form and the xn-- form, because some lists normalize one way and some the other.

Then check across projects, not just the one you are patching. A domain that is missing from disposable-email-domains may already sit in FakeFilter, which publishes an automated list of temp-mail providers daily, or in MailChecker, which supports over 55,000 throwable email domains across its Python, PHP, and JavaScript packages. If a sibling project already carries the domain, say so in the PR description. Maintainers of overlapping lists often want to know whether a gap is real or just a sync lag, and amieiro/disposable-email-domains regenerates its aggregated deny and allow lists every 15 minutes, so a domain can appear there before it reaches the upstream source you are editing.

Verify the domain actually hands out disposable inboxes

A domain blocklist is only as good as its precision. Every false positive is a real person who cannot sign up, and every one of those turns into a support ticket or a blocklist removal request. Before you add a domain, load the site and confirm it offers temporary, throwaway, or burner inboxes to anyone who visits. A landing page that promises “10 minute mail” is evidence. A parked page, a domain-for-sale notice, or a generic webmail login is not.

Watch for the near-misses that generate rejected PRs. Disposable email domains list entries sometimes arrive because a domain appeared in a sign-up form’s spam folder, which proves nothing about the domain itself. Others are custom domains of a known provider, catch-all domains that forward to a real mailbox, or the marketing domain of a company that also runs a legitimate mail service. If the provider uses a shared MX or a recognizable infrastructure pattern, note it in the PR. Reviewers on repos like burner-email-providers, which is a plain list of temporary providers, tend to accept a domain faster when the evidence is right there in the description, and that same clarity helps explain why sites reject disposable email in the first place.

It also helps to record what you tested and when. Providers appear and disappear, and a domain that issued inboxes last year may now redirect to a squatter. A line like “tested 2025-03-14, inbox created and received mail” gives the maintainer something to trust. If you are adding several domains from one provider, group them in a single PR with one test note rather than opening five separate requests.

Read the contribution guidelines before you write the diff

This is where most otherwise-correct PRs die. Repos differ on almost everything: sort order, whether entries go in a text file or a JSON manifest, whether the domain needs a comment with a source URL, and whether the project requires a changelog entry. disposable-email-domains is a community blocklist plus an allowlist licensed under CC0, and like most community lists it has rules about where new entries go and how they are ordered. Skip them and a maintainer closes the PR with a template response, no matter how valid the domain is.

Check for test requirements too. Some projects run a CI job that validates formatting, checks for duplicates, or regenerates derived files, and a PR that fails those checks sits unmerged until you fix it. If the repo asks you to run a build script or update a generated list, do it in the same commit. If it asks for a changelog line, add one. If it asks you to sign off or use a commit message convention, follow it. ivolo/disposable-email-domains is no longer maintained, which is a useful reminder to check the last commit date before you invest effort: a repo that has not seen activity in two years will not review your patch.

One more habit worth building: validate your candidate with an independent tool before you submit. DeBounce provides a free disposable-check endpoint without an API key, and commercial services like Kickbox expose similar checks through their email validation API. If two independent checkers already flag the domain, your PR is stronger. If they disagree, dig into why before you claim the domain belongs on the list.

Clone the repo, lowercase the domain, search for the parent and every subdomain form, load the site and confirm it issues throwaway inboxes, then read CONTRIBUTING.md line by line and match the format exactly. Write a PR description that states the test date, the evidence, and any sibling projects that already list the domain. That is a five-minute routine, and it is the difference between a merge and a closed tab. For background on how these lists are built and consumed, AllMail publishes a guide on disposable email domain lists that pairs well with this checklist.