When a Site Blocks Disposable Email

Domain burnpublic = listed
A field of domains with the blocklist front moving across it
Every domain shown on a public page reaches the blocklists eventually. The newest ones are simply not there yet.

You paste an address, press submit, and the form answers with something like "please use a valid email address" even though the address is perfectly valid. What it means is that the site recognised the domain and refused it on purpose.

Here is how that check works, why it is not personal, and what to do about it.

How the blocking works

There are public lists of domains known to belong to disposable mail services. They are maintained on code hosting sites, updated constantly, and free to use. Commercial validation companies keep larger private versions and sell access to them.

A signup form calls one of these, or bundles a copy, and compares the part of your address after the at sign against it. If the domain is on the list, the form rejects you. Nothing about your specific address is examined, and nobody looked at you individually.

The lists are built by watching services like this one. Somebody visits, notes which domains are offered, and adds them. Some run automated scrapers that check the popular services every day. This is why any domain shown publicly on a page like this one will end up on a list eventually. It is not a flaw that can be fixed, it is a consequence of being a public service.

Why sites do it

Usually not to spite you. The common reasons are mundane.

Trial abuse. A free trial that costs the company money is worth protecting from somebody claiming it twenty times.

Vote and review manipulation. Anything that counts one per person needs some friction, and email is the cheapest friction available.

Delivery statistics. Marketing teams are judged on bounce rates and open rates. Addresses that vanish after a day damage both numbers, so their tools are configured to refuse them.

Compliance nerves. Some businesses believe, rightly or not, that they must be able to reach a customer later.

What to try, in order

Use a different domain. The list of domains on the home page changes over time, and the newer ones are usually not yet on the blocklists. This solves the problem more often than anything else and takes five seconds.

Consider whether the site is worth it. A shop that will hold your order and your money genuinely does need a way to reach you. A recipe site that wants an address before showing the ingredients does not. Spend real addresses only where they buy you something.

Use a permanent alias instead. If your mail provider supports aliases or plus addressing, an alias is not disposable, passes every blocklist, and can still be switched off later. It is a different tool for a different situation, and it is the right answer for anything you expect to keep.

Register here and use a private domain. Addresses on our private domains are not published anywhere, so they do not appear on scrapers' lists and are not added to blocklists. That is the main reason accounts exist. It is not a permanent guarantee either, but it lasts considerably longer.

What does not work

Adding characters to the domain. The check is on the domain, not the local part, so writing something before the at sign changes nothing.

Looking for an undetectable service. Any service with a public page is scraped. Services that promise otherwise are either new, in which case they will be scraped shortly, or lying.

Complaining to the site. The check is usually a setting inside a third party tool that the person reading your message cannot alter.

How to recognise which check you hit

Sites reject addresses in three different ways, and the wording tells you which one you are facing.

Instant rejection at the form. The page answers before you can blink, usually with "please enter a valid email address" even though the address is valid. This is a blocklist lookup, and a different domain fixes it.

Rejection after submitting. The form accepts you, the page reloads, and then says the address cannot be used. This is a server side check, often against a paid validation service with a larger list. A different domain still helps, but less often.

Silent acceptance and no message. The signup appears to work and nothing arrives. This is the sending platform refusing the recipient, not the site. Covered in detail on the page about codes that never arrive.

Why the same domain works on one site and fails on another

There is no single list. There are dozens, they disagree, and each site uses whichever one its developer picked years ago.

An open list on a code hosting site might have forty thousand domains and be updated weekly by volunteers. A commercial service might have two hundred thousand and update hourly, but cost money that a small site will not spend. Some sites maintain their own list of domains they personally saw abuse from.

This is why trying a different domain works so reliably: you are not defeating a system, you are stepping outside one particular list.

What registering actually changes

The domains shown publicly on any disposable service get scraped, and there is no defence against that: the scraper is just a visitor reading the page.

Domains that are never displayed to anonymous visitors have no such exposure. They end up on lists only when somebody who has an account uses one somewhere that reports it, which happens far more slowly. That is the entire mechanism, and it is why the domains behind registration keep working after the public ones stop.

It is a delay, not immunity. Anyone claiming a permanently undetectable disposable domain is describing something that cannot exist on a public service.

When to give up and use a real address

Some categories of site will never accept a disposable address, and recognising them early saves time:

  • banks, payment services and anything regulated;
  • government and tax portals;
  • employers and job platforms;
  • anything that ships you a physical object;
  • services with a free tier that costs them money per account.

For these, the refusal is not an obstacle to route around. It is the service correctly identifying that it needs to reach you later, and it is right.

The realistic view

Disposable addresses and blocklists are in a permanent, slow race. Domains get registered, get used, get noticed, get blocked, and get replaced. A service that takes this seriously treats domains as consumables and keeps replacing them, and that is exactly what we do.

What that means for you day to day: if one domain is refused, try another. If your address gets refused everywhere on a particular site, that site has decided it wants a permanent relationship, and you get to decide whether it deserves one.

Read next

All guides