Yup. A lot of network admins are blocking domains like *.zip and *.mov because the majority of them are used for malicious link abuse and it isn’t worth the work to check them.
If you operate a *.zip instance: now is the time to take the hit, and start over at a proper domain. If you’re a Lemmy user at one of these TLD instances: now is the time to take the hit and move to another instance with a regular TLD.
There are situations where a url with .zip at the end could download a zip file with the newest edition of some popular free game. A very similar looking url could also end with .zip, download a similarly looking zip file, with very different actions when the software is launched.
Putting anything onto or any effort into a .zip domain seems futile and short-sighted.
Also easily abusable
Yup. A lot of network admins are blocking domains like *.zip and *.mov because the majority of them are used for malicious link abuse and it isn’t worth the work to check them.
If you operate a *.zip instance: now is the time to take the hit, and start over at a proper domain. If you’re a Lemmy user at one of these TLD instances: now is the time to take the hit and move to another instance with a regular TLD.
Not op, but still curious… what is wrong with .zip domains?
Here is one example: https://medium.com/@bobbyrsec/the-dangers-of-googles-zip-tld-5e1e675e59a5
There are situations where a url with .zip at the end could download a zip file with the newest edition of some popular free game. A very similar looking url could also end with .zip, download a similarly looking zip file, with very different actions when the software is launched.
Great article! Thanks for the share.
So is the concern (for lemmy.zip) that .zip domains might go away, due to the potential for abuse?
deleted by creator
So you’re saying we should switch to a .exe domain…