Wingus Dongshire
kiwifarms.net
- Joined
- Dec 22, 2018
Sorry if this is a repeat, I tried searching but "archive.fo" isn't exactly a unique string on the farms and the "search title only" button seems to do nothing.
I was digging through some threads on my weekly "I'm bored as fuck, time to lurk" period and noticed I got 404'd for archive.fo ridiculously quickly. Naturally, I wondered if either my pi-hole was blocking it (like it did the farms) or if my upstream DNS provider is sinkholing it.
So, having a closed AirVPN account and being too strapped to renew just to test this, I decided to poke around resolving it through my standard upstream (CloudFlare)
Finding it strange that I was getting a loopback reserved IP from it, I decided to check the nameservers and lo and behold, CloudFlare is the nameserver.
Likewise, here's Google's results:
However, that IP just returns the out-of-the-box NGINX landing page
Furthermore, the SSL cert bound to that page is for "adieo.com"
Archive.is resolves normally (which is weird, since that's the one they stated would be getting shut down) but doesn't actually respond to my HTTP/S traffic.
Judging from the fact that archive.fo resolves from (seemingly) the proper nameservers but I get this, I'm unsure if it's been hijacked/shutdown or if it's being actively censored.
If the former, why the NS fuckwittery from CloudFlare?
If the latter, the fuck DNS do I use now?
I was digging through some threads on my weekly "I'm bored as fuck, time to lurk" period and noticed I got 404'd for archive.fo ridiculously quickly. Naturally, I wondered if either my pi-hole was blocking it (like it did the farms) or if my upstream DNS provider is sinkholing it.
So, having a closed AirVPN account and being too strapped to renew just to test this, I decided to poke around resolving it through my standard upstream (CloudFlare)
Finding it strange that I was getting a loopback reserved IP from it, I decided to check the nameservers and lo and behold, CloudFlare is the nameserver.
Likewise, here's Google's results:
However, that IP just returns the out-of-the-box NGINX landing page
Furthermore, the SSL cert bound to that page is for "adieo.com"
Archive.is resolves normally (which is weird, since that's the one they stated would be getting shut down) but doesn't actually respond to my HTTP/S traffic.
Judging from the fact that archive.fo resolves from (seemingly) the proper nameservers but I get this, I'm unsure if it's been hijacked/shutdown or if it's being actively censored.
If the former, why the NS fuckwittery from CloudFlare?
If the latter, the fuck DNS do I use now?