Identifying domains that don’t accept or send email

A couple folks have asked me recently about MX records that they don’t understand. These records consist of a single . or they contain localhost or they are 127.0.0.1.

In all cases, the domain owners use these records to signal that the domains don’t accept email. What do these records look like?

screenshot of a terminal session that says: laura@pazu:~$ host yahooo.com yahooo.com has address 98.136.103.23 yahooo.com has address 212.82.100.150 yahooo.com has address 74.6.136.150 yahooo.com mail is handled by 0 .

Why do domains do this? In all cases it’s because the domain owners want to signal they don’t accept email. But there are a number of different reasons to do this.

In the yahooo.com example, this is a domain actually owned by Yahoo. The website redirects to the primary yahoo.com site. But, it’s not a domain that accepts mail. They notify us of this by using a dot mx.

Screenshot of a terminal session that says: laura@pazu:~$ host collectors.org collectors.org has address 91.195.240.126 collectors.org mail is handled by 0 localhost.

In the collectors.org example, they list the MX as localhost. This is a convention I’ve seen from a lot of for-sale domains. (As an aside, some of the for sale domains do accept email. The ones I’ve identified use a handful of common MXs that I suspect belong to the companies that sell access to spamtraps.)

I’ve also seen some domains use 127.0.0.1 as a MX record. Again, this is signalling that they really, really don’t want to accept email.

There’s also a way to signal a domain doesn’t send mail. This is accomplished by using a SPF -all record.

Screenshot of a terminal session that says: laura@pazu:~$ host -t txt collectors.org collectors.org descriptive text "v=spf1 -all"

There you go. Multiple ways to signal a domain doesn’t accept email and one way to signal the domain never sends email.

Related Posts

Organizational security and doxxing

The security risks of organizational doxxing. 
These are risks every email marketer needs to understand. As collectors of data they are a major target for hackers and other bad people. Even worse, many marketers don’t collect valid data and risk implicating the wrong people if their data is ever stolen. I have repeatedly talked about incidents where people get mail not intended for them. I’ve talked about this before, in a number of posts talking about misdirected email. Consumerist, as well, has documented many incidents of companies mailing the wrong person with PII. Many of these stories end with the company not allowing the recipient to remove the address on the account because the user can’t prove they own the account.
I generally focus on the benefits to the company to verify addresses. There are definite deliverability advantages to making sure email address belongs to the account owner. But there’s also the PR benefits of not revealing PII attached to the wrong email address. With Ashley Madison nearly every article mentioned that the email address was never confirmed. But how many other companies don’t verify email addresses and risk losing personally damaging data belonging to non customers.
Data verification is so important. So very, very important. We’ve gone beyond the point where any big sender should just believe that the addresses users give them are accurate. They need to do it for their own business reasons and they need to do it to prevent incorrect PII from being leaked and shared.

Read More

Purging to prevent spamtraps

Someone recently asked when they should purge addresses to remove spamtraps. To my mind this is actually the wrong question. Purging addresses that don’t engage is rarely about spamtraps, it’s about your overall communication processes.

Read More

Metric Monetization

As a digital channel, email provides a lot of different metrics for marketers to use. Not only can marketers measure things like open and click rates, but they can tie these numbers back to a particular recipient. This treasure trove of information leads to obsessing over making the numbers look good. For good deliverability senders want low bounce rates, low spamtrap rates, and high engagement rates.
These metrics are important because they’re some of the things that filters look at when making delivery decisions. We care about this data because the receiver ISPs care about the data. The ISPs care about this data because they are characteristics of wanted and/or opt in email.

Over the past few years a number of companies sell services selling good metrics.

Read More