tldgeek

Q: new gTLDs do not function correctly in Safari?

For those of you who don't know, there is a big change going on with internet domain names (website addresses). Instead of just a few generic Top Level Domains (TLDs) like .com, .net, .org there will be hundreds and eventually over a thousand of new TLDs like .tips, .guru, .photography. etc This will help with finding unique and memorable names, and is a groundbreaking change in the way we will enter addresses into the address bar of browsers. The popular names on the existing .com, .net, etc have been flooded for years now and it has been near impossible for awhile now to find a decent domain name to use for your website. The good news is that the new TLDs will change all of this (at least until they start filling up like the original gTLDs) giving website developers a chance to utilize unique and easy to remember names once again on the internet.

 

Ok so the first wave of these new generic TLDs (gTLDs) have started being released to general availability since January of this year, but the problem is they are not working in Safari! Obviously this is a big deal since these extensions are not  going anywhere and they need to be functional in Safari especially  since this is one of the most widely used web browsers today. I have personally registered a few of the new gTLDs and they do not function in Safari as they are  supposed to - instead they redirect to a google search! It should be a  simple fix for apple to implement that anything following a dot (.)  should be treated as a gTLD. So when someone enters www.xyz.tips or xyz.tips it will direct the user to the http://www.xyz.tips website and not a google search. I don't know of any other reason  (other than entering an ip address) someone would be entering a dot or  period (.) into the address bar other than to specify a domain name so  this should be something that apple can implement quickly to insure  users can access websites utilizing the new TLDs. The logic would be  pretty simple to allow a qualified IP address string to still work as  usual while allowing pretty much anything else following a dot (.) to be  treated as a gTLD. Has anyone else tried contacting apple engineers  about this issue and what responses have you received? I thought for  sure Apple would already have been on top of this in time for the new  gTLD launches but I was disappointed to see the weeks come and go with  no solution to this problem! Please help Apple!

 

FYI entering http://www.xyz.tips or www.xyz.tips/ will function properly in Safari, the problem is that most people don't type http or add a slash at the end of a website address when typing it in the address bar so we need to have xyz.tips and www.xyz.tips working in Safari just like xyz.com or www.xyz.com would fuction in Safari.

 

Thanks for your feedback guys. Maybe someone who has a developer account can pass this along to the Apple engineers?

 

There is another forum discussing this same issue on MacRumors:

 

http://forums.macrumors.com/showthread.php?p=18927514#post18927514

Posted on Mar 26, 2014 12:10 PM

Close

Q: new gTLDs do not function correctly in Safari?

  • All replies
  • Helpful answers

  • by barnhart.photography,

    barnhart.photography barnhart.photography Mar 27, 2014 5:39 AM in response to tldgeek
    Level 1 (0 points)
    Mar 27, 2014 5:39 AM in response to tldgeek

    Glad this issue is being acknowledged!  I just purchased barnhart.photography and am having the same issues.  I want to get my new business cards but the fact is unless I put that http:// on the card (which most people still wont type) the site will not work, and then the google search will find other photographers with the name barnhart who's sites are higher on the search. 

     

    SO PLEASE HELP US AND MAKE SOME CHANGES TO ADAPT TO THE NEW TLD'S MUCH APPRECIATED!

  • by Jörg Pyrlik,

    Jörg Pyrlik Jörg Pyrlik Mar 28, 2014 6:52 AM in response to tldgeek
    Level 1 (25 points)
    Mar 28, 2014 6:52 AM in response to tldgeek

    hold down the Command-key and "Google Search" changes to "Go to Site" and does just that.

  • by tldgeek,

    tldgeek tldgeek Mar 28, 2014 9:43 AM in response to Jörg Pyrlik
    Level 1 (0 points)
    Mar 28, 2014 9:43 AM in response to Jörg Pyrlik

    Thanks for the reply Jorg, unfortunately, that doesn't solve our issue. Of course we can get to our sites by typing the full address with http://www. or adding a slash at the end or by using the Command - Key like you stated (not sure if this would even work on ipad / iphone) but the problem is most people trying to visit the new gTLD websites will not be typing the fully qualified domain name or holding control when they enter the domain name so they will still get the google search. The problem is about allowing the browser to recognize the new gTLDs like they would a usual TLD like .com and sending users looking for a particular website to that website and not a google search. Apple needs to make some modifications to the logic used to identify a TLD so the new gTLDs will work like they should. Like I said earlier pretty much everything following a dot (.) should be treated as a TLD unless it is a qualified IP address. When someone enters something in the address bar with a (.) it now more than ever needs to be recognized as a domain name or IP address and not a google search.

     

    I have sent a Safari bug report to Apple via the feeback form below and sugest anyone else having this problem do the same - the more demand apple has for this fix, the sooner it will happen!

     

    You can report the bug to Apple about the new gTLD domains not working properly here:

     

    http://www.apple.com/feedback/safari.html

  • by tldgeek,

    tldgeek tldgeek Apr 18, 2014 12:27 PM in response to tldgeek
    Level 1 (0 points)
    Apr 18, 2014 12:27 PM in response to tldgeek

    Anyone get any feedback from Apple on this issue yet or submit a bug report as I suggested above?

     

    Hopefully Apple will fix this issue soon!!

  • by James Smutek,

    James Smutek James Smutek Jul 3, 2014 1:34 AM in response to tldgeek
    Level 1 (145 points)
    Jul 3, 2014 1:34 AM in response to tldgeek

    Chiming in. I just bought some new TLD's and stumbled across this issue when I checked mobile Safari while starting setup on one of my new blogs.

     

    Pretty frustrating. The command key thing is a good tip, now if I can just get that info out via direct mail to any potential viewers....

  • by James Smutek,

    James Smutek James Smutek Jul 4, 2014 5:09 PM in response to James Smutek
    Level 1 (145 points)
    Jul 4, 2014 5:09 PM in response to James Smutek

    Seems to be resolved in 7.1.2, yay!

  • by John Baughman,

    John Baughman John Baughman Oct 3, 2014 8:07 PM in response to James Smutek
    Level 1 (41 points)
    Mac OS X
    Oct 3, 2014 8:07 PM in response to James Smutek

    That's great.  But how do I get Safari 7.1.2?

    John

  • by Tec Team,

    Tec Team Tec Team Aug 22, 2015 1:39 AM in response to John Baughman
    Level 1 (0 points)
    Aug 22, 2015 1:39 AM in response to John Baughman

    Im on 8.0.7 still an issue with new .team domain

  • by billdoesdev,

    billdoesdev billdoesdev Sep 26, 2016 5:12 PM in response to Tec Team
    Level 1 (8 points)
    Safari
    Sep 26, 2016 5:12 PM in response to Tec Team

    Hi,

     

    Been lurking on this thread (and others like it) for a while now, and while it appears from very limited testing that the issue is resolved in Safari on IOS10, has anyone been able to confirm this?

     

    I would love to know definitively that the issue is resolved. I haven't seen anything in Safari release notes addressing the bug. I'm still loathe to move forward with major business decisions where this bug may impact the user experience.

     

    I would very much appreciate someone smarter than me (or Apple directly!) weighing in on the issue as this is a longstanding bug!