Support for more verification options on unicode domains
I own an emoji unicode domain, https://⚪🐯.ws. While I can start the verification process, I'm not able to complete verification via email as every email is considered disallowed. DNS TXT verification results in "Catastrophic failure!" (500), as does meta tag validation. File upload results in "No response from domain".
Interestingly, converting it to Punycode (https://xn--f8h8099n.ws) also doesn't work.
Edit: Apologies, the TXT record method works when the domain is converted to unicode. I don't believe anything else does though!
Connor Bell
shared this idea
-
Haha, no rush! Just thought it was interesting mainly. I think not supporting unicode domains is probably fine for the most part, but I was very curious why Punycode wasn't working for the other verification methods aside from TXT. Feel free to drop me emails, and thanks for looking into it so quickly.
-
It looks like the native browser email address validator is rejecting the emoji version. Try submitting this: https://jsfiddle.net/troyhunt/u10mpzef/
That's at least part of the problem. There's also then a problem with sending a verification email to one of the 4 pre-loaded ones, but for some reason that's only happening in the production environment and not for me locally (I'm wondering if there's a culture difference in the string comparison).
This is going to require some time so am going to leave it here pending for now, sorry there wasn't a quick fix.
-
This *should* be ok, let me delve into a bit, apologies if you get some emails from the system in the process...
