What would cause SSL Certificate errors across all installed OSX browsers but Firefox?
<p>Every attempt to connect to Wired.com is met with a certificate error.</p>
<p><a href="https://i.stack.imgur.com/0nxL6.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/0nxL6.png" alt="The Cert Error" /></a></p>
<p>I've checked the usual suspects and even done things that probably have nothing to do with it.
Browsers tried</p>
<pre><code>Safari=failed
Chrome=failed
Brave=failed
Firefox=success
</code></pre>
<ul>
<li>Verified no Chrome extensions interfering (incognito w/ no approved incog extensions)</li>
<li>Same with Safari.</li>
<li>Flushed DNS</li>
<li>Rebooted</li>
<li>Time settings obv correct</li>
</ul>
<p>I started to get paranoid thinking that something is hijacking my connection, but the only active ports I've got open and connected are... well, supposed to be open. And then the fact that it works with Firefox is even stranger. Firefox is my proxy browser, but it works via proxy w/out.</p>
<p>This is a recently upgraded Sierra machine. I'm not an avid wired reader, so I couldn't tell you if it was happening previously, but I can say I've got 4 other mac test machines here and none of them are experiencing the same issue.</p>
<p>Sierra vs Capitan doesn't make a difference. And this is now going on a 2 week issue. Wired appears to be literally the only site effected. At this point it's more a curiosity at getting to the bottom of this than anything else, since it does appear to be something isolated to this machine.</p>
<p>Also, I think we can rule out a CDN issue. As all my other machines are connecting from this same wanIP.</p>
<p>Man, just absolutely any suggestions for more internals I could go digging through to try and get to the bottom of this would be oh so greatly appreciated. Because I've about relegated myself to keyboard head smashing.</p>