Stacheldraht attack diagram, courtesy of Wikipedia More than likely, the problem is what you think it was-you’ve been DDoSed. Thinking back a bit, you recall your young CEO going off the rails and making some very divisive remarks in a series of interviews that triggered a nasty war of words on Twitter. You close the connection and reboot, making adjustments to your DNS on CloudFlare, and, eventually, your site comes up again. Same error.įortunately, you’d already configured your Time to Live (TTL)-to 1 hour (rather than the default 72) and you’re able to configure your Response Rate Limiter (RRL) to limit the number of outgoing requests your server will send. You also try accessing your site anonymously with Tor or Psiphon, to rule out this possibility. When that isn’t the case, you try visiting other sites with content like yours to make sure that you’re not being censored or blocked. Failing to see any problems there, you then check your host’s website, and subsequently run a traceroute to your hosting company to ensure the problem isn’t with them.
DDOS ATTACK TOOL OFFLINE
Next, you check for any messages from your web hosting provider, to ensure that you weren’t taken offline for billing, legal, or other reasons. Is the WebHost up? You check with to verify that it’s not a network problem, or that the account hasn’t been disabled. Worried, you walk through the usual administrative checks, to make sure it’s not what you think it is. The irritated messages start flooding in to support. Imagine the following scenario: you’re running a small corporate website, and suddenly, your service becomes unreachable, throwing a 503 (service unavailable) Http error at your customers and website visitors.