I think there are two angles to look at this. Yes, there’s the attack on the weblog. But there’s also pressure on archive.today, e.g. an FBI investigation [1] and some entity using fictitious CSAM allegations [2]. [1]: https://arstechnica.com/tech-policy/2025/11/fbi-subpoena-tri... [2]: https://adguard-dns.io/en/blog/archive-today-adguard-dns-blo...
Jani Patokallio who runs gyrovague.com published a blog post attempting to dox the owner of archive.today. Jani justifies his doxing as follows "I found it curious that we know so little about this widely-used service, so I dug into it" [1] Archive.today on the other hand is a charitable archival project offered to the public for free. The operator of Archive.today risks significant legal liability, but still offers…
Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2
91–100 of 351 posts
Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2
#92Cloudflare dns has gone back and forth on whether it wants to resolve them since 2019. It’s taken that away and restored it again (intentionally? mistake?) at least four times. The c&c/botnet designation would seem to be new though.
Just tells me they are an unreliable resolver. Instead of being a neutral web infra, they actively participate in political agendas and censor things they "think" is wrong.
Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2
#93I think there are two angles to look at this. Yes, there’s the attack on the weblog. But there’s also pressure on archive.today, e.g. an FBI investigation [1] and some entity using fictitious CSAM allegations [2]. [1]: https://arstechnica.com/tech-policy/2025/11/fbi-subpoena-tri... [2]: https://adguard-dns.io/en/blog/archive-today-adguard-dns-blo...
Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2
#94Earlier quoted context omitted.
Given they are retroactively tampering with past archives it's not exactly trustworhy in the first place
Proof?
Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2
#95Earlier quoted context omitted.
Should providing a public service absolve all sins?
So far, the only sin archive.today has been accused of is retaliating against a guy attempting to dox them. That's a pretty small sin in my book. To be written off as wildly unsuccessful but entirely justified self defense. DDoSing gyrovague.com is silly, not evil. The content on gyrovague.com which targets archive.today is evil, plain and simple.
I think you're missing that circumventing paywalls is unlawful in most parts of the world.
Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2
#96Earlier quoted context omitted.
So far, the only sin archive.today has been accused of is retaliating against a guy attempting to dox them. That's a pretty small sin in my book. To be written off as wildly unsuccessful but entirely justified self defense. DDoSing gyrovague.com is silly, not evil. The content on gyrovague.com which targets archive.today is evil, plain and simple.
> So far, the only sin archive.today has been accused of is retaliating against a guy attempting to dox them. I think you're missing that circumventing paywalls is unlawful in most parts of the world.
Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2
#97Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2
#98Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2
#99Earlier quoted context omitted.
The linked blog contains a story about who funds archive today and they presumably don’t like being exposed.
You mean just to keep their secrets hidden they hurt others?
As an individual, keeping their identity private is the only way to prevent oppression.
Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2
#100Earlier quoted context omitted.
So far, the only sin archive.today has been accused of is retaliating against a guy attempting to dox them. That's a pretty small sin in my book. To be written off as wildly unsuccessful but entirely justified self defense. DDoSing gyrovague.com is silly, not evil. The content on gyrovague.com which targets archive.today is evil, plain and simple.
> So far, the only sin archive.today has been accused of is retaliating against a guy attempting to dox them. I think you're missing that circumventing paywalls is unlawful in most parts of the world.
And a necessity if you want to archive the content correctly, also necessary if you want the archives to be publicly available.