Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

radar.cloudflare.com

Post reply on HN
Print view View original

51–60 of 351 posts

Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

#51

Post by longislandguido »

JasonADrury wrote: post #27
winkelmann wrote: post #20

Earlier quoted context omitted.

I'm not a web developer, but I've picked up some bits of knowledge here and there, mostly from troubleshooting issues I encounter while using websites. I know there are a number of headers used to control cross-site access to websites, and the linked blog post shows archive.today's denial-of-service script sending random queries to the site's search function. Shouldn't there be a way to prevent those from running whe…

[flagged]

You think DDoS (which is illegal btw) is okay as long as you don't like the target?

Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

#52

Post by charcircuit »

gbear605 wrote: post #18
charcircuit wrote: post #17

Earlier quoted context omitted.

>Why? Because once the problematic content is removed it should no longer be blocked. >It's accurate It is neither a C&C server for a botnet, nor any other server related to a botnet. I would not call it accurate. >Nobody should ever use that site It has a good reputation for archiving sites, has stead the test of time, and doesn't censor pages like archive.org does allowing you to actually see the history of news ar…

It is in fact a botnet - they’ve been hijacking user browsers to act as a botnet to DDoS.

Are Hacker News users part of a botnet since they link to sites that when people click they go down due to all of the traffic? Am I part of a botnet if I have HN open as it means HN can execute javascript? I think it's stretching the definition.

Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

#53

Post by riedel »

JasonADrury wrote: post #27
winkelmann wrote: post #20

Earlier quoted context omitted.

I'm not a web developer, but I've picked up some bits of knowledge here and there, mostly from troubleshooting issues I encounter while using websites. I know there are a number of headers used to control cross-site access to websites, and the linked blog post shows archive.today's denial-of-service script sending random queries to the site's search function. Shouldn't there be a way to prevent those from running whe…

[flagged]

While I would it also better to a bit redact names and details mentioned in the original article in hindsight, I hardly find real defamation. I guess you want to provide random unproven evidence if someone is target of various foreign law enforcement and commercial sites. In the article they even call for donations to archive.today . As far as I read the tone of the post is full of admiration. Funny thing is that IMHO the rather childish JavaScript attack gives credibility to the post after all. In all this I somehow hope that we see a legal solution to all this major global copyright crisis that has been reinforced by LLM training. (If you want conspiracy theory: that I guess would be easy monetization for archive these days selling their snapshots)

Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

#54

Post by kay_o »

longislandguido wrote: post #41
_moof wrote: post #8

Good. You don't get to use my computer for a DDoS. I don't care why the DDoS was happening. I wasn't asked, and that's a serious breach of trust.

Breach of trust by a site whose unstated primary purpose is bypassing paywalls and ripping off content? 20 years ago during the P2P heyday this was assumed to come with the territory. Play with fire and you could get burned. If you walk into a seedy brothel in the developing world, your first thought should be "I might get drugged and robbed here" and not what you're going to type in the Yelp review later about their…

Given they are retroactively tampering with past archives it's not exactly trustworhy in the first place

Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

#55

Post by leonidasv »

dydgbxx wrote: post #9
charcircuit wrote: post #6

When the heat dies down, hopefully this flag gets removed.

Why? It’s accurate and if the owner has chosen to do this for months now, why should we ever trust they won’t again? Nobody should ever use that site and every optional filter should block them.

Also, they were caught tampering saved webpages as well, so the website cannot be trusted to fulfill it's main purpose anymore: https://arstechnica.com/tech-policy/2026/02/wikipedia-bans-a...

Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

#56

Post by jrflowers »

JasonADrury wrote: post #37
throwingcookies wrote: post #32

Earlier quoted context omitted.

> The blog is still online and only exists as a part of a harassment campaign targeting archive.today The blog has a lot of more posts on random topics. Why do you imply that the owner of the bloh is part of a harassment campaign and "only" that is the reason for this years old blog to exist?

Because all the content in the past 4+ years is about archive.today?

This is a weird way of saying that you wish gyrovague updated more frequently. You could just say “Big fan of his writing, I’d love it if he posted more” if your only complaint is that there aren’t enough recent blog posts on that website

Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

#59

Post by rollulus »

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...

Re: Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

#60

Post by bawolff »

winkelmann wrote: post #20
stuffoverflow wrote: post #10

Archive.today's attack on https://gyrovague.com is still on-going btw. It started just over two months ago. Some IPs get through normally but for example finnish residential IPs get stuck on endless captchas. The JS snippet that starts spamming gyrovague appears after solving the first captcha.

I'm not a web developer, but I've picked up some bits of knowledge here and there, mostly from troubleshooting issues I encounter while using websites. I know there are a number of headers used to control cross-site access to websites, and the linked blog post shows archive.today's denial-of-service script sending random queries to the site's search function. Shouldn't there be a way to prevent those from running whe…

> I know there are a number of headers used to control cross-site access to websites

Mostly these headers are designed around preventing reading content. Sending content generally does not require anything.

(As a kind of random tidbit, this is why csrf tokens are a thing, you can't prevent sending so websites test to see if you were able to read the token in a previous request)

This is partially historical. The rough rule is if it was possible to make the request without javascript then it doesn't need any special headers (preflight)

Post reply on HN