Hopefully this .Internal domain takes off and becomes generally recognized as the only correct non-routable domain we all use. Otherwise it’s just the latest addition to the list of possible TLDs and confusion continues.
That one is absolutely abhorrent because I know as a fact my parents would easily fall for a .zip domain leading to a virus infested site thinking it’s actually them getting a zip file because they don’t know better. At least the first few times they’d fall for it.
The last time I talked to my mom about a zip file, she didn’t even fully understand what a zip file is. That’s how I know my mom would get confused.
My dad, he’s better since he has and uses a laptop, so he knows more than my mom, but he’s still not the brightest when he has CCleaner and malwarebytes installed simultaneously on his laptop. Hell, back around 2018-2019 he was extremely stubborn about me trying to fix the family computer that had a password that I didn’t know on it. I just wanted to uninstall some bad programs (don’t remember which ones) and my dad was getting super anal about it. I have no doubt if he did accidentally click on a .zip web link, we’d never know because he’d be too stubborn to admit it.
It’s such a shitty situation. ICANN is not going to sell .home or .corp as they found a crapton of traffic when they checked for it, but IETF never finished an RFC for them - however people easily stumble into the draft RFC that lists what they were thinking of, and assume stuff like .lan is good to go too. They’re safe by ICANN policy, but unsanctioned.
.home.arpa is safe, per RFC, but user unfriendly to normal people. There are a few others but none a corporation would realistically use. I’ve used . internal for lab testing stuff for ages, so this is extra good news for me I guess.
Really I wish they’d have just reserved the most common ones rather than getting caught in some bureaucratic black hole.
And .home.
Hopefully this .Internal domain takes off and becomes generally recognized as the only correct non-routable domain we all use. Otherwise it’s just the latest addition to the list of possible TLDs and confusion continues.
I’m just waiting for .exe
.zip is already a thing
https://www.malwarebytes.com/blog/news/2023/05/zip-domains
That one is absolutely abhorrent because I know as a fact my parents would easily fall for a .zip domain leading to a virus infested site thinking it’s actually them getting a zip file because they don’t know better. At least the first few times they’d fall for it.
How would you know?
Because they’re his parents, not yours
The last time I talked to my mom about a zip file, she didn’t even fully understand what a zip file is. That’s how I know my mom would get confused.
My dad, he’s better since he has and uses a laptop, so he knows more than my mom, but he’s still not the brightest when he has CCleaner and malwarebytes installed simultaneously on his laptop. Hell, back around 2018-2019 he was extremely stubborn about me trying to fix the family computer that had a password that I didn’t know on it. I just wanted to uninstall some bad programs (don’t remember which ones) and my dad was getting super anal about it. I have no doubt if he did accidentally click on a .zip web link, we’d never know because he’d be too stubborn to admit it.
It’s such a shitty situation. ICANN is not going to sell .home or .corp as they found a crapton of traffic when they checked for it, but IETF never finished an RFC for them - however people easily stumble into the draft RFC that lists what they were thinking of, and assume stuff like .lan is good to go too. They’re safe by ICANN policy, but unsanctioned.
.home.arpa is safe, per RFC, but user unfriendly to normal people. There are a few others but none a corporation would realistically use. I’ve used . internal for lab testing stuff for ages, so this is extra good news for me I guess.
Really I wish they’d have just reserved the most common ones rather than getting caught in some bureaucratic black hole.