GoDaddy domain forwarding - not working as it should...

[tonyk2000]

If you are using domain forwarding for GoDaddy-regged domain, please check the following. Their forwarding server now responds to httpS requests, but fails to provide a valid SSL certificate. Resultingly, a browser which enforces SSL (Google Chrome for example) shows ssl error if you try to visit the domain in question. Moreover, google search engine in their wisdom still adds httpS to such a domain in search results (even though there is no valid certificate), which make impossible for any human to visit the website (forwarded domain) if found via google search...

How to reproduce:

Add domain forwarding to any GD-regged domain, and try to visit this domain via httpS.

So, GoDaddy should either:

a) stop responding to httpS requests on forwarding server(s) at all (which was always the case, until recently)

OR

b) start generating valid SSL certificates for domains which are using the forwarding service. LetsEncrypt would be fine. Also, GoDaddy itself is a certification authority...

@Joe Styler
@Paul Nicks

 

[tonyk2000]

Proof. Not mine, no affiliation. http request works and forwards to another website, but:
(domain in question resolves to 184.168.131.241 - one of GD forwarding IPs)

 

[Paul Nicks]

Thx, will fwd to the appropriate dev team.