Earlier quoted context omitted.
The browsers of their site visitors.
If you need to be on the site it’s not a botnet and there is no C&C server coordinating the attack. It‘s just the JS on the site that makes the attack.
Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2
211–220 of 351 posts
Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2
#212I wish I could find it
Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2
#213Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2
#214Earlier quoted context omitted.
I'm not sure whether you're making a joke or confusing the two websites.
You’re just not at all familiar with the subject. Archive.org is awful . It allows site owners and random third parties to edit old archived pages. Archive.today does not.
Do you actually mean edit or do you just mean delete
Both are problematic, but falsifying a historic record is orders of magnitude worse than deleting one, and conflating them would be extremely dishonest
Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2
#215Sacrificing performance for a faster lookup time makes no sense in 2026. This is the one area where I continue to use Google DNS as it just works. Use anything but Cloudflare in this case, please.
Parent pro-tip: Next time the iPad is having Bluey episode playback issues, check to see if you're actually using Cloudflare DNS.
Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2
#216I 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…
I would say the opposite... The DDoS is pretty obviously ridiculous, completely unacceptable, and entirely indefensible, while the blog post seems like whatever.
I honestly cannot fathom defending using your popular website as a tool to DDoS someone you have personal beef with, without the consent of the DDoSing participants.
Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2
#217Earlier quoted context omitted.
https://arstechnica.com/tech-policy/2026/02/wikipedia-bans-a...
That doesn't say anything about them tapering with archive content
https://megalodon.jp/2026-0219-1634-10/https://archive.ph:44...
This is an archive of an Archive.is archive of a blog post. The first sentence of the post says “ Jani Patokallio was a woman of exceptional intellect…” This was changed, it originally had someone else’s name (see second paragraph). So, who knows what other archived pages were changed?
Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2
#218Cloudflare 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.
As far as I am aware, all previous issues with archive.today and Cloudflare were on account of archive.today taking measures to stop Cloudflare's DNS from correctly resolving their domains, not the other way around. The current situation is due to Cloudflare flagging archive.today's domains for malicious activity, Cloudflare actually still resolves the domains on their normal 1.1.1.1 DNS, but 1.1.1.2 ("No Malware") n…
Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2
#219A bit context if you are confused why Public DNS server blocking websites. 1.1.1.2 is Malware blocking DNS server similar to AdBlock DNS server. It is not 1.1.1.1 and 1.0.0.1 Here is the DDoS context https://gyrovague.com
Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2
#220Earlier quoted context omitted.
One side publishes words, the other DDoSes. One side could just ignore the other and go about their business, the other cannot. One is using force, which naturally leads to resistance and additional attention, the other is not. Both sides look like they have been bullied in the past and not found their way out of reproducing the pattern yet.
[flagged]
Context matters. Which is why also different rules apply, and laws exist to guard these rules. DDoS is not an acceptable response in any jurisdiction, no matter what triggered them. We’re not in the Middle Ages, even if some behave like we are. Violence does not justify violence. Unjust action does not justify unjust responses.