Hacker News new | past | comments | ask | show | jobs | submit login

That site just made me realise that my surname (kitchen) has now become a .gtld

Someone else clearly figured this out before me though and firstname.surname has gone already.

What would I have done with it though? I've already discovered through having a .cc domain that there are many companies, websites and forms that simply don't accept unexpected domains.

For example, in the past I've spent several days on the phone with a business insurance company trying to get the policy emailed to the company email address and failing because somewhere in their system emails only get routed to 'valid' addresses where 'valid' includes known domain names. The only solution was buying a .com as well to use in such circumstances.




This is a big point. The internet probably has a million systems that have a regexp somewhere listing all the top level domain names that were valid at the time, and half of them aren't maintained and will stay broken forever.

That being said, email validation needs to check for trivial issues (i.e., have you entered a non-empty string? does it have a @ somewhere?) and the proper validation happens if a verification email gets delivered or not.


To be honest, ^.+@.+$ is probably all you need, along with a confirmation email.


A simpler, yet equivalent regex : .@.

Also good: [^@]@[^@]


Addresses can contain multiple @s legally, though, right?


You should get your-email-system-is-broken.com to give out addresses on in those cases.


And they won't accept it because they didn't expect any dashes in the domain name!


Even Mobile Safari doesn't recognize the new gTLDs: typing in dumb.domains takes you to search.

Buying those new domains only makes sense to reserve them, using them really won't make sense for a few years.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: