IT.COM

domains Afternic introduced new Buy-Now landing page

Spaceship Spaceship
Watch

Ntmt

Top Member
Impact
2,642
upload_2021-4-27_18-43-26.png

NS5.AFTERNIC.COM
NS6.AFTERNIC.COM
 
17
•••
The views expressed on this page by users and staff are their own, not those of NamePros.
Wow. This would be a huge waste of traffic/sales.

Not just for the investors, but for GD/Afternic, as they lose the 20% of the cut. You'd think they'd focus on implementing this simple pre-requisite feature since browsers have started strictly requiring this couple of years ago, yet still not done...

Agree. Godaddy never ceases to amaze me.

It's 2021.

Godaddy is a well-known CA authority, member of the CA/Browser Forum, and their G2 Root Certs are present in our browsers. With the complete redesign and testing of the new 3/4 and 5/6 landers, you would expect TLS to be part of the new landers. But it's not.
 
Last edited:
2
•••
@Joe Styler @Paul Nicks

New bug of GD/Afternic integration.

I select names in my GD interface to list then click list for sale as I have done many times before and since today I get "you have no domains to list" error. Repeated few times (which is a hassle in itself, as I need to re-sort, get to the pages I need, find the names, select those after struggling with another bug that doesn't show listed status - reported in GD bugs thread with zero reaction, btw - and then get this error) and the same happens every time.

Show attachment 191132

Thank you, I'll fwd to the product team
 
2
•••
you would expect TLS to be part of the new landers. But it's not.

Although the http:// itself is not secure, but once you enter a domain it goes to a secure Godaddy page.

Perhaps they have left the initial entry point unsecure on purpose in order to make it easier to get to the Landers from all different places around the World (just guessing).

We got to assume that Godaddy has designed their system to produce the maximum number of sales and as such there might be some justification for certain things that don't look right on the surface.

Perhaps @Paul Nicks or @Joe Styler can chime in to address this issue better,

IMO
 
Last edited:
0
•••
Thank you, I'll fwd to the product team

There might be a limit on the number of domains that you can do at the same time,

I have noticed that when I want to forward a bunch of domains to one of my websites it only lets me do 10 at a time (otherwise it gives an error message when I click on "save").

IMO
 
Last edited:
0
•••
Although the http:// itself is not secure, but once you enter a domain it goes to a secure Godaddy page.

Perhaps they have left the initial entry point unsecure on purpose in order to make it easier to get to the Landers from all different places around the World (just guessing).

We got to assume that Godaddy has designed their system to produce the maximum number of sales and as such there might be some justification for certain things that don't look right on the surface.

Perhaps @Paul Nicks or @Joe Styler can chime in to address this issue better,

IMO

The problem is that this is not about people entering a domain manually in their browser. This is about already existing https backlinks on websites, and indexed https links in Google. All these https links don't work now, simple as that. Read what @Recons.Com wrote about this as well.

You're assuming a lot here about Godaddy's intentions, but in case of Afternic with their bare naked services and ancient domain management interface, I would not assume things too fast. The best is to let Afternic answer first, and then have them fix it. I'm still trying the new ns5/ns6 Afternic landers for the majority of my domains, and since I noticed this, I think about switching back to my old landers. For 20% commission on a lander, I expect this to work.
 
Last edited:
5
•••
The problem is that this is not about people entering a domain manually in their browser. This is about already existing https backlinks on websites, and indexed https links in Google. All these https links don't work now, simple as that. Read what @Recons.Com wrote about this as well.

You're assuming a lot here about Godaddy's intentions, but in case of Afternic with their bare naked services and ancient domain management interface, I would not assume things too fast. The best is to let Afternic answer first, and then have them fix it. I'm still trying the new ns5/ns6 Afternic landers for the majority of my domains, and since I noticed this, I think about switching back to my old landers. For 20% commission on a lander, I expect this to work.

Thanks. This is unbelievable, honestly. With the size of my portfolio, even with 0.1%-0.2% loss in STR, this would mean loss of 10-20 sales a year, which would translate into tens of thousands $ lost for me and Afternic. For the whole Afternic platform, the annual loss is definitely in millions $.

@Paul Nicks could you guys focus on fixing this urgently? The simplest solution is just forward the https:// to http:// if you have issues with the certificates or need time to handle this.

Just today sold a name that has an Afternic lander via ... DomainAgents where it is not even listed. This easily could have been due to the fact that the buyer landed on a dead page and sought out a broker. I am sure there are bunch of cases where buyer just moves on assuming a name is not for sale.
 
4
•••
@Joe Styler @Paul Nicks

New bug of GD/Afternic integration.

I select names in my GD interface to list then click list for sale as I have done many times before and since today I get "you have no domains to list" error. Repeated few times (which is a hassle in itself, as I need to re-sort, get to the pages I need, find the names, select those after struggling with another bug that doesn't show listed status - reported in GD bugs thread with zero reaction, btw - and then get this error) and the same happens every time.

Show attachment 191132
Thanks. I let the person in charge of that know and also about the https vs http above in the thread.
 
3
•••
Wow. This would be a huge waste of traffic/sales.

Not just for the investors, but for GD/Afternic, as they lose the 20% of the cut. You'd think they'd focus on implementing this simple pre-requisite feature since browsers have started strictly requiring this couple of years ago, yet still not done...
So I simply tested this thing further, just to find that the https issue occurs with both ns3 ns4 as well as the ns5 ns6 landers.
 
5
•••
That landing page design appears to be good and eye-catching, but I haven't had the opportunity to check with a point to domain.
 
0
•••
Thanks. I let the person in charge of that know and also about the https vs http above in the thread.

I was wondering what is the timeline on this?

For the whole huge IT team it shouldn't be problem to make sure that the https:// works as normal?

Supposedly, the landing pages has gone through all the beta testing and have been launched. How can a tech company launch something that works only on INSECURE protocol and DOESN'T support AT ALL a secure protocol?

Again, every day this protocol is not working Afternic/Godaddy is losing tens of thousands of $ given 20 million+ domains listed.

Again, I have 10000+ domains (doubling every year) with GD/Afternic and I am using this landers and if this cannot be fixed, I will send my business elsewhere, both as registrar and the landing service.

It is annoying that bugs reported years ago are still there and if there is any change, it is only towards worse, never towards fixing anything.


timeout1.PNG
 
Last edited:
5
•••
Wow. This would be a huge waste of traffic/sales.

Not just for the investors, but for GD/Afternic, as they lose the 20% of the cut. You'd think they'd focus on implementing this simple pre-requisite feature since browsers have started strictly requiring this couple of years ago, yet still not done...

In addition to what you've already said earlier in this thread about browsers upgrading the connection automatically to https, all domains with HSTS Preload enabled (this includes the complete .app TLD, whether developed domains or not) will not work without having this configured correctly at Afternic/Godaddy.
 
Last edited:
2
•••
So I simply tested this thing further, just to find that the https issue occurs with both ns3 ns4 as well as the ns5 ns6 landers.
Thanks for the heads up. I made sure the person in charge of that knows.
 
Last edited:
2
•••
Any way to make the domain name appear as DomainName.com instead of domainname.com?
 
1
•••
@Joe Styler please pay attention to the SSL problem that @Recons.Com and others mentioned, I switched recently to Afternic Bin landers and I confirm that there is a problem. Here what is happening:
  • When you enter domain name in browser for first time it opens without problem
  • If you later type the same domain in browser the autocomplete will format the url as https://domainName
  • Then the domain fails to resolve
  • This only happened for me with Chrome browser not Firefox

To be honest this is a killer bug, now I am considering switching back to Dan until this problem is resolved.
 
4
•••
@Joe Styler please pay attention to the SSL problem that @Recons.Com and others mentioned, I switched recently to Afternic Bin landers and I confirm that there is a problem. Here what is happening:
  • When you enter domain name in browser for first time it opens without problem
  • If you later type the same domain in browser the autocomplete will format the url as
  • Then the domain fails to resolve
  • This only happened for me with Chrome browser not Firefox

To be honest this is a killer bug, now I am considering switching back to Dan until this problem is resolved.
Has this been resolved?
 
0
•••
Still n
Wow. This would be a huge waste of traffic/sales.

Not just for the investors, but for GD/Afternic, as they lose the 20% of the cut. You'd think they'd focus on implementing this simple pre-requisite feature since browsers have started strictly requiring this couple of years ago, yet still not done...

Still not fixed. Don't they sell SSL certificates lol? This is ridiculous
 
2
•••
1
•••
Still n


Still not fixed. Don't they sell SSL certificates lol? This is ridiculous

I removed all my domains from Afternic BIN and switched back to Dan landers, until this problem is fixed!
 
2
•••
Big things coming to afternic in 2021
@joejoestyler said so. Unresponsive control panel, insecure landers. Daddy loves those traffic stats. And only 20% .comish
 
1
•••
I removed all my domains from Afternic BIN and switched back to Dan landers, until this problem is fixed!

Seems like the way to go at this point we can't expect them to ever fix this. I'll be switching to Bodis. At least they can handle https lol

Domains parked with Uniregistry don't resolve with https either. At least the ones using buy.internettraffic.om name servers..
 
1
•••
@Joe Styler Can you give us a status update on the TLS issues? Appreciate it.
 
1
•••
I just took a huge portion of my landers from Afternic and moved over to DAN.
 
1
•••
@Joe Styler please pay attention to the SSL problem that @Recons.Com and others mentioned, I switched recently to Afternic Bin landers and I confirm that there is a problem. Here what is happening:
  • When you enter domain name in browser for first time it opens without problem
  • If you later type the same domain in browser the autocomplete will format the url as https://domainName
  • Then the domain fails to resolve
  • This only happened for me with Chrome browser not Firefox

To be honest this is a killer bug, now I am considering switching back to Dan until this problem is resolved.


In Firefox when you type in KEYWORD and click ctrl+enter the browser adds .com to the end of the KEYWORD and https://www. before the keyword.

That's a type in.

And since Afternic cannot handle https, the page does not resolve so that's basically blackholing type in traffic
 
2
•••
1
•••
no new news. The Afternic team is aware of it but I do not have any ETA.

Thank you. Another marketplace fixed this within one week after reporting the same issue. And they are not such a huge player in the TLS certificate field as Godaddy is. In fact, they don't sell any certificates at all.
 
Last edited:
2
•••
  • The sidebar remains visible by scrolling at a speed relative to the page’s height.
Back