My employer blocks it on our work computers. Looking around it seems like this is commonly done because one of the main uses of the .zip tld is to spread malware by faking links to zip files using "/" look alike characters and other URLs that look like download links to zip files.
I had little opinion on .zip but this convinced me to go figure out how to block .zip tld. Why would someone risk all those attack vectors when there is so much available on the many other tlds. I could see myself getting caught by many of them.
Comments
My employer blocks it on our work computers. Looking around it seems like this is commonly done because one of the main uses of the .zip tld is to spread malware by faking links to zip files using "/" look alike characters and other URLs that look like download links to zip files.
Well by that token we should probably also block the .com TLD since that is actually an executable file suffix.
Modern 64-bit Windows doesn't execute .com files, unless the user installs an emulator or something.
It does execute PE files with .com extension.
https://luke.zip/posts/zip-defense/
I get asked this a lot, so here's my defense!
I had little opinion on .zip but this convinced me to go figure out how to block .zip tld. Why would someone risk all those attack vectors when there is so much available on the many other tlds. I could see myself getting caught by many of them.