Echo Dot (3rd Gen) - Smart speaker with Alexa - Charcoal

Use your voice to play a song, artist, or genre through Amazon Music, Apple Music, Spotify, Pandora, and others. With compatible Echo devices in different rooms, you can fill your whole home with music.

Buy Now

Wireless Rechargeable Battery Powered WiFi Camera.

Wireless Rechargeable Battery Powered WiFi Camera is home security camera system lets you listen in and talk back through the built in speaker and microphone that work directly through your iPhone or Android Mic.

Buy Now

8chan is all the way down—“It’s DNS. It’s always DNS.”


Doctored photograph of a crowd of people wearing white masks.

“Look, just host our website. It’ll be fine, we promise.”

Earlier today in the Ars Technica staff Slack channel, a call went out—”is 8chan down for other people? I can’t get it to load anymore.” This brings up the interesting question of how to check where and why a site might be down, as well as whether it can even load for anyone.

But first a little background.

When Cloudflare finally had enough of 8chan and fired it, the site—notoriously a haven for mass shooters and their fans—immediately jumped ship for BitMitigate, the same CDN that hosts far-right white nationalist site The Daily Stormer. The site also changed DNS and Web hosting to Epik, which is the parent company to BitMitigate and the host of far-right social media platform Gab.

Alex Stamos, cybersecurity expert at Stanford University and former CSO of Facebook, observed that BitMitigate seemed itself to be almost entirely made of equipment and network infrastructure leased from a company called Voxility. This public and pointed observation prompted Voxility to fire BitMitigate and Epik, leaving both 8chan and The Daily Stormer dead in the water.

This brings us back to the lede: when a site is dead, how can you figure out why it’s dead and whether it’s likely to be dead for everybody or just for yourself? If you have access to a Linux, FreeBSD, or Mac computer—or to the Windows Subsystem for Linux—answering these questions is not too difficult. The first thing to realize is that you need DNS in order to have a website.

The most important troubleshooting tool for DNS is a command-line utility called dig. Dig allows you to query DNS records directly; it’s sort of like nslookup on steroids. By default, just like nslookupdig will query whatever your locally configured DNS server is. But you can ask it to query any arbitrary server directly, and you can ask it for exactly the records you want.

If you follow through the gallery above, what we’re doing should be reasonably clear. First, we query our standard DNS infrastructure, asking it where to find a nameserver for—and we come up empty: our own local DNS server hasn’t the foggiest clue.

The next step starts to get a bit more wizardly—we know that is a subdomain of the top-level domain net. So, we ask for the nameserver for net itself—and armed with an answer, we can directly query a root nameserver for information about‘s DNS infrastructure. tells us that the DNS for is handled by and It offers us glue records so that we can reach them.

Once we start asking questions from and, we quickly discover that they aren’t answering any questions at all. So, that’s that— cannot possibly be up, because the domain itself isn’t answering any DNS queries. Even if the Web servers and database servers are functional, there’s no way to find them.

We can still learn more, though. We know that Epik, the hosting service that owns BitMitigate and is supposed to be providing hosting for 8chan and The Daily Stormer, is still online despite having its own netblock cancelled by Voxility. Why would that be?

The dig command served us well in terms of finding DNS information by walking up and down the DNS hierarchy. But in order to figure out why Epik’s own DNS is working despite its network infrastructure being down, we turn to the whois command. (I’ve piped the results through grep in order to show only the information I’m looking for; otherwise, the wealth of data returned wouldn’t fit on one screen.) The whole process looks like this:

  1. dig +short NS to get the hostnames of its nameservers
  2. dig +short A each of the hostnames from step one, to get raw IP addresses
  3. Pipe that whole mess through sort -nu so that we only get one return for each individual IP address serving DNS for
  4. Finally, we can start using whois on those IP addresses to see whose netblocks they’re hosted in.

In the screenshot gallery, you can see I’ve piped the whois results through grep for OrgName. This isn’t strictly necessary, but whois by itself returns pages of information; grep allows us to only look at the lines containing keyword OrgName—which is the organization responsible for managing the subnet of IP addresses they’re each in. This nets us one IP address at Linode, another at Amazon Web Services, and the third at OVH, a large European cloud provider. (We can also find that Epik’s website itself is running on a Web server hosted at NatCoWeb, a New Jersey-based hosting provider.)

We can also take a look at the whois information for the netblock containing’s DNS servers and The Daily Stormer’s Web server. Epik’s now-disconnected netblock is in Switzerland, so we need to query RIPE‘s infrastructure rather than ARIN‘s, and the format is a little different—but we can see that it’s registered to Robert Monster, the CEO of Epik and BitMitigate. (There is a contact address and phone number for Monster listed in Sammamish, Washington. We tried calling but received no answer; the number went to a generic voicemail with no configured greeting.)

What this all boils down to is that Epik itself only seems “up” because Epik—unlike 8chan and The Daily Stormer—isn’t hosted on Epik at all.

Read More


Please enter your comment!
Please enter your name here