This may be your issue. I've had it happen with OpenDNS as well. Archive.today frequently experiences resolution issues with major DNS providers (like Cloudflare, NextDNS) due to its reliance on EDNS Client-Subnet (ECS) data for geo-routing, which some providers strip for privacy. If using OpenDNS or others, manual DNS rewrites (mapping archive.ph to IPs like 178.250.246.75) are often required to bypass connection issues. ###Archive.today & DNS Troubleshooting ----------- The Problem: Archive.today intentionally blocks or fails to resolve for DNS providers that do not pass client IP information (ECS). This is designed to enforce geo-specific requirements, though it often results in 403 Forbidden or connection timeouts for users. Alternative Providers: While Cloudflare (1.1.1.1) often has issues, other providers like Google DNS (8.8.8.8) or switching to ISP-provided DNS may work, according to users in a Reddit discussion. Manual Fix (Rewrites): If your DNS provider (e.g., NextDNS) cannot resolve the site, you can set up manual "rewrites" in your DNS settings for archive.today, archive.is, and archive.ph to 178.250.246.75 or 82.153.138.197. ###Current Status and Controversies ------------ FBI Investigation: In October 2025, the FBI subpoenaed Tucows, the registrar for archive.today, as part of an undisclosed investigation. AdGuard DNS Incident: In late 2025, a fabricated entity (WebAbuseDefense) pressured AdGuard DNS to block archive.today, leading to a temporary, now-resolved, dispute over accusations of hosting illegal content. Access Issues: As of late 2025, the site faces intermittent access issues stemming from this controversy and ongoing investigations