Oh, I see - the loading screen. Yeah, I got that, too - didn't even think about it. At first, I thought it might be me, so I checked with a VM machine using Firefox instead of Chrome "with some urgency." Heh, sorry about the scare.

DNS attack shouldn't be able to adequately forge SSL certificate in most reasonable scenarios (though it's happened outside cert keys just being stolen/compromised - google comodo attack, allegedly done by a single guy). DNS attacker who was really specific (targeting crypto users, maybe) would probably just self-sign certificates for fake crypto websites and hope you click through the browser warnings (so to answer your question - no - or at least "no, I don't think so."). Idunno SSL cert mechanics well enough to fully answer you, though.