Alternative to archive.ph, no Javascript, no CAPTCHAs:

   x=www.washingtonpost.com 
   { 
   printf 'GET /technology/2026/02/07/ai-spending-economy-shortages/ HTTP/1.1\r\n'
   printf 'Host: '$x'\r\n'
   printf 'User-Agent: Chrome/115.0.5790.171 Mobile Safari/537.36 (compatible ; Googlebot/2.1 ; +http://www.google.com/bot.html)\r\n'
   printf 'X-Forwarded-For: 66.249.66.1\r\n\r\n'
   }|busybox ssl_client -n $x $x > 1.htm
   firefox ./1.htm

▲ 1vuio0pswjnm7 2 hours ago | parent | next [-]

Anonymous middleman that could potentiallly collect browsing histories, serves CAPTCHAS, requires Javascript, maybe in crosshairs of authorities, unreliable according to some commenters (YMMV). NB. Nothing about "honeypot", just observations (cf. "accusations")

Someone recently noticed an apparent DDOS attempt on some blogger using Javascript fetch function

The site used to include a tracking pixel containing the visitor's IP address

Also used to ping mail.ru

Would need to look at the page source again to see what it contains today

It's a crowd favorite

People love it

▲

dmix 2 hours ago | parent [-]

Are you accusing archive.today of being a honeypot for the feds because they use Cloudflare? That's a bit much don't you think?

	▲	MallocVoidstar 2 hours ago \| parent [-]
		Archive.today don't use Cloudflare, the admin mimics their captcha page because he hates them. He also used to captcha-loop anyone using Cloudflare's DNS resolver because they don't send the IP subnet of clients to upstreams. I don't think it's a honeypot, though, it's not like he's learning much about me other than I like not paying for news sites.

▲ WarOnPrivacy 3 hours ago | parent | prev [-]

> Alternative to archive.ph, no Javascript, no CAPTCHAs:

The other tld have been kinder to me (no captcha).

https://archive.md/J8pg5

https://archive.fo/J8pg5