Email domain debugger
You typed a temp mail address into a sign-up form, pressed “send code”, and the inbox stayed empty. Before trying another site, find out where the message got stuck. Type the address you used (or only the part after the @) and press Look up.
Three places a code gets lost
The address. A stray space, a doubled dot or a name longer than 64 characters, and many forms refuse the address. The first line of the result says so straight away.
The domain. If no DNS server answers for it, the name has most likely lapsed at the registrar. Nothing can deliver to it until someone renews it.
The mail route. The domain exists, but its MX records send mail to someone else’s server, or nowhere. That is the only case you can fix yourself, and only if the domain is yours.
Short answers
| Result line | In plain words | Your move |
|---|---|---|
| All good: mail … comes to this site | Delivery works on our end. | Ask the website to send the code again. |
| This site is only the fallback | Another host takes the mail first. | Put our host on top. |
| Same top preference | Mail is split between hosts at random. | Keep a single host on top. |
| Has its own mail service | Mail goes to another provider. | Use one of our domains, or repoint yours. |
| No MX record at all | No route for mail exists. | Add an MX record or pick another domain. |
| Nobody answers for this domain | The name is not live. | Usually an expired registration. |
The one thing DNS cannot show
A website may keep its own list of domains it refuses. That list lives on their side and never appears in DNS. When this page reports everything in order and the form still says “email not accepted”, the block is theirs — switching to another of our domains is the quickest way around it.
Related pages
- Connect your own domain — which MX value to publish, then come back here to confirm.
- Why temp mail cannot send — receiving and sending are separate things.
- Domains that work right now — if you would rather not troubleshoot at all.