Is 24faw.com a Disposable Email Domain? DNS and List Check

Updated 31 October 2026 · Volt Ghost team

24faw.com at a glance

We read the DNS records through Cloudflare's public DNS-over-HTTPS resolver. The list status comes from the copy of the open-source disposable email domains list that ships with our checker, and the date it was added comes from that project's public Git history.

What the records say about 24faw.com

A normal mail provider publishes a website, a DMARC policy and an SPF record listing the servers it really sends from. 24faw.com has none of that. It only has what it needs to receive mail:

• Two equal mail servers. Both MX hosts sit at priority 10, so senders split incoming mail between them. On the day we checked, mail.wabblywabble.com resolved to two IPv4 addresses, one in a Hetzner range in Germany and one in a DigitalOcean range in the Netherlands, and mail.wallywatts.com to two more (Hetzner and DigitalOcean, both in Germany), according to the regional internet registry records for those addresses. Neither host had an IPv6 address.
• An SPF record that allows nobody. The only sender it names is fd36:7c64:44d0::/48. Addresses starting with fd are IPv6 "unique local" addresses, the IPv6 version of a home network range, and can't send mail across the internet. With -all at the end, any message claiming to be from @24faw.com should fail SPF. That fits a domain whose addresses only ever receive codes and links.
• No DMARC and no website. There is nothing to visit and no policy telling other providers what to do with forged mail.

The shared servers behind it

The two MX host names aren't unique to this domain. When we looked up 3dkai.com and the four domains added to the list alongside it (flosek.com, hlkes.com, indevgo.com and niprack.com), all six returned the same pair of servers, the same private-range SPF record and, for 3dkai.com, the same dnsowl.com name servers. That is the usual pattern for temp mail: one set of receiving machines and a rotating pool of cheap domains in front of it, so a block on one domain is easy to step around. It's also why checking the MX records of an unknown domain is a useful second signal next to a list lookup.

If you saw @24faw.com in your sign-ups

Someone used a short-lived inbox, usually to get a verification code without handing over a real address. They may be a spammer, or just someone avoiding marketing mail. Our guide on how sites detect disposable email covers the trade-offs of blocking, and the email address validator checks syntax, typos and temp mail domains in one go. If you're the one who needs a throwaway inbox, our own domains are on the same list on purpose, as explained in is disposable email legal?

Questions