Live data from Hacker News

Watch out: ɢoogle.com isn’t the same as Google.com

thenextweb.com

11–20 of 136 posts

Re: Watch out: ɢoogle.com isn’t the same as Google.com

#11

Web browsers should have an option to show non-ascii chars in urls in red.

This would be a great solution. Allowing unicode characters in domain names is just inviting trouble. I understand that people with non-Latin scripts want domain names in their own language and alphabet, but there are way too many unicode characters that will confuse people about legitimate-looking domain names.

Showing non-ascii in red would be an easy solution for everybody.

Re: Watch out: ɢoogle.com isn’t the same as Google.com

#12
post #9

It was a pretty nice surprise that when sending this URL in Slack it was automatically converted to `xn--oogle-wmc.com`.

The fact that we need application-specific security measures against this just emphasizes the problem. There are a lot of applications.

Re: Watch out: ɢoogle.com isn’t the same as Google.com

#13
post #8

I thought there were supposed to be registry rules preventing similar looking names to be registered as an idna. I guess not.

I believe they aren't preventative measures, but responsive. So if Google contacts ICANN, then they may do something about it

Some registries do this automatically. Some don't.

Re: Watch out: ɢoogle.com isn’t the same as Google.com

#14
post #11

Web browsers should have an option to show non-ascii chars in urls in red.

This would be a great solution. Allowing unicode characters in domain names is just inviting trouble. I understand that people with non-Latin scripts want domain names in their own language and alphabet, but there are way too many unicode characters that will confuse people about legitimate-looking domain names. Showing non-ascii in red would be an easy solution for everybody.

> people with non-Latin scripts want domain names in their own language

I've yet to see a useful site with Cyrillic domain. Theoretically it sounds good, but practically everyone still uses Latin domains. May be it'll change with time.

Re: Watch out: ɢoogle.com isn’t the same as Google.com

#18
post #7

Web browsers should have an option to show non-ascii chars in urls in red.

They should already only show punycode for characters inside your locale. 'ɢ' is obviously an exception since (I imagine) it's considered to be in your locale, but maybe it shouldn't be.

That would be very confusing for multilingual users. Just because my OS is configured to use a certain locale, doesn't mean I don't read text in scripts not considered part of it.

Re: Watch out: ɢoogle.com isn’t the same as Google.com

#20

Some time ago I registered http://www.goolge.io/ . Still haven't done anything with it, I guess at some point I'll just redirect it to duckduckgo. [EDIT: now it's redirected to duckduckgo.] This can of course be used in a malicious way. I thought about rebuilding the homepage of the bank Credit Suisse on www.credit-siusse.ch, but that's probably illegal.

I registered http://www.4ppl3.com a while back. No potential for abuse really, but I just thought it was fun to have a l33t-speak version of the domain name of one of the world's most litigious companies.

That said, I haven't done anything with it, and I'm not a domain squatter, so if anyone wants it I can hook you up!

Post reply on HN