5 ms·

Is Something Going on with Archive.ph?

15 points by gdudeman 3y ago

Archive.is is showing a default page, archive.ph is showing an insecure connection and then doesn’t resolve. Legal troubles?

gravitate 3y ago
'One more step. Please complete the security check to access' Except I have JS disabled and can't complete the CAPTCHA interstitial.
- LinuxBender 3y ago
  That is what one would see if using Cloudflare DNS. It's cloudflare's captcha but archive.is is not on of their customers so it will just be a never-ending captcha.
  - dtech 3y ago
    Why would cloudflare DNS work that way? Why don't they cache the authoritative DNS server?
    - nimih 3y ago
      archive.ph misreports its IP address when responding to queries from cloudflare, apparently on purpose. It's not too hard to dig up some old threads/comments discussing the issue if you're curious about the details--you can find A (The?) Cloudflare Guy discussing it from cloudflare's perspective here on HN, and The Archive.ph Guy tweeting about it from his perspective.
    - detaro 3y ago
      Archive.ph intentionally gives the wrong IP to requests from Cloudflare DNS servers, because cloudflare is not giving them information about the IP subnet that made the original DNS request, and archive.ph claims that is a massive problem for them.
    - Brian_K_White 3y ago
      It's a long standing well known thing for years now. For the technical details just google "archive.is cloudflare". It's been discussed and written up and explained many times over by now. Many times over right here on HN even. I will only add that as far as I can tell, neither side is exactly doing anything wrong, other than the fact that they both could have concocted some sort of special handling for each other years ago if they wanted. The failure to bother is on both I think.
- Dwedit 3y ago
  In Firefox settings, look for 'DNS'. For the "DNS over HTTPS" section, click the "Manage Exceptions" button, and manually add "archive.is", "archive.ph", "archive.today". Then restart the browser, and it might work.
  - Brian_K_White 3y ago
    It has nothing to do with dns over https. I wish people would stop giving out this incorrect direction.
    - Dwedit 3y ago
      It has to do with Cloudflare being the selected choice of provider, and adding to an exclusion list will bypass queries to Cloudflare.
Bender 3y ago
Are you by chance using Cloudflare for DNS? If so that would be the answer. Archive.is gives CF their own IP's back to them rather than the correct DNS answer on purpose. Some people will get endless captchas and some will get errors.
digianarchist 3y ago
I always use the onion link. Never appears to be down.
gvkhna 3y ago
I switched Archive domains from Cloudflare DNS to Mullvad DNS on my unbound, haven’t had issues since. I also would recommend quad9 as a dns resolver, it doesn’t have an issue.
- toomuchtodo 3y ago
  I think Archive doesn’t work with Apple’s private relay browsing feature due to them using Cloudflare for that capability, although I have not had time to test. Absolutely know it doesn’t work when using Cloudflare public DNS servers though.
ThePowerOfFuet 3y ago
Works for me.
invisibel 3y ago
It resolves for me but shows a captcha loop as others said, strangely the captcha page I'm getting seems to be some mockup of the Cloudflare one, using reCAPTCHA which Cloudflare publicly spoke about switching from. Seems to be doing something odd, code of the page includes some XmlHttpRequest to a blog site with randomized query string (see end of https://pastebin.com/W21Au8RK https://pastebin.com/W21Au8RK), along with some fingerprint library (though commented out) That blog site loads very slow for me if I go there manually - maybe some kind of DoS being directed to it? Seen this same faux-cloudflare page used on btdig.com too, with the same strange XmlHttpRequest & fingerprint code, pretty weird.
djhope99 3y ago
The other day I was on hotel Wi-Fi and I got this recapture loop. I got off the Wi-Fi and went to mobile network and it came back. Are some ISPs blocking it ?
- schappim 3y ago
  I can get stuck in the recapture loop on normal Wi-Fi.
voytec 3y ago
> Legal troubles? Wouldn't be surprising - these services were basically stealing content from other sites and replacing original ads/tracking/spyware with their own.
michelangelo 3y ago
Similar discussion few days ago with more insights: https://news.ycombinator.com/item?id=38063548 https://news.ycombinator.com/item?id=38063548
deleted 3y ago
[deleted]

15 points by gdudeman 3y ago

Archive.is is showing a default page, archive.ph is showing an insecure connection and then doesn’t resolve. Legal troubles?

gravitate 3y ago

'One more step. Please complete the security check to access' Except I have JS disabled and can't complete the CAPTCHA interstitial.

LinuxBender 3y ago
That is what one would see if using Cloudflare DNS. It's cloudflare's captcha but archive.is is not on of their customers so it will just be a never-ending captcha.
- dtech 3y ago
  Why would cloudflare DNS work that way? Why don't they cache the authoritative DNS server?
  - nimih 3y ago
    archive.ph misreports its IP address when responding to queries from cloudflare, apparently on purpose. It's not too hard to dig up some old threads/comments discussing the issue if you're curious about the details--you can find A (The?) Cloudflare Guy discussing it from cloudflare's perspective here on HN, and The Archive.ph Guy tweeting about it from his perspective.
  - detaro 3y ago
    Archive.ph intentionally gives the wrong IP to requests from Cloudflare DNS servers, because cloudflare is not giving them information about the IP subnet that made the original DNS request, and archive.ph claims that is a massive problem for them.
  - Brian_K_White 3y ago
    It's a long standing well known thing for years now. For the technical details just google "archive.is cloudflare". It's been discussed and written up and explained many times over by now. Many times over right here on HN even. I will only add that as far as I can tell, neither side is exactly doing anything wrong, other than the fact that they both could have concocted some sort of special handling for each other years ago if they wanted. The failure to bother is on both I think.
Dwedit 3y ago
In Firefox settings, look for 'DNS'. For the "DNS over HTTPS" section, click the "Manage Exceptions" button, and manually add "archive.is", "archive.ph", "archive.today". Then restart the browser, and it might work.
- Brian_K_White 3y ago
  It has nothing to do with dns over https. I wish people would stop giving out this incorrect direction.
  - Dwedit 3y ago
    It has to do with Cloudflare being the selected choice of provider, and adding to an exclusion list will bypass queries to Cloudflare.

Bender 3y ago

Are you by chance using Cloudflare for DNS? If so that would be the answer. Archive.is gives CF their own IP's back to them rather than the correct DNS answer on purpose. Some people will get endless captchas and some will get errors.

digianarchist 3y ago

I always use the onion link. Never appears to be down.

gvkhna 3y ago

I switched Archive domains from Cloudflare DNS to Mullvad DNS on my unbound, haven’t had issues since. I also would recommend quad9 as a dns resolver, it doesn’t have an issue.

toomuchtodo 3y ago
I think Archive doesn’t work with Apple’s private relay browsing feature due to them using Cloudflare for that capability, although I have not had time to test. Absolutely know it doesn’t work when using Cloudflare public DNS servers though.

ThePowerOfFuet 3y ago

Works for me.

invisibel 3y ago

It resolves for me but shows a captcha loop as others said, strangely the captcha page I'm getting seems to be some mockup of the Cloudflare one, using reCAPTCHA which Cloudflare publicly spoke about switching from. Seems to be doing something odd, code of the page includes some XmlHttpRequest to a blog site with randomized query string (see end of https://pastebin.com/W21Au8RK https://pastebin.com/W21Au8RK), along with some fingerprint library (though commented out) That blog site loads very slow for me if I go there manually - maybe some kind of DoS being directed to it? Seen this same faux-cloudflare page used on btdig.com too, with the same strange XmlHttpRequest & fingerprint code, pretty weird.

djhope99 3y ago

The other day I was on hotel Wi-Fi and I got this recapture loop. I got off the Wi-Fi and went to mobile network and it came back. Are some ISPs blocking it ?

schappim 3y ago
I can get stuck in the recapture loop on normal Wi-Fi.

voytec 3y ago

> Legal troubles? Wouldn't be surprising - these services were basically stealing content from other sites and replacing original ads/tracking/spyware with their own.

michelangelo 3y ago

Similar discussion few days ago with more insights: https://news.ycombinator.com/item?id=38063548 https://news.ycombinator.com/item?id=38063548

deleted 3y ago

[deleted]