all 20 comments

sorted by: hot top controversial new old
[–] 121 points 10 months ago

DNS: Do Not Serve

  • source
  • [–] 53 points 10 months ago (9 children)

    lol whats this basaka.top website can't resolve

  • source
  • hideshow 9 child comments
  • [–] 35 points 10 months ago (2 children)

    Apparently malware, according to uBlock

  • source
  • parent
  • hideshow 2 child comments
  • [–] 17 points 10 months ago* (1 child)

    Well, it's certainly an interesting method of self-promotion to those that bother caring enough to read that part. If it is a malware host, then those reading that far are also probably more conscious of the possibility of it being such so I'm not sure how effective it'd actually be.

    Of course you being the one pointing it out could be considered sus...

    🤪

  • source
  • parent
  • hideshow 1 child comment
  • [–] 22 points 10 months ago (8 children)

    This makes me curious, was there actually a cloudflare error page with the error on the cloudflare cloud? I'm used to seeing the one where the error is on the host. But, for an error where the error shows as being on cloudflare, cloudflare's systems would have to be working enough to serve the error page where they show that their cloud is the issue, but broken enough to not be able to serve the cached content.

  • source
  • hideshow 8 child comments
  • [–] 17 points 10 months ago (4 children)

    Mine said the issue was Cloudflare this morning, similar to the picture.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 18 points 10 months ago (3 children)

    Interesting, good job cloudflare for at least being able to serve the correct error message.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 12 points 10 months ago (2 children)

    The part that I got a kick out of was that their status page was also throwing out the error. I guess it was still indicating the status in a way…

  • source
  • parent
  • hideshow 2 child comments