Differs by the ISP you have, I've seen DNS manipulation, IP filtering, hostname filtering, and HTTPS interception so far. Obviously most websites use TLS today so it mostly "fails" so people see certificate errors rather than their scary "You're contributing to breaking the law blah blah blah". Sometimes just straight up timeouts, resets, or generic connection failures.
Differs by the ISP you have, I've seen DNS manipulation, IP filtering, hostname filtering, and HTTPS interception so far. Obviously most websites use TLS today so it mostly "fails" so people see certificate errors rather than their scary "You're contributing to breaking the law blah blah blah". Sometimes just straight up timeouts, resets, or generic connection failures.
According to this site https://bandaancha.eu/articulos/gobierno-tiene-lista-web-ofi..., they use SNI (https://en.wikipedia.org/wiki/Server_Name_Indication)
Enabling ESNI in Firefox should be a countermeasure (encrypted SNI extension of the TLS so that hostname is no longer sent in plain text)
https://superuser.com/questions/1346634/modern-browser-with-...
It's not magic. archive.is has no HTTPS record, so ESNI cannot be used.