A cloud administrator configures a new web server for the site https://companyname.com. The administrator installs a wildcard SSL certificate for *.companyname.com. When users attempt to access the…

The wildcard certificate *.companyname.com is valid only for one level of subdomains such as www.companyname.com but explicitly does not cover the bare apex domain companyname.com. When users browse to https://companyname.com, the certificate Common Name does not match the requested hostname, producing a certificate error. The administrator should have obtained a SAN certificate listing both *.companyname.com and companyname.com, or redirected all apex traffic to the www subdomain.

An expired certificate produces an expiration warning tied to the validity period end date, but a newly installed certificate would still be within its validity window and would not trigger an expiration error.

Certificate revocation requires an explicit revocation event recorded in a CRL or returned via OCSP, which does not apply to a freshly configured certificate that has never been compromised.

An unsigned or self-signed certificate would cause a trust-chain error referencing an unknown or untrusted CA, not the hostname mismatch error produced by a wildcard scope limitation.