3 ms·
Do we know yet how browsers will be treating these tlds? Eg if I type "diamonds" into the Chrome omnibar will it take me to a Google search for "diamonds" or to
by yeldarb 13y ago
Do we know yet how browsers will be treating these tlds? Eg if I type "diamonds" into the Chrome omnibar will it take me to a Google search for "diamonds" or to http://diamonds http://diamonds
- dsl 13y agoICANN made a decision late in the game to not allow "dotless" domains, i.e. making "diamonds" resolve to something the TLD owner decides. This crushed the business model of most of the new TLD operators, so don't expect them to be around in a few years.
- molecule 13y agofollowing up, ICANN's announcement and reasoning: http://www.icann.org/en/news/announcements/announcement-30aug13-en.htm http://www.icann.org/en/news/announcements/announcement-30au...
- sp332 13y agoThe most prominent example is the Simple Mail Transfer Protocol (SMTP) to deliver electronic mail. It requires at least two labels in the FQDN of a mail address. Thus standard-compliant mail servers would reject emails to addresses such as user@brand. Do most mail servers follow this rule?
- nwh 13y agoI remember some ccTLD had A records a while back (bs. was one), but they lacked MX. I think it would just cause lots of form validation errors if that suddenly changed, not to mention the confusion you'd cause with people expecting a suffix. I cause enough issues with not having a ".com" on my email address, people love adding a .com.
- 0x0 13y agoInteresting that the fully-qualified (with a dot suffix) URL http://nic.diamonds./ http://nic.diamonds./ brings up a 404...