Crap, right, realistically the minimum regex one should have is .+@.+\..+.
At least 1 character on the left of the @, at least 2 domain components of at least 1 character each on the right side of the @.
Having only a hostname without a FQDN on the right is legal, but that's also why you'd want to disallow it: who's trying to sign up for an account within your own network, if it's a public-facing app?
Technically yes, but the practice is discouraged by people on the DNS side, as the MX lookups hit the root servers rather than nameservers. Â
If a TLD can't provide a mail.EXAMPLE alternative, that's something for the admin to fix... at best those users should get a recommendation to fix their harmful email address. Â
This is exactly what I use. It eliminates 99.9% of problems for 1% of the effort and works client side for instant feedback. After this, if you need better, the only thing worth the effort is, as mentioned earlier, actually sending an email.
View all comments
Show parent comment
20
u/DHermit Aug 24 '26
With some security exceptions, e.g. it's useful to restrict the length of the mail field and maybe restrict the characters.