Firefox Users Report Infinite reCAPTCHA Loops on archive.is
A technical dispute on Hacker News suggests the issue may be tied to DNS configurations rather than browser bias.
Users of the Firefox browser on Linux have reported being trapped in infinite Google reCAPTCHA loops when attempting to access the web archiving service archive.is. The issue has sparked a debate among technical users regarding whether the site is discriminating against non-Chrome browsers or targeting specific network configurations.
The reports first gained traction on Hacker News, where a user described a systemic failure to pass the bot-detection checks. Other users confirmed experiencing similar loops, noting that while closing the browser tab sometimes resolves the problem, the audio-based reCAPTCHA alternatives are frequently unintelligible and ineffective.
The DNS Theory
While initial suspicions pointed toward a bias against Firefox or ad-blocking software, some community members suggest the problem lies with the user's Domain Name System (DNS) settings. One commenter claimed that archive.today does not utilize a genuine reCAPTCHA system and that the Cloudflare-branded page users encounter is actually a "punishment" for using Cloudflare's 1.1.1.1 DNS.
According to this theory, the site owner may be intentionally blocking or hindering users of 1.1.1.1 because that specific DNS service does not support EDNS (Extension Mechanisms for DNS) client subnets. EDNS client subnets allow a DNS resolver to pass a portion of the user's IP address to the authoritative DNS server, providing more accurate geographic routing and security filtering.
Why It Matters
This incident highlights the often opaque nature of bot protection and traffic management. When a website implements aggressive filtering based on network metadata—such as the presence or absence of EDNS client subnets—the resulting errors can be easily misidentified by the end user as browser-specific discrimination or software bugs.
For the broader industry, it underscores a growing tension between privacy-focused network configurations and the restrictive security measures employed by site administrators. If site owners begin penalizing specific DNS providers, it creates a fragmented web experience where access is determined not by the user's identity or browser, but by the technical specifications of their network resolver.
What's Next
It remains unconfirmed whether archive.is has an official policy of penalizing 1.1.1.1 DNS users or if the reported reCAPTCHA page is a deliberate design choice. Users continue to share anecdotal workarounds, but a formal explanation from the site's administration has not been provided. Observers will be watching to see if other archiving services or high-traffic sites implement similar DNS-based filtering.