Updated · Volt Ghost team
Address records: can mail fall back?
| What the domain publishes besides "no MX" | Domains |
|---|---|
| IPv4 address (A record) | 866 (80%) |
| of which also IPv6 (AAAA) | 189 |
| No address record at all | 219 (20%) |
RFC 5321 section 5.1 defines the "implicit MX" rule: no MX means try the A or AAAA record of the domain itself. The 219 names with neither are undeliverable in practice. For the 866 with an address, delivery depends on whether that machine runs a mail server. We did not probe port 25, so this page does not claim any of them accept mail; it only shows where a sender would try.
Where the address records point
| IPv4 address | Network (RDAP) | Listed domains |
|---|---|---|
43.134.226.173 | ACEVILLE PTE LTD, Singapore (APNIC) | 134 |
44.233.250.75 | Amazon (AWS) | 79 |
54.243.117.197 | Amazon Data Services, Northern Virginia | 35 |
117.122.125.107 | VNNIC, Vietnam (APNIC) | 28 |
104.219.250.37 | Namecheap | 20 |
The 866 names use 406 distinct first addresses, but one Singapore server holds 134 of them. That is the batch of four-letter .hair and .skin names added on 27 September 2026, described on the September 2026 page: 75 of the 79 listed .hair domains and 59 of 66 .skin domains still have no MX.
Who runs their DNS
| Nameserver domain | Listed domains with no MX |
|---|---|
Cloudflare (ns.cloudflare.com) | 208 |
Alibaba Cloud (hichina.com) | 185 |
Spaceship (spaceship.net) | 108 |
share-dns.com | 61 |
GoDaddy (domaincontrol.com) | 54 |
namebrightdns.com | 53 |
| No NS record returned for the name itself | 60 |
Many of these look like registrar defaults: a name was bought, left on the registrar's or Cloudflare's nameservers, and given a web address but no mail route. 104 publish an SPF record, and 73 use exactly v=spf1 -all, a statement that the domain sends no mail. 83 entries sit under a second-level ending, 27 of them under io.vn.
How they were listed
| Date added | Upstream change | No MX now |
|---|---|---|
| 8 October 2018 | use neutral language for naming and describing assets in this repo (7448bb6) | 437 of 2,828 |
| 5 June 2026 | Add missing domains from sources (#1004) (ce7c1aa) | 149 of 808 |
| 27 September 2026 | Add missing domains from sources (#1197) (0655284) | 136 of 200 |
| 16 June 2026 | Add missing domains from sources (#1030) (10df315) | 31 of 269 |
| 30 August 2026 | Add missing domains from sources (#1138) (9ba9a45) | 21 of 326 |
The 2018 seed accounts for 438 of these names: old temp mail domains whose owners kept the registration but switched off mail. The 2026 share (515) comes mostly from the bulk "Add missing domains from sources" changes of June and September; the September names have had no MX since we first checked them on 4 November.
A moving target
From 5 to 8 Nov 2026, 31 listed domains removed their MX record, 5 added one, 28 without MX stopped existing and 1 switched to a null MX. A domain with no MX today can be a working temp inbox next week, which is why the checker keeps flagging the name rather than its current DNS.
Compare with a normal setup
A mail provider publishes MX, SPF and DMARC together; see iCloud's MX records for a clean example, or a listed temp mail domain with a live route such as 365boxmail.com. To see any domain's raw records, use the MX lookup; for names that no longer exist, see the dead (NXDOMAIN) domains page.
Check one domain
Paste a single address or domain. Choose MX records to see whether it publishes any, or ask whether it is disposable.
Questions
Can a domain with no MX record receive email?
Sometimes. RFC 5321 says that when a domain has no MX record, a sender should treat the domain's A or AAAA address as the mail server. Delivery then works only if that machine accepts SMTP on port 25, which most web and parking servers do not.
How many disposable domains have no MX record?
1,085 of the 9,894 in our list copy on 8 November 2026. 866 of them have an IPv4 address record and 219 have no address record at all.
Why do temp mail domains lose their MX record?
Services rotate domains, registrars park lapsed names, and some batches were listed before mail was ever set up. In three days, 31 listed domains dropped their MX record and 28 domains without MX disappeared from DNS entirely.
Should a validator reject a domain without MX?
Treat it as risky rather than invalid. The fallback rule means a few such domains do take mail. For a temp mail list, the domain stays flagged either way.
