Industry Observations-Technical Insight

Why Should Scare You

A long time ago I began to compile a list of lesser known but still very scary choke points on the Internet. This was a short list of providers (like the DNS that most routers use, for instance) that could have major impact if they were ever compromised or owned by a nefarious 3rd party. One of those was is the single best typo squatter domain on the planet. Let’s say, for instance, you accidentally type in (notice the end there). Yes, it would go to email servers if they were set up to allow email to come in. If you typed a URL as similarly, you would also redirect to the typo domain. Or how about phishing sites of or have you downloaded the latest patch from Given that .com is the largest TLD, is the best typo domain naturally.

A few months ago and without much fan fare, was silently sold by CNET to – one of the most notorious domain squatters ever. Sources close to the deal told me it was sold for around $1.5 million. Yes, the fox owns the hen-house. For $1.5 million it was a steal though – it’s easily worth that just in typo traffic and the huge volume of accidental inbound links.

However, things are not as bad as they could be. For instance, port 80 (web) is open, yes, but port 25 (mail) is not. If and when DSparking decides to open port 25 they will start receiving tons of email that is potentially extremely sensitive. Even if it seems rejected by the mail servers they could still be logging it.

For now mail appears to be closed and has been since the deal went through. They could easily be opening port 25 only to selective IP address ranges, or even opening and closing it periodically to get a snapshot of traffic. There’s no easy way to know for sure. I doubt it’s open at all but should that change, and it could easily, this should be considered an extremely dangerous domain.


as @spazef0rze pointed out although port 25 is closed on the website, mail is still being processed through a seperate DNS entry:

$ host -t MX mail is handled by 10

Also, as @mubix noted, there are many other ports/protocols that can be subject to interception if typo’d in the same way. So yes, it’s probably time to block this. No good can come of it.