You can buy one, just use another email. You are welcome!
>How can a normal internet user figure this out? If I wasn't a web developer I would have given up.
A normal internet user will have a gmail or outlook mail address, not a .pizza one.
>How can a normal internet user figure this out? If I wasn't a web developer I would have given up.
A normal internet user will have a gmail or outlook mail address, not a .pizza one.
A normal internet user may also be in a country where ".com" is not the main TLD.
Granted, .pizza is unusual, but there is no valid excuse for not supporting it, and systems that fail to use it likely also fail other completely "normal" email addresses due to other invalid email validation like assuming a TLD has one dot, that an email address has a certain arbitrary max length, or because they failed to enumerate even common TLDs.
The only proper way to validate an email is to send an email to it.
In my experience ccTLDs are always supported (I've used some funky ones over the years like .sh and .dj), while newer general ones (like .online) are sometimes rejected. My "solution" is to keep a ccTLD to use as an email alias.
- .香港 is a valid ccTLD (for Hong Kong)
- .xn--j6w193g is a valid ccTLD (punycode transliteration of the above)
Regardless, the issue is in the validation end here. There's public lists with valid TLD's and any email address validation should ensure valid email addresses are let through.
A normal user does not know about common unsafe assumptions in every aspect of programming and IT integration.
Once the option to get foo.pizza exists, absolutely a ton of normal users take it, just like they do everything else.
If a "is this real" filter is required, they should write a script to check for new TLDs daily.