DNS: Do Not Serve
this post was submitted on 18 Nov 2025
751 points (98.3% liked)
Programmer Humor
27379 readers
1796 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
lol whats this basaka.top website can't resolve
Its probably porn
It is now
As soon as the dns changes have propagated anyway
Apparently malware, according to uBlock
Wayback machine has captures from 2021 and it just looks like an abandoned WordPress site... So yeah, probably malware.
Wtf are you doing OP?
Doesn't even register in WHOIS searches anymore for me. Apparently Namecheap will sell it to you for $2.98.
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...
🤪
Lol I figured it was porn that would make even Cloudflare blush
there are .top websites and they aren't for dating?
If I remember correctly, .top is just one of those dirt cheap TLDs that you can use for whatever.
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.
Mine said the issue was Cloudflare this morning, similar to the picture.
Interesting, good job cloudflare for at least being able to serve the correct error message.
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…