1: http://en.wikipedia.org/wiki/Extended_Validation_Certificate
Screenshots: https://www.expeditedssl.com/pages/visual-security-browser-s...
Edit: apple-store.com is obviously a real site, so let's say I find something just as legitimately looking as that.
I hear you, though, it's a real pain, but welcome to 2014, we're all learning more about crypto than we ever thought we would have to know, which is what crypto experts have been telling us for 20+ years we would have to do.
Ergo, encrypt everything, and the sensitive stuff can hide in a sea of meaningless traffic.
Anyone that can do a MITM over HTTPS can really easily find the hostname of all theses IP. in fact anyone could find the hostname of theses IP....
Something more interesting: if your site provides something like a code snippet, a MITM could change it.
A lot of download sites serve downloads on http. A MITM could change out the binary. This is especially bad if you're downloading something like a library (example: zeptojs, foundation by zurb)
So yeah. There's a lot of attack vectors. Do your best to minimize it even if you can't think of anything.
Also, really, Apple can't figure out how to get a wildcard cert and properly install it? I had an idea at one point to put together an bot to scan and publicly shame Alexa top whatever sites if they don't do HTTPS properly and consistently. Perhaps I should go back to that idea.