I note that it is Pale Moon, it uses user agent override function to mask the browser with a more modern one.
I've seen a similar issue with Firefox, a few times, in the past week. The details say: When I view the certificate, it shows it is a Go Daddy certificate for gridserver.com, instead of the Starfield certificate for dedoimedo.com. In all cases, the issue is resolved when I try again.
@Joxx and @stapp, If you close the page and then access it again (not a reload), does it open correctly, with the correct certificate, as is my experience?
Is that with Pale Moon, or Firefox, or both? I have no experience with Pale Moon, but with Firefox, if I close the page and then access it again (not a reload), it opens correctly, with the correct certificate. Anyhow, I suppose the site owner might have a look at mentioned issue.
I guess Mrkvonic may notice this thread, or may be aware of the issue, already, but if you like, you could contact him at Wilders. (Or contact him by e-mail, the mail address is at the Dedoimedo contact page, with you probably cannot access. I could post it here, but I don't know if I'm allowed to. Anyhow, Mrkvonic can be contacted here at Wilders.)
My hosting provider seems to have a problem with SSL termination on one of their loadbalancers. I pointed this out quite a few times, and hopefully they will fix, or I will move to different provider. To resolve, wait a couple of min, then try again, you will land on another Web server node, and it will be fine. And I'm gonna ping them AGAIN. Mrk
Indeed, no termination on the loadbalancer/server node, so the site resolves to the grid instead of the site. Wait a minute, refresh, should be fine. Time to submit a support ticket... Mrk
The hosting provider still seems to have a problem with dedoimedo.com. Today, and the past couple of days, I see the issue more often than last week. Firefox shows the security warning, because of the Go Daddy certificate for gridserver.com, instead of the Starfield certificate for dedoimedo.com. As mentioned, waiting a couple of minutes and trying again resolves the issue, but it takes more time and more attempts than last week.