Looks like `archive.is` is currently using reCaptcha. So Google might be able to figure out and tell the FBI who runs it. (If not by data around the registration, then by data around accesses to the site that seem to be by a developer of it, coupled with their cross-site tracking data.)
I've also seen Cloudflare similarly in the loop, and they have similar cross-site tracking data.
Lesson: The same third-party tech surveillance companies to which you sell out all your visitors, can also violate you.
Coincidentally, their adoption of Google CAPTCHA (along with requiring javascript) is why I stopped using archive.today. I don't particularly want either of those entities executing mystery code in my browser, or on my computer at all.
Helping Google to collect records of my reading habits is also unappealing.
I've also seen Cloudflare similarly in the loop, and they have similar cross-site tracking data.
Lesson: The same third-party tech surveillance companies to which you sell out all your visitors, can also violate you.