This addon includes "archive.is" (also known as "archive.today") as a default option.

Early this year, that site's owner/operator inserted malicious code into the site's captcha page, hijacking archive.is/archive.today visitors' internet connections to commit a DDOS attack on a small blog.

While debating whether to blacklist archive.is/archive.today for that alone, Wikipedia editors discovered that the site had also tampered with its own 'archived' web snapshots, altering them to insert the name of the targeted blog owner and frame them for things they never said. This was the nail in the coffin for the site's credibility as an archive.

Wikipedia blacklisted archive.is/archive.today, despite that doing so would require the replacement of almost 700,000 existing reference links.

It is not a trustworthy website.

This platform won't allow me to include a url. But source (with more details) is at arstechnica dot com slash "tech-policy/2026/02/wikipedia-bans-archive-today-after-site-executed-ddos-and-altered-web-captures/".

Anyway, I am assuming the maker of this extension missed all this news, since said website is still included prominently in the extension.

I would have inquired first, before reviewing, but unfortunately github seems to detest one of my browser settings or extensions, so I can't currently use it.

In any case, if you choose to use this extension, be sure to disable the archive.is/archive.today option in its settings.

Alas it breaks login pages which use Cloudflare captcha!

I first thought that uBO and/or Privacy Badger are the culprit and disabled those, but then still could reliably reproduce the bug. Then I disabled *ALL* my extensions and enabled them one by one, meanwhile testing logging in. When I turned on Web Archives, login stopped working, I got an error message after entering my credentials and clicking the "I am a human" checkbox on the popup Cloudflare captcha.

Once I disabled Web Archives, login started to work again.

Mind you, this test was done with uBO and PB still being disabled.

You're better off just manually visiting the archive websites. Here's a suggestion, instead of opening a specific snapshot, open the snapshots (or history) page where the user can see (if) different snapshots and play around till they find the one that works. This will reduce the number of times the user gets "No results"

All these permissions for what is essentially just a bookmark.