Hacker News new | past | comments | ask | show | jobs | submit login

> Right but then working slow looks like archive.is issue but is ultimately caused by cloudflare.

Whereas not loading at all looks like archive.is issue but is ultimately caused by archive.is.

> CF is bascically saying "we can know your IP but not the site you are trying to resolve" (that will know your IP anyway once you navigate there).

Not necessarily. For example, the DNS query could go straight to CF while the eventual request to archive.is goes through a proxy or VPN.




Ok, really? Who is using a proxy for HTTP but not DNS in 2023?




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: