Disposable inboxes on a domain that belongs to you — so they pass the blocklist checks that reject shared temp-mail domains. Connect your own domain or use a private TempMaily dedicated domain.
Every free temp-mail service — TempMaily's free tier included — hands out addresses on a small set of domains that the whole internet shares. That's fine for a quick throwaway, but it has a cost: public disposable-domain blocklists crawl and index those domains within days.
Strict signup forms check every address you enter against those lists, so anything on a shared temp-mail domain gets bounced with the familiar "email not accepted" error. A domain that's yours alone isn't on those lists, which is exactly why it gets through. More on why websites block temp mail.
Upgrade to Premium — this unlocks custom domains, dedicated domains, up to 10 addresses, and forwarding.
Connect a domain you own by switching its nameservers once, or pick a TempMaily dedicated domain with no setup at all.
Mint disposable addresses on that domain — as many as you need, up to 10 active at a time.
Mail arrives in the same real-time inbox as the free tool, with forwarding to your real inbox and permanent addresses included.
No MX records to copy, no TXT verification strings. You change your domain's nameservers once and the mail plumbing is configured for you. Here is the whole flow:
Open Dashboard → Domains and enter the domain you own (say, example-mail.com). You immediately get two nameservers back — something like ada.ns.cloudflare.com and carl.ns.cloudflare.com. That pair is the only thing you need from this side.
In your registrar's DNS settings (Namecheap, GoDaddy, Porkbun, Google Domains…), replace the domain's current nameservers with the two you were given. If the registrar has DNSSEC enabled for the domain, turn it off before saving — active DNSSEC blocks the switch.
The domain shows Pending nameservers, then Verifying, then Active. Your dashboard re-checks every 30 seconds automatically. Most domains activate within an hour; a slow registrar can take up to 24–48 hours to propagate.
On activation the MX and SPF records are created automatically and the domain starts routing into TempMaily's ingestion pipeline. There are no records to copy by hand, which also means none to typo. Mail is stored for the addresses you've created — anything else sent to the domain is dropped, so old addresses can't quietly pile up spam.
Create an address on your domain, send it a message from any account, and watch it arrive in real time. From here it behaves like every TempMaily inbox — except the domain is yours, so blocklist checks have nothing to match.
One honest caveat: switching nameservers hands the domain's DNS to TempMaily's infrastructure, and existing records (like a website's A records) don't migrate automatically. Connect a spare domain or one you registered for mail — not the domain serving your production site.
Propagation is registrar-dependent — some push nameserver changes in minutes, others batch them for up to 24–48 hours. Confirm the two nameservers were saved exactly (no trailing dots or typos, old nameservers removed) and that DNSSEC is disabled at the registrar. The status updates on its own once the change propagates.
First check the address: mail is only stored for addresses that exist in your account, and a typo'd or deleted address is dropped silently. If the address is right, give it a few minutes and check the sending side for a bounce — some corporate outbounds refuse newly-activated domains for a day; re-send from a personal account to compare.
Then that site isn't doing a blocklist check — it's requiring phone verification, or only accepting established consumer or corporate providers. A custom domain clears the disposable-domain blocklists, and that's the honest limit: no temp-mail setup of any kind gets past a phone gate.
The domain is registered to another TempMaily account or already exists as a zone on another Cloudflare account. Remove it there first (or pick a different domain), then add it again.
Codes still not landing anywhere? The broader checklist in verification email not arriving covers the sender-side causes.
Straight answer: a custom domain clears blocklist checks, but it won't get you into services that verify by phone or only accept corporate mail. No disposable domain of any kind will.
Privacy users who keep hitting "email not accepted." If shared temp-mail domains bounce on the signups you actually care about, an address on your own domain gets through where a throwaway can't.
QA and automation teams who need a stable, predictable domain for test accounts. Point the API at your own domain and automate email verification testing without your test domain landing on a blocklist mid-suite.
Anyone running lots of signups who wants addresses that survive past 24 hours and forward to a real inbox instead of vanishing on a timer.
Custom domains and private dedicated domains, up to 10 addresses at once, forwarding to your real inbox, permanent addresses, 2GB storage, and no ads — $9.90/mo or $90/year (save 24%).
See the full free-vs-Premium breakdown on the pricing page.
Yes, on TempMaily Premium. Point a domain you own at TempMaily and generate disposable addresses on it — up to 10 active at once. Because the domain is yours and isn't handed out to the whole internet, it doesn't show up on the public disposable-domain blocklists that get shared temp-mail addresses rejected.
Free temp-mail services give everyone addresses on a small pool of shared domains. Public blocklists crawl and index those domains within days, and strict signup forms check incoming addresses against those lists and bounce anything that matches. Your own domain isn't on those lists, so it isn't flagged as disposable.
A dedicated domain is one TempMaily provides that stays private to your account rather than being shared with every free user — no DNS work, and it isn't publicly listed as disposable. A custom domain is a domain you already own and connect yourself, so addresses carry your own brand and you have maximum control. Both are included with Premium.
Not for a dedicated domain — you pick one inside your account and start using it immediately, no configuration. For your own custom domain the only step is changing your domain's nameservers at the registrar to the two you're given; the mail records (MX and SPF) are then configured automatically, so there is nothing to copy by hand. If you'd rather not touch your registrar at all, use a dedicated domain instead.
The nameserver change is a two-minute edit at your registrar. Propagation is what you wait on: the domain usually flips to Active within an hour, though some registrars take up to 24–48 hours. Your dashboard re-checks the status automatically every 30 seconds — you don't need to do anything after saving the nameservers.
We recommend a spare domain instead. Connecting a domain moves its DNS management to TempMaily's infrastructure, and existing records like your website's A records don't carry over automatically. A domain you registered for mail — or an unused one you already own — connects cleanly with nothing to migrate.
Yes. Premium addresses aren't wiped on the free 24-hour timer — you can keep an address long-term or permanently, run up to 10 at once, and forward incoming mail to your real inbox. That's what makes a custom or dedicated domain worth setting up: the addresses on it survive well past a throwaway window.
No, and we won't pretend otherwise. A custom domain gets you past blocklist checks that reject known disposable domains, which is the most common block. It won't get you into services that require phone verification, or ones that only accept corporate or established consumer email providers. For those, no temp-mail domain of any kind will work.
Just need a quick throwaway? The free inbox is here.