just realized that https://archive.today is blocked at the @zlb_berlin. anyone know what thats about?
(yes I know about the recent drama with .today)
13
Replies
2
Boosts
@liaizon @zlb_berlin very interesting.
I wonder if it relates to AT being able to circumvent paywalls?
I know CloudFlare and Palo Alto flagged archive.today as malicious after the DDoS, so maybe their network security is blocking it.
@iampytest1 I wish there was an easy way to see all the domains that are blocked on the local connection. though I guess there are many places they could do the blocking so its sorta difficult to ascertain
@iampytest1 yep all down. I get `cannot resolve https://archive.ph/: Unknown host` with `ping`
@liaizon @iampytest1 ping but doing a lookup through the same name server? Often blocks are done at the dns level and alternate lookup strategies will circumvent it. On my openbsd machines I use unwind but outside of that I have been considering setting up my own DNS resolver using the same tools for machines less lucky to have great tools out of the box.
@cararemixed @iampytest1 I was just confirming those domains didn't load on the library wifi. not that they were down themselves
@liaizon @iampytest1 I'm not implying they were down. I'm asking if it was an IP range block or a DNS lookup block.
@cararemixed I guess I don't understand how to figure that out, all I ran was `ping archive.ph` ect
@liaizon The issue with ping isn't icmp vs tcp/http/tls. It's the mechanism that doesn't change. You have to resolve archive.ph first. This makes it a convenient step for censorship even if it's trivial to circumvent by itself. Most people don't look further.
@cararemixed I didn't understand what you were asking but now I think I do. You were just asking if I tried going to any of them directly by IP. I didn't try that, but will try next time I am at the library
@cararemixed back at the ZLB library:
archive.today (107.189.8.227) gives me `Direct IP access not allowed` when I try to visit from the IP.
annas-archive.pk (186.2.163.174) gives me a different error:
`503 Service Unavailable Server could not complete your request. Might be a good idea to check back later`
but now trying those both from Tor I get the same thing there so it seems they are blocking visiting directly via IP themselves. And they both load fine from Tor via URL
and @internetarchive's wayback machine is down at the same time! what is going on!
