Wildcard certificate

wikipedia:Wildcard certificates

Limitations

• Only a single level of subdomain matching is supported in accordance with Template:IETF RFC.

• wikipedia:Wildcard certificates do not valid for *.example.com or www.example.com and example.com. If you need a cert to work for example.com and www.example.com, you need to request a certificate with subjectAltNames so that you have "example.com" and "*.example.com".

• DNS-01 challenge must be used to issue/renew wilcard cerfificates, HTTP-01 challenge is not allowed only available via ACMEv2

Activities

• Use Let's Encrypt certbot to request a wildcard certificate (since 2018)
• Renews your wilcard certificate: certbot renew

Related terms

• RFC 2818
• Wildcard DNS record

See also

• HTTP, HTTP client, HTTP/1.1, HTTP/2, HTTP/3, HTTPS, HSTS CSR, TLS, SSL, openSSL, WebSockets, WebRTC, ssl_certificate QUIC, HPKP, CT, List of HTTP status codes, URL redirection, Content-type:, Webhook, HTTP headers, --insecure, Axios HTTP client, HTTP cookies, HTTP ETag
• CA, Root Certificates, FreeIPA, PKI, OpenCA, Wildcard certificate, certtool, certbot (Let's Encrypt), certinfo (Cloudflare), ACME, Boulder, cfssl (Cloudflare), Public key certificate, public key, TLS and X.509, OCSP, Subject Alternative Name (SAN), openssl ca, Self signed certificate, CSR, keytool, ACM, KMS, aws acm, IdenTrust, multirootca, cert-manager, ca_cert_identifier
• TLS, mTLS: OpenSSL, LibreSSL, BoringSSL, WolfSSL, X.509, .pem, SNI, CT, OCSP, Mbed TLS, ALPN, your connection is not private, SSL Certificate Checker, Wildcard certificate, JA3 fingerprint, sslcan, TLS inspection

Wildcard SSL certificate limitation on QuovadisGlobal.com

https://letsencrypt.org/docs/challenge-types/

https://community.letsencrypt.org/t/acme-v2-and-wildcard-certificate-support-is-live/55579