I continue to get this error even though I have run checks through https://www.sslshopper.com/ssl-checker.html show that everything is fine.
My domain is: compasswinesandspirits.com
I should note that I didn’t see the error until recently as I was updating my site through WordPress. Some users have alerted me that they have received the error while others have not.
Can someone point me in the right direction on how to fix this issue?
Thank you!
Hi @clentino
there are some errors and a Grade N ( https://check-your-website.server-daten.de/?q=compasswinesandspirits.com ):
You have two different ipv4-addresses:
| Host | T | IP-Address | is auth. | ∑ Queries | ∑ Timeout |
|---|---|---|---|---|---|
| compasswinesandspirits.com | A | 66.206.32.94 | yes | 1 | 0 |
| A | 184.168.131.241 | yes | 1 | 0 | |
| AAAA | yes | ||||
| www.compasswinesandspirits.com | A | 66.206.32.94 | yes | 1 | 0 |
| AAAA | yes |
But your connections:
| Domainname | Http-Status | redirect | Sec. | G |
|---|---|---|---|---|
| • http://compasswinesandspirits.com/ | ||||
| 66.206.32.94 | 301 | https://compasswinesandspirits.com/ | 0.210 | A |
| • http://compasswinesandspirits.com/ | ||||
| 184.168.131.241 | 301 | http://www.compasswinesandspirits.com | 0.353 | D |
| • http://www.compasswinesandspirits.com | 301 | https://abetterpour.com/ | 1.587 | E |
| • http://www.compasswinesandspirits.com/ | ||||
| 66.206.32.94 | 301 | https://abetterpour.com/ | 2.626 | E |
| • https://compasswinesandspirits.com/ | ||||
| 184.168.131.241 | 301 | http://www.compasswinesandspirits.com | 1.913 | N |
| Certificate error: RemoteCertificateNameMismatch | ||||
| • https://abetterpour.com/ | 200 | 2.830 | I | |
| • https://compasswinesandspirits.com/ | ||||
| 66.206.32.94 | 200 | 4.074 | N | |
| Certificate error: RemoteCertificateChainErrors | ||||
| • https://www.compasswinesandspirits.com/ | ||||
| 66.206.32.94 | 200 | 1.300 | N | |
| Certificate error: RemoteCertificateNameMismatch, RemoteCertificateChainErrors | ||||
There are only wrong certificates, both non-www versions and the www-version.
Did you rechecked the domain via sslchecker? The current result is cached.
It appears that the 2nd IP is from GoDaddy (who seemed to add their IP in and won't allow us to remove it).
I did run the second check on the SSL and see an error:
The certificate is self-signed. Users will receive a warning when accessing this site unless the certificate is manually added as a trusted certificate to their web browser. You can fix this error by buying a trusted SSL certificate.
It's looking like it might be an issue with GoDaddy. I have to call back tomorrow to figure out why.