Good catch! The addition is for the new .google TLD. Looks like the Chromium source code had some "protection" against this, at least at one point in time: htt

Good catch! The addition is for the new .google TLD. Looks like the Chromium source code had some "protection" against this, at least at one point in time: http://security.stackexchange.com/questions/6873/can-a-wildcard-ssl-certificate-be-issued-for-a-second-level-domain http://security.stackexchange.com/questions/6873/can-a-wildc... It appears that the specification (RFC 2818?) doesn't specify what is acceptable with regards to allowed wildcard certificates - leaving the various implementations to decide what is "too risky" for themselves.