Nice — I pulled the Gyrovague post and made a ready-to-publish Blogger entry for you: three headline options, a full post (Blogger-ready HTML), a short excerpt for social sharing, meta description, labels/tags, and a suggested permalink. I included source attribution to the original article.

Source

The original report is on Gyrovague (Jani Patokallio, Feb 1, 2026). Gyrovague

Title options

1. When an Archive Became an Attack: archive.today’s DDOS Against a Blogger

2. Users as Proxies: How archive.today’s CAPTCHA Pumped Requests at a Personal Blog

3. Why a Web Archive’s CAPTCHA Is Causing Traffic and Trouble for Gyrovague

Ready-to-publish post (recommended)

Suggested slug / permalink: archive-today-ddos-against-gyrovague
Suggested labels / tags: archive.today, DDOS, web-archives, infosec, online-privacy

Meta description (for search/social):
Short: A first-person summary of how archive.today's CAPTCHA page began issuing repeated requests to a personal blog, timeline and implications.

Plaintext post (paraphrased, original wording)

Lede:
In January 2026 I discovered that archive.today’s CAPTCHA page was causing visitors’ browsers to repeatedly request my blog, effectively using those visitors as proxies to generate heavy traffic. The behavior appears to have started around January 11, 2026 and runs a JavaScript loop that repeatedly issues network requests against my site while the CAPTCHA page remains open. Gyrovague

What happened (summary):
I originally wrote about archive.today in 2023; that older investigation resurfaced in late 2025 after other reporting and commentary. In early January 2026, readers began noticing that visiting archive.today triggered a client-side script that made frequent, randomized search requests to my site — every few hundred milliseconds — which effectively hammered my blog’s search endpoint while the CAPTCHA page stayed open. Gyrovague

Timeline & response:
After the script’s activity was reported publicly, words spread via discussion forums and security lists. The blog host was contacted via a GDPR complaint and the author exchanged emails with archive.today’s webmaster; those exchanges and later community posts are part of the record. The site owner also added gyrovague.com to DNS blocklists used by ad-blockers, which prevented the requests for readers running those blockers. Gyrovague

Why it matters:
Whether intentional or not, a design that causes a third-party archive to trigger repeated requests to other websites raises questions about abuse, responsibility, and the line between defensive site behavior and harmful traffic generation. It also highlights how archival tools and anti-bot/UIs can have unexpected effects on other web properties. Gyrovague

Conclusion:
The situation remains messy: there are conflicting claims and a lot of speculation, but the observable fact is that the archive.today CAPTCHA page was issuing repeated requests to a third-party blog. I’ll watch how the community, the archive, and hosting platforms respond. For the full technical details and the author’s timeline, see the original post linked below. Gyrovague

Attribution / link back:
This post summarizes a first-person report by Jani Patokallio on Gyrovague (Feb 1, 2026). Read the original for full details and screenshots. Gyrovague

Blogger-ready HTML (copy & paste into the Blogger post editor — switch to HTML mode if you want to paste the HTML)

html
Copy code
<h2>When an Archive Became an Attack: archive.today’s DDOS Against a Blogger</h2>
<p><strong>Lede:</strong> In January 2026 I discovered that archive.today’s CAPTCHA page was causing visitors’ browsers to repeatedly request my blog, effectively using those visitors as proxies to generate heavy traffic. The behavior appears to have started around January 11, 2026 and runs a JavaScript loop that repeatedly issues network requests against my site while the CAPTCHA page remains open. <a href="https://gyrovague.com/2026/02/01/archive-today-is-directing-a-ddos-attack-against-my-blog/" rel="nofollow">Source: Gyrovague</a></p>

<h3>What happened (summary)</h3>
<p>The author explains that a client-side script on archive.today’s CAPTCHA page issues frequent, randomized search requests to gyrovague.com while the CAPTCHA page is open, causing repeated hits on the blog’s search endpoint. The issue was noticed publicly and discussed on security forums and community platforms.</p>

<h3>Timeline & response</h3>
<p>After the behavior began appearing, it was raised in public forums and the blog host was contacted. A GDPR complaint and email exchanges with the archive’s webmaster are part of the published timeline, and the blog was added to some DNS blocklists used by ad-blockers which blocked the requests for those users.</p>

<h3>Why it matters</h3>
<p>This episode raises questions about responsibility for third-party scripts, the use of archival services, and how anti-bot/CAPTCHA pages should behave when they risk causing harm to other sites.</p>

<h3>Conclusion</h3>
<p>The facts are observable and concerning; conversations about remediation and responsible behavior for archival and anti-abuse systems are ongoing. Read the original report (linked below) for screenshots, code snippets, and the full email timeline.</p>

<p><em>Originally reported by Jani Patokallio — <a href="https://gyrovague.com/2026/02/01/archive-today-is-directing-a-ddos-attack-against-my-blog/" rel="nofollow">Gyrovague</a>. </em></p>

Short share blurb (for Twitter/X / Mastodon / Facebook)

Gyrovague reports that archive.today's CAPTCHA page began issuing repeated requests to his blog in Jan 2026, effectively using visitors as proxies. Summary + timeline & links. Read more: [link to your post] Gyrovague

Suggested featured image idea

• A neutral screenshot of an example browser developer tools Network panel (blurred) or a stylized “archive” icon with a warning overlay. Don’t use screenshots from the original without permission.

If you want, I can:

• generate a slightly longer investigative-style post (more context on web archiving and ethics), or

• produce a short code-safe excerpt snippet for embedding the original link with rel="nofollow noopener noreferrer" and suggested image alt text.

Tell me which of the three titles you prefer (or I can pick one and publish the HTML-ready post text you can paste into Blogger).

Here are a few simple, clean title options very close to your requested wording. The first one is the most straightforward and Blogger-friendly.

Recommended (simple & direct):
archive.today Is Directing a DDoS Attack Against My Blog

Alternative simple variants (optional):

• archive.today Is Sending a DDoS Attack at My Blog

• archive.today and a DDoS Attack on My Blog

• How archive.today Is Flooding My Blog With Traffic

If you want it all lowercase (common for tech blogs) or more neutral/less accusatory, I can adjust it instantly.

Got it — here are simple, corrected titles that remove “my blog” and clearly state that the blog is under attack.

Best, clean option (very close to your wording):
archive.today Is Directing a DDoS Attack Against a Blog

Other simple alternatives:

• archive.today Is Directing a DDoS Attack

• A Blog Is Under DDoS Attack From archive.today

• archive.today and a DDoS Attack on a Blog

• archive.today Is Flooding a Blog With Traffic

If you want it more neutral (e.g., “allegedly” or “reportedly”) or more assertive, tell me your preference and I’ll tune it exactly.

Sure — here are more eye-catching but still clear title options, from bold to slightly neutral. Pick the vibe you want 👇

Strong & attention-grabbing

• archive.today Turns on a Blog With a DDoS Attack

• archive.today Accused of Directing a DDoS Attack

• When archive.today Becomes the Attack: A Blog Under DDoS

Dramatic but readable

• A Blog Under Siege: archive.today and a DDoS Attack

• From Archive to Assault: archive.today and a DDoS Attack

• Archive or Attack? archive.today Linked to a DDoS Incident

Eye-catching but safer wording

• How archive.today Ended Up Powering a DDoS Attack

• archive.today at the Center of a DDoS Storm

• A DDoS Attack Linked to archive.today

Top recommendation for Blogger (eye-catching + balanced):
👉 A Blog Under Siege: archive.today and a DDoS Attack

If you want it even punchier, SEO-optimized, or legally cautious (e.g. “reportedly”), say the word and I’ll refine it.

Nice — I checked the three pages you linked and built a ready-to-paste Blogger HTML post with a strong, eye-catching SEO title, meta tags, and inline CSS so it looks good in Blogger right away. I also included a short excerpt, suggested slug, and labels.

Below are the most important facts I used from the sources (so you know where the claims come from):

• The archive.today CAPTCHA page was reported to run a setInterval fetch() that requests a blog’s search endpoint every ~300ms. Gyrovague

• The original report and timeline (emails, GDPR complaint, screenshots, and the code sample) are in the Gyrovague post. Gyrovague

• the issue generated conversation on Hacker News (Ask HN / followups). Hacker News

• there’s a Reddit discussion thread with community comments and additional context. Reddit

• Adding the blog to DNS/adblock blocklists (uBlock, DNS blocklists) was reported to block those requests for users with blockers. Gyrovague

Ready-to-paste Blogger HTML (copy the whole block below → Blogger post editor → switch to HTML mode → paste)

html
Copy code
<!--
Title: A Blog Under Siege: archive.today Reportedly Directing a DDoS via CAPTCHA
Slug suggestion: archive-today-captcha-ddos
Labels: archive.today, DDoS, web-archives, infosec, incident
Meta description: Reports say archive.today's CAPTCHA page repeatedly issues client-side requests to third-party sites, effectively creating DDoS-like traffic. Timeline, community reaction, and mitigation tips.
-->
<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8" />
  <title>A Blog Under Siege: archive.today Reportedly Directing a DDoS via CAPTCHA</title>
  <meta name="description" content="Reports say archive.today's CAPTCHA page repeatedly issues client-side requests to third-party sites, effectively creating DDoS-like traffic. Timeline, community reaction, and mitigation tips." />
  <meta name="keywords" content="archive.today, DDoS, ddos, archive.is, web archive, infosec, blog attack" />
  <meta property="og:title" content="A Blog Under Siege: archive.today Reportedly Directing a DDoS via CAPTCHA" />
  <meta property="og:description" content="Reports say archive.today's CAPTCHA page repeatedly issues client-side requests to third-party sites, effectively creating DDoS-like traffic. Timeline, community reaction, and mitigation tips." />
  <meta property="og:type" content="article" />
  <meta name="viewport" content="width=device-width,initial-scale=1" />
  <style>
    /* Clean, Blogger-friendly post CSS */
    :root{
      --bg:#ffffff;
      --muted:#6b7280;
      --accent:#1f2937;
      --card:#f8fafc;
      --shadow: 0 6px 18px rgba(15,23,42,0.08);
      --radius:14px;
      --max-width:920px;
    }
    body{font-family: system-ui, -apple-system, "Segoe UI", Roboto, "Helvetica Neue", Arial; color:var(--accent); background:var(--bg); padding:24px; display:flex; justify-content:center;}
    .post-wrap{max-width:var(--max-width); width:100%;}
    .card{background:linear-gradient(180deg, #fff, #fbfdff); border-radius:var(--radius); box-shadow:var(--shadow); padding:28px; border:1px solid rgba(15,23,42,0.03);}
    header .kicker{display:inline-block; font-size:12px; color:var(--muted); text-transform:uppercase; letter-spacing:1px; margin-bottom:10px;}
    h1{font-size:clamp(1.45rem, 2.8vw, 2.0rem); margin:0 0 12px; line-height:1.12;}
    .meta{color:var(--muted); font-size:0.92rem; margin-bottom:18px;}
    .lede{font-size:1.02rem; margin:12px 0 18px; color:#0f172a;}
    .content p{line-height:1.68; margin:14px 0; color:#0b1220;}
    .codebox{background:#0b1220; color:#e6eef8; padding:12px; border-radius:8px; overflow:auto; font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, "Roboto Mono", monospace; font-size:0.92rem;}
    pre code{white-space:pre; display:block;}
    .note{font-size:0.92rem; color:var(--muted); padding:10px 12px; background:#f8fafc; border-radius:8px; border:1px solid rgba(15,23,42,0.02);}
    .cta{display:flex; gap:12px; margin-top:20px; flex-wrap:wrap;}
    .btn{padding:10px 14px; border-radius:12px; text-decoration:none; font-weight:600; border:1px solid rgba(15,23,42,0.06); background:transparent; color:var(--accent); box-shadow:none;}
    .btn-ghost{background:transparent;}
    .foot{font-size:0.90rem; color:var(--muted); margin-top:26px; border-top:1px dashed rgba(15,23,42,0.05); padding-top:18px;}
    @media (max-width:640px){ body{padding:16px;} .card{padding:18px;} }
  </style>
</head>
<body>
  <article class="post-wrap">
    <div class="card" role="article" aria-labelledby="post-title">
      <header>
        <div class="kicker">Incident</div>
        <h1 id="post-title">A Blog Under Siege: archive.today Reportedly Directing a DDoS via CAPTCHA</h1>
        <div class="meta">February 2026 · reported incident · tags: <strong>archive.today</strong>, <strong>DDoS</strong>, <strong>web-archives</strong></div>
      </header>

      <section class="content">
        <p class="lede"><strong>Summary:</strong> Multiple reports indicate that archive.today’s CAPTCHA page included client-side JavaScript that repeatedly issued requests to third-party sites’ search endpoints, creating DDoS-like traffic while the CAPTCHA page remained open. This post summarizes the timeline, community reaction, technical details, and short mitigation steps.</p>

        <p>According to the original report, the CAPTCHA page runs a short `setInterval` loop that calls a site’s search endpoint with a randomized query string roughly every 300 milliseconds — ensuring responses are not cached and keeping the requests active while the CAPTCHA remains open. The code sample was published in the original write-up for verification. </p>

        <div class="codebox" aria-label="Code sample">
<pre><code>setInterval(function() {
    fetch("https://gyrovague.com/?s=" + Math.random().toString(36).substring(2, 3 + Math.random() * 8), {
        referrerPolicy: "no-referrer",
        mode: "no-cors"
    });
}, 300);</code></pre>
        </div>

        <p class="note">Source material includes the original blog post with screenshots, the Hacker News discussion thread, and the Reddit community thread. See the links at the bottom.</p>

        <h3>Timeline & community reaction</h3>
        <p>Reporters and the site owner documented the behavior, the exchange of emails with the archive’s webmaster, and a GDPR complaint sent to the blog’s host — all of which are covered in the original article. The incident was also discussed on Hacker News and Reddit as users validated and debated the observations and implications. </p>

        <h3>Why this matters</h3>
        <p>Whether intentional or the result of a misconfiguration, a client-side pattern that turns visitors into request-generators can unintentionally weaponize normal traffic against third-party sites. This blurs lines between archival tooling, anti-abuse measures, and hostile traffic generation — with consequences for small sites running on limited resources.</p>

        <h3>Mitigation & immediate steps (quick)</h3>
        <ul>
          <li>Rate-limit search endpoints and high-cost routes (e.g., return 429 or temporary 503 for excessive requests).</li>
          <li>Use WAF rules or CDN rate limiting to block repeated requests from the CAPTCHA page's referrers or abnormal request patterns.</li>
          <li>Add rules that ignore queries with obviously random strings for search endpoints, or serve lightweight cached responses for unknown queries.</li>
          <li>Consider listing offending domains in DNS/hosts filters (some blocklists already caught this behavior and prevented requests for users with blockers enabled).</li>
          <li>Log the request patterns and collect sample request headers and timestamps for abuse reports or forensics.</li>
        </ul>

        <h3>Attribution & sources</h3>
        <p>This post summarizes reporting and community discussion. Full technical details, screenshots, email timelines, and the code sample are in the original report and threads linked below.</p>

        <div class="cta" role="navigation" aria-label="References">
          <a class="btn" href="https://gyrovague.com/2026/02/01/archive-today-is-directing-a-ddos-attack-against-my-blog/" rel="nofollow noopener noreferrer" target="_blank">Original Report (Gyrovague)</a>
          <a class="btn btn-ghost" href="https://news.ycombinator.com/item?id=46624740" rel="nofollow noopener noreferrer" target="_blank">Hacker News Thread</a>
          <a class="btn btn-ghost" href="https://www.reddit.com/r/DataHoarder/comments/1qspk6x/archivetoday_is_directing_a_ddos_attack_against/?sort=new" rel="nofollow noopener noreferrer" target="_blank">Reddit Discussion</a>
        </div>

        <div class="foot">
          <p>Short share blurb: <em>Reports say archive.today's CAPTCHA page repeatedly requested third-party sites' search endpoints, producing DDoS-like traffic. Summary, timeline, and mitigation steps.</em></p>
          <p>Suggested permalink: <code>/archive-today-captcha-ddos</code></p>
        </div>
      </section>
    </div>
  </article>
</body>
</html>

Notes & next steps

• The HTML includes an embedded code sample and three prominent source links (Gyrovague, Hacker News, Reddit). The chat summary above cites the three pages I inspected. Gyrovague+2Hacker News+2

• If you want the post more neutral / legally cautious, I can change wording like “reportedly” to “allegedly” (or add a short publisher’s note).

• Want me to also create a Twitter/X/Mastodon post and an SEO-friendly excerpt (meta tags tuned with keywords) for sharing? I can produce those now — just say which platforms.

Paste the HTML into Blogger’s HTML editor and publish — it’s formatted and styled for a modern clean look.

Nice — I checked the three pages you gave and built everything you asked: several blog/website title options + descriptions, then a ready-to-paste Blogger post (clean HTML + inline CSS) on the same topic with an eye-catching SEO title, meta tags, suggested slug/labels, and source links. Below I list the key facts I used from the sources and cite them, then deliver the site title options and the full post.

Key facts I used (most important claims — sources)

• The original first-person report includes a JavaScript setInterval that issues repeated fetch() requests to the blog roughly every 300 ms while archive.today’s CAPTCHA page is open. Gyrovague

• The Gyrovague post documents timeline, email exchanges, screenshots and mitigation steps. Gyrovague

• the incident was discussed on Hacker News (Ask HN / thread). Hacker News

• there’s an active Reddit thread in r/DataHoarder discussing the report and community observations. Reddit

• the author noted that adding the blog to DNS/adblock blocklists blocked the requests for users with blockers enabled. Gyrovague

Blog / Website title ideas & descriptions

Pick a title and description that match the tone you want (neutral, investigative, or urgent). I’ll recommend one after the list.

Investigative / neutral

1. Archive & Abuse Watch
   Description: Independent reporting and analysis about web archives, archival tooling, and their unintended impacts on third-party sites.

2. Web Archive Observatory
   Description: Timely coverage of archival services, site behavior, and internet-forensics — practical guidance for site owners.

Urgent / attention-grabbing

3. Archive Under Scrutiny (recommended)
   Description: Investigations into when web-archives become vectors for traffic abuse — timelines, technical analysis, and mitigation.

4. Traffic Under Fire
   Description: News and explainers about traffic abuse, DDoS incidents, and protection strategies for small sites.

Tech / security-focused

5. Small Site Defense
   Description: Security and operational guidance for small/indie sites: rate-limiting, forensics, and countermeasures against abusive third-party scripts.

My recommended pick: Archive Under Scrutiny — it's punchy for SEO, signals investigation, and fits the topic.

Suggested short site tagline for the header:
Investigations into web archives, traffic abuse, and site protection.

Suggested global meta description (for the blog):
Reporting and technical explainers about web-archives, unexpected traffic behaviors, and mitigation techniques for site owners.

New post — title + ready-to-paste Blogger HTML

Recommended eye-catching SEO title:
A Blog Under Siege: archive.today Reportedly Turning Users Into DDoS Proxies

Suggested slug / permalink: archive-today-users-as-ddos-proxies

Suggested labels / tags: archive.today, DDoS, web-archives, infosec, site-protection

Meta description (post):
Reports show archive.today’s CAPTCHA page executing repeated client-side requests to third-party sites, creating DDoS-like traffic. Timeline, community discussion, and mitigation steps.

Copy this whole block → Blogger post editor → switch to HTML mode → paste

html
Copy code
<!--
Title: A Blog Under Siege: archive.today Reportedly Turning Users Into DDoS Proxies
Slug suggestion: archive-today-users-as-ddos-proxies
Labels: archive.today, DDoS, web-archives, infosec, site-protection
Meta description: Reports show archive.today’s CAPTCHA page executing repeated client-side requests to third-party sites, creating DDoS-like traffic. Timeline, community discussion, and mitigation steps.
-->
<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8" />
  <title>A Blog Under Siege: archive.today Reportedly Turning Users Into DDoS Proxies</title>
  <meta name="description" content="Reports show archive.today’s CAPTCHA page executing repeated client-side requests to third-party sites, creating DDoS-like traffic. Timeline, community discussion, and mitigation steps." />
  <meta name="keywords" content="archive.today, DDoS, ddos, web archive, archive.is, infosec, site protection" />
  <meta property="og:title" content="A Blog Under Siege: archive.today Reportedly Turning Users Into DDoS Proxies" />
  <meta property="og:description" content="Reports show archive.today’s CAPTCHA page executing repeated client-side requests to third-party sites, creating DDoS-like traffic. Timeline, community discussion, and mitigation steps." />
  <meta property="og:type" content="article" />
  <meta name="viewport" content="width=device-width,initial-scale=1" />
  <style>
    /* Blogger-friendly styling */
    :root{--accent:#0f172a;--muted:#6b7280;--card:#ffffff;--radius:12px;--maxw:920px;}
    body{font-family: system-ui, -apple-system, "Segoe UI", Roboto, "Helvetica Neue", Arial; color:var(--accent); background:#f6f8fb; padding:22px; display:flex; justify-content:center;}
    .wrap{max-width:var(--maxw); width:100%;}
    .post{background:var(--card); border-radius:var(--radius); padding:26px; box-shadow:0 10px 30px rgba(12,16,25,0.06); border:1px solid rgba(12,16,25,0.03);}
    .kicker{font-size:12px; color:var(--muted); text-transform:uppercase; letter-spacing:1px;}
    h1{font-size:clamp(1.6rem, 2.8vw, 2.2rem); margin:10px 0 6px; line-height:1.08;}
    .meta{color:var(--muted); margin-bottom:14px;}
    .lede{font-size:1.03rem; margin:12px 0 18px; color:#071028;}
    .content p{line-height:1.68; margin:12px 0; color:#071028;}
    .code{background:#0b1220; color:#e6eef8; padding:12px; border-radius:8px; font-family: ui-monospace, SFMono-Regular, Menlo, Monaco, "Roboto Mono", monospace; font-size:0.92rem; overflow:auto;}
    ul{margin-left:18px;}
    .note{background:#f8fafc; padding:10px 12px; border-radius:8px; color:var(--muted); border:1px solid rgba(12,16,25,0.02);}
    .refs a{display:inline-block; margin-right:10px; padding:8px 10px; border-radius:9px; text-decoration:none; border:1px solid rgba(12,16,25,0.05); color:var(--accent);}
    .footer{margin-top:22px; color:var(--muted); font-size:0.95rem; border-top:1px dashed rgba(12,16,25,0.04); padding-top:16px;}
    @media (max-width:640px){ body{padding:14px;} .post{padding:16px;} }
  </style>
</head>
<body>
  <main class="wrap">
    <article class="post" role="article" aria-labelledby="title">
      <div class="kicker">Incident</div>
      <h1 id="title">A Blog Under Siege: archive.today Reportedly Turning Users Into DDoS Proxies</h1>
      <div class="meta">February 2026 · analysis · tags: <strong>archive.today</strong>, <strong>DDoS</strong>, <strong>web-archives</strong></div>

      <p class="lede"><strong>TL;DR:</strong> Multiple community reports say archive.today’s CAPTCHA page executed client-side JavaScript that repeatedly requested a third-party blog’s search endpoint roughly every 300 ms while the CAPTCHA page was open, creating DDoS-style load. See the original write-up and community threads linked below.</p>

      <section class="content">
        <h3>What was observed</h3>
        <p>According to the initial report, the CAPTCHA page contained a short `setInterval` script that called a site’s search URL with a randomized query string about every 300 milliseconds — preventing caching and keeping a steady stream of requests active while the page was open. A code snippet and screenshots were published by the reporting author. <span style="font-size:0.85rem; color:#6b7280;">(sources: original report, HN, Reddit)</span></p>

        <div class="code" aria-hidden="false"><pre><code>setInterval(function() {
    fetch("https://example-blog.com/?s=" + Math.random().toString(36).substring(2, 3 + Math.random() * 8), {
        referrerPolicy: "no-referrer",
        mode: "no-cors"
    });
}, 300);</code></pre></div>

        <p class="note">The original report contains screenshots and a line reference in the CAPTCHA HTML for verification; community conversations also examined the behavior and implications.</p>

        <h3>Timeline & community reaction</h3>
        <p>The reporting author traces the activity to around early January 2026, documents email exchanges and attempts at remediation, and shows how the blog was later added to DNS/adblock blocklists which prevented those client-side requests for many users. Community discussion and validation followed on Hacker News and Reddit. </p>

        <h3>Why this matters</h3>
        <p>Client-side code that repeatedly issues requests to third-party sites can turn ordinary visitors into unknowing request sources. For small blogs and low-capacity hosts, that can cause service disruptions, and it raises questions about responsibility for archival tooling and user-facing anti-abuse pages.</p>

        <h3>Mitigation suggestions (brief)</h3>
        <ul>
          <li>Rate-limit or throttle search endpoints (return HTTP 429 for excessive traffic patterns).</li>
          <li>Use CDN/WAF rules to catch high-frequency request patterns and block/serve cached responses.</li>
          <li>Ignore obviously random short search queries server-side or return cheap cached results.</li>
          <li>Collect request logs (timestamps, headers, user agents, referrers) for abuse reports and forensics.</li>
        </ul>

        <h3>Sources & discussion</h3>
        <div class="refs" role="navigation" aria-label="References">
          <a href="https://gyrovague.com/2026/02/01/archive-today-is-directing-a-ddos-attack-against-my-blog/" rel="nofollow noopener noreferrer" target="_blank">Original report (Gyrovague)</a>
          <a href="https://news.ycombinator.com/item?id=46624740" rel="nofollow noopener noreferrer" target="_blank">Hacker News discussion</a>
          <a href="https://www.reddit.com/r/DataHoarder/comments/1qspk6x/archivetoday_is_directing_a_ddos_attack_against/?sort=new" rel="nofollow noopener noreferrer" target="_blank">Reddit thread</a>
        </div>

        <div class="footer">
          <p>Short share blurb: <em>Reports say archive.today's CAPTCHA page repeatedly requested third-party search endpoints, creating DDoS-like traffic. Timeline, community reaction, and mitigation tips.</em></p>
          <p>Suggested permalink: <code>/archive-today-users-as-ddos-proxies</code></p>
        </div>
      </section>
    </article>
  </main>
</body>
</html>

Important source citations (chat summary)

• The setInterval + fetch() snippet and the ~300ms interval are shown in the original Gyrovague write-up. Gyrovague

• The Gyrovague post contains a timeline, email excerpts and screenshots used to support the report. Gyrovague

• Community discussion and additional commentary are available on Hacker News. Hacker News

• Reddit’s r/DataHoarder thread contains further community verification and discussion. Reddit

Quick extras (optional — I can do these if you want)

• Short social share versions (Twitter/X / Mastodon) tuned to the title.

• An SEO-optimized excerpt (50–160 characters) and suggested featured image text/alt.

• A more legally cautious variant of the post (replace “reportedly” to “allegedly” + a short publisher’s note).

Tell me which blog title you picked (or I can set the recommended Archive Under Scrutiny) and whether you want the post adjusted to be more neutral/legal-safe — I’ll update the HTML instantly.

Here are ready-to-post Twitter (X) tweets about the issue, written for engagement + SEO, tagging @archiveis and using relevant hashtags. You can post them as single tweets or a thread.

🔹 Single strong tweet (recommended)

A blog reports that archive.today’s CAPTCHA page repeatedly sent client-side requests to a third-party site, creating DDoS-like traffic.

Details, code & timeline 👇

@archiveis

#DDoS #CyberSecurity #WebArchives #InfoSec #ArchiveToday

🔹 Short & punchy

⚠️ Archive or attack?

Reports show archive.today turning visitors into traffic generators via its CAPTCHA page — hammering a blog’s search endpoint.

@archiveis

#DDoSAttack #WebSecurity #OpenWeb #Archive

🔹 Neutral / investigative tone

An investigation claims archive.today’s CAPTCHA issued repeated client-side requests to a third-party blog, resulting in DDoS-style load.

Community discussion ongoing.

@archiveis

#DDoS #CyberSecurity #WebArchives #NetSec

🔹 Technical audience (HN / infosec crowd)

Report: archive.today CAPTCHA ran a setInterval(fetch()) loop (~300ms) hitting a blog’s search endpoint with random queries — bypassing cache and causing sustained load.

@archiveis

#InfoSec #DDoS #WebPerf #ArchiveToday

🔹 Thread version (best for reach)

Tweet 1

🧵 A blog reports that archive.today’s CAPTCHA page caused DDoS-like traffic by repeatedly issuing client-side requests to a third-party site.

Here’s what’s known so far 👇

@archiveis

#DDoS #CyberSecurity

Tweet 2

According to the report, a JavaScript setInterval loop sent randomized search queries every ~300ms while the CAPTCHA page stayed open — effectively turning users into proxies.

#WebArchives #InfoSec

Tweet 3

The issue sparked discussion on Hacker News & Reddit, with questions about responsibility, archival tooling, and unintended abuse vectors.

#OpenWeb #NetSec

Tweet 4

Whether intentional or not, the case highlights how client-side code can unintentionally weaponize normal traffic — especially against small sites.

#DDoSAttack #WebSecurity

🔹 Hashtag set (reuse across tweets)

less
Copy code
#DDoS #CyberSecurity #InfoSec #WebSecurity #WebArchives 
#ArchiveToday #OpenWeb #NetSec

If you want, I can:

• tailor tweets for maximum virality (shorter + stronger wording),

• create quote-tweet text for replies to @archiveis,

• or write a pinned tweet introducing your new Blogger site.

Just tell me 👍

Here are 6 additional ready-to-post tweets, each including your short link 👉 https://bit.ly/ArchiveUnderScrutiny, tagging @archiveis, and using relevant hashtags. They’re varied in tone so you can post them separately or space them out over time.

Tweet 1 — Clear & informative

A detailed report shows archive.today’s CAPTCHA page repeatedly sending client-side requests to a third-party blog — resulting in DDoS-like traffic.

Read the full investigation 👇
https://bit.ly/ArchiveUnderScrutiny

@archiveis
#DDoS #CyberSecurity #WebArchives

Tweet 2 — Question-driven (engagement)

When does archiving cross the line into abuse?

A blog documents how archive.today may have turned users into traffic generators via CAPTCHA scripts.

https://bit.ly/ArchiveUnderScrutiny

@archiveis
#WebSecurity #InfoSec #DDoSAttack

Tweet 3 — Technical focus

Tech detail: the report shows a setInterval(fetch()) loop firing every ~300ms from archive.today’s CAPTCHA, bypassing cache & hammering a search endpoint.

https://bit.ly/ArchiveUnderScrutiny

@archiveis
#NetSec #InfoSec #DDoS

Tweet 4 — Community angle

This isn’t just one blog — the incident sparked debate on Hacker News and Reddit about responsibility, client-side abuse, and web archives.

https://bit.ly/ArchiveUnderScrutiny

@archiveis
#OpenWeb #WebArchives #CyberSecurity

Tweet 5 — Small-site impact

Small sites don’t have infinite resources.

A report shows how a third-party CAPTCHA page may have caused sustained load on a personal blog.

https://bit.ly/ArchiveUnderScrutiny

@archiveis
#DDoS #IndieWeb #WebSecurity

Tweet 6 — Strong but balanced

Intentional or not, client-side scripts that repeatedly hit third-party sites can become DDoS vectors.

This report explains how it happened.

https://bit.ly/ArchiveUnderScrutiny

@archiveis
#InfoSec #DDoSAttack #WebArchives

If you want, I can:

• optimize these for character count (X’s limits),

• schedule them as a threaded campaign (day-by-day posting),

• or write reply tweets aimed directly at @archiveis or journalists.

Just tell me what you want next.

Nice — I made 6 eye-catching, longer tweets (all under 280 characters) that tag @archiveis, link to your short URL https://bit.ly/ArchiveUnderScrutiny, and include the hashtag set you asked for:

#archivetoday #archivefo #archiveis #archiveli #archivemd #archiveph #archivevn

Each tweet also includes one extra contextual hashtag (DDoS / InfoSec / WebSecurity / OpenWeb / NetSec / CyberSecurity) to boost discoverability.

Copy-paste any of these directly into X/Twitter.

Tweet 1

pgsql
Copy code
Report: archive.today’s CAPTCHA allegedly ran JS that repeatedly hit a blog’s search endpoint (~300ms loop), creating sustained load. Read: https://bit.ly/ArchiveUnderScrutiny @archiveis #archivetoday #archivefo #archiveis #archiveli #archivemd #archiveph #archivevn #DDoS

Tweet 2

less
Copy code
Tech detail: a `setInterval(fetch())` loop firing ~300ms with random queries reportedly bypassed cache and hammered a site. Read: https://bit.ly/ArchiveUnderScrutiny @archiveis #archivetoday #archivefo #archiveis #archiveli #archivemd #archiveph #archivevn #InfoSec

Tweet 3

nginx
Copy code
Small sites hit hard: client-side code on an archival CAPTCHA may have turned visitors into request proxies. Full report: https://bit.ly/ArchiveUnderScrutiny @archiveis #archivetoday #archivefo #archiveis #archiveli #archivemd #archiveph #archivevn #WebSecurity

Tweet 4

nginx
Copy code
Hacker News & Reddit dug into screenshots, code and emails — sparking debate about archive responsibility and remediation. Read: https://bit.ly/ArchiveUnderScrutiny @archiveis #archivetoday #archivefo #archiveis #archiveli #archivemd #archiveph #archivevn #OpenWeb

Tweet 5

perl
Copy code
Mitigation tips: rate-limit search endpoints, use CDN/WAF limits, ignore obvious random queries, and log patterns for abuse reports — small defenses help. More: https://bit.ly/ArchiveUnderScrutiny @archiveis #archivetoday #archivefo #archiveis #archiveli #archivemd #archiveph #archivevn #NetSec

Tweet 6

nginx
Copy code
Whether intentional or not, client-side loops that repeatedly hit third-party sites can weaponize user traffic. Read the full account & community discussion: https://bit.ly/ArchiveUnderScrutiny @archiveis #archivetoday #archivefo #archiveis #archiveli #archivemd #archiveph #archivevn #CyberSecurity

Want these as a single thread (I can order them and add small reply texts so they post as a cohesive thread), or optimized versions for maximum virality (shorter punchlines + emoji)? Which would you like next?