erroneous security warnings
In the last few months, FireFox (accesed from Roamnia, on Firefox an a MacOS 26, both always updated to the latest available final version) has been showing the error: “Be careful. Something doesn’t look right. Firefox spotted a potentially serious security issue with e360.yale.edu. Someone pretending to be the site could try to steal things like credit card info, passwords, or emails. Advanced What makes the site look dangerous? Sites use certificates issued by a certificate authority to prove they’re really who they say they are. Firefox doesn’t trust this site because it looks like the certificate expired on 14/08/2026. What can you do about it? Your device’s clock is set to 22/09/2026. If this is correct, the security issue is probably with the site itself. If it’s wrong, you can change it in your device’s system settings. View the site’s certificate Learn more about troubleshooting time-related errors Error Code: SEC_ERROR_EXPIRED_CERTIFICATE 22 Sept 2026 08:34:11 EEST“ On perfectly innocent sites. Two examples: FAIR.org does not load beyond the initial “Home” page; e360.yale.edu/ shows the warning instead of accessing the homepage. This is annying, possibly wrong and, as any false security warning, potentially dangerous. Please help.
Všetky odpovede (3)
This has nothing to do how innocent sites are, but whether their transport all the way to you stays authentic and nobody touches the content along the way.
The sites appear working correctly, so you're right if someone is annoying you with tampering with the connection it's definitely wrong and potentially dangerous. Either check with the site operators, or your ISP, security solution vendors, national censorship/filtering service etc.
Well it appears it's Mozilla whois annoying me. If it is something / someone else how to find out? For instance, if it is a FireFox Extension, which could it be?
It has no logic of its own to annoy people based on… mood? It's just the integrity of the incoming data that either matches what the sender expects, or not, and the message is the result of that.
You can restart intro Troubleshoot Mode (from Help menu) to eliminate any addon interference, but that's not the usual culprit.
What however can influence routing and the hosts/datacenters used is "DNS over HTTPS" feature — check for its options in Settings, and switch them around, enabling, disabling, changing providers — to see how the responses look like via different domain resolution.