Web browsers should have an option to show non-ascii chars in urls in red.
Chinese character domains would be shown in red letters. I think it's a good choice of color. :)
Watch out: ɢoogle.com isn’t the same as Google.com
21–30 of 136 posts
Re: Watch out: ɢoogle.com isn’t the same as Google.com
#22For me it just redirects to http://money.get.away.get.a.good.job.with.jack.ilovevitaly.com The actual domain is http://xn--oogle-wmc.com/ Which is an Internationalized domain name[1] in punycode transcription [1] https://en.wikipedia.org/wiki/Internationalized_domain_name The G in question here is https://en.wiktionary.org/wiki/%C9%A2 OR http://charcod.es/#%C9%A2/610
>ilovevitaly.com This Vitaly guy… I got tons of referral header spam (that shows up in e.g. Google Analytics) for all sorts of social media buttons and EU cookie law scare tactic sites. And then there was Vitaly who just spammed me with ilovevitaly.com, which if I recall correctly actually was a site about himself at the time.
Wow what an odd site
Re: Watch out: ɢoogle.com isn’t the same as Google.com
#23What about Googlé.com and infinite number of other variations?
Why is everyone thinking so small? What about https://www.goоgle.com ? Or how about the word "gullible" isn't in the dictionary? http://www.dictionary.com/browse/gulliblе
Would it be possible to register a .xn--cm-fmc TLD and have a .cоm registry all of your own?
Re: Watch out: ɢoogle.com isn’t the same as Google.com
#24Re: Watch out: ɢoogle.com isn’t the same as Google.com
#25It was a pretty nice surprise that when sending this URL in Slack it was automatically converted to `xn--oogle-wmc.com`.
Slack is not doing anything. It's Google chrome filling up your clipboard with the "extended" version of the url.
But when I paste it in the Slack message box it shows the ɢoogle.com version.
Re: Watch out: ɢoogle.com isn’t the same as Google.com
#26Some 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.
That looks a lot like the sort of trademark use that authorities have deemed infringing, I'd expect the registrar to "recover" that unless you've got a clear explanation (like Goolge is your name, even then ... (remember Nissan, Mike Rowe, etc.)).
Re: Watch out: ɢoogle.com isn’t the same as Google.com
#27Some 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.
Most browsers should forcibly transcribe this to Punycode[1]:
https://www.𝙿𝙰𝚈𝙿𝙰𝙻.com/
No 301 redirects or anything, the browser just treats it like ASCII, which it is clearly not, it actually happens to be Fullwidth:
https://en.wikipedia.org/wiki/Fullwidth_form
Serious phishing opportunity if you ask me!
Re: Watch out: ɢoogle.com isn’t the same as Google.com
#28I thought there were supposed to be registry rules preventing similar looking names to be registered as an idna. I guess not.
Yes and no. One of the problems is that Verisign's handling of IDNs wasn't exactly the best conceived, which left them with silly IDN codepoint tables like this: https://www.iana.org/domains/idn-tables/tables/com_latn_1.2....
Re: Watch out: ɢoogle.com isn’t the same as Google.com
#29Web browsers should have an option to show non-ascii chars in urls in red.
It should display each code page with a different color. That would make the schema useful for non-english speaking people too.
Re: Watch out: ɢoogle.com isn’t the same as Google.com
#30Web 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.
Wouldn't a good compromise to be to somehow highlight any characters that are outside of ASCII and the character set of the language you are using in the browser/os?