I was involved in setting up .name back in 2001. We spent ages contacting people with validation rules based on the old set of TLDs. Given that was the first expansion of the gTLD space in a long time, it wasn't so unreasonable then. But it's just astounding that it's still and issue 20 years later.
sometimes you get regressions too. Kaiser Permanente invalidated my email address earlier this year.
Someone found a sleeper regexp on Stack Overflow...
I managed to buy firstname.dev a while ago and this was one of my fears of using it as my email address. I ended up switching to a .com one just to avoid any issues. I certainly don't want government services emails not to work just because maybe they didn't account for .dev TLD
I have the same issue. I use sparr.email and it fails validation on a few critical websites, namely my online utilities account (seattle public utilities) and payroll processor (ADP).
yeah, I routinely use .email and .cloud and it's so annoying when the occasional site goes "THAT IS NOT AN EMAIL ADDRESS !!111!1 YOU HAXXXOR!".
and the regex you provide doesn't even account for unicode..
The domain in question being david.kitchen, so an email may be [email protected]
The issue I encounter more than any other is trivial: Most sites still have a tld validation that only accepts domains that end in net|com|org and some other small list of accepted suffixes such as co.uk
The list of TLDs is constantly expanding https://newgtlds.icann.org/en/program-status/sunrise-claims-... so even `[a-z0-9.-]+@[a-z0-9.-]+\.[a-z0-9]+` would be better than what I see in the wild.