For what it's worth, the warning isn't appearing in Firefox in multiple test machines either. It certainly is appearing in Chrome, and as you note, it's scary looking. Fortunately, it DOES have a bypass link.

For now, we're just hoping they'll get it cleaned up by the AM. If not, we'll have to consider more drastic steps (a very first step being user-agent based warnings on our side of things).

For the future, we'll certainly want to see a smarter separation of domains, to avoid this very issue.