Wildcard SSL certificate expired

When *.example.com expires, every matching subdomain fails until you redeploy a renewed wildcard or replace it with per-host certificates.

Wildcards simplify ops until the night they all expire together.

Nested names like a.b.example.com are not covered unless specified in SAN.

First response

A wildcard *.example.com cert expiring takes every matching subdomain offline. Renew early, validate SAN coverage for nested names, and monitor all hosts that share the wildcard file.

Search interest in wildcard ssl certificate expired rises when the leaf notAfter on the hostname customers type is already in the past. Clients cannot rewrite server certificate dates; they only accept chains that pass PKIX checks at handshake time.

For Wildcard SSL certificate expired, prove the failure from outside your office VPN before you change application code, purge caches, or ask end users to reboot. Capture the broken serial number and notAfter, renew on the listener that actually terminates that name, reload every node in the path, then re-run the same OpenSSL and browser checks that opened the incident.

Escalations for wildcard-ssl-certificate-expired should cite fresh openssl on apex and nested names like a.b.example.com output before anyone edits client code or blames Wi‑Fi. A wildcard *.example.com cert expiring takes every matching subdomain offline. Renew early, validate SAN coverage for nested names, and monitor all hosts that share the wildcard file. When simultaneous subdomain outages clusters around Every hostname matching *.example.com, the expired material is usually bound to shared wildcard PEM on many vhosts instead of a mysterious platform bug. Executive summaries need the public hostname and current notAfter, not screenshots from a VPN-split test laptop.

See also Android SSL certificate expired errors and CDN edge OK but origin certificate expired.

What this error means

One notAfter controls the entire wildcard footprint.

Shared PEM on many vhosts means one missed reload breaks dozens of sites.

Renew early, validate SAN coverage, orchestrate rolling reloads, verify top subdomains.

In PKIX terms, Every hostname matching *.example.com treat the TLS Certificate message as authoritative: signatures must verify, each link must be within notBefore/notAfter, and only then does name matching run against CN and SAN. When the leaf expired, simultaneous subdomain outages is expected even if the issuer is publicly trusted. Guides titled wildcard ssl certificate expired still require reading dates on every certificate the server sends, including forgotten cross-sign intermediates.

Triage for wildcard ssl certificate expired should reject quick myths: flushing DNS or rebooting laptops does not move server notAfter forward. It is not proof the whole internet is broken when other HTTPS sites load for Every hostname matching *.example.com. It is not interchangeable with registrar billing lapses unless revalidation fails later. It is not fixed by turning off TLS at the load balancer while marketing keeps publishing https:// links. Validated externally, openssl on apex and nested names like a.b.example.com must show fresh dates on shared wildcard PEM on many vhosts before you close the incident.

Common causes

These patterns appear often during wildcard ssl certificate expired incidents. They are not exhaustive, but they explain why renewal looked finished internally while strangers still received expired material.

Runbooks for wildcard ssl certificate expired most often break at handoff: certbot or a vendor portal issued new certs, but shared wildcard PEM on many vhosts never received a reload. Teams tracked PEM files in git while production continued serving the previous listener binding. OV renewals waited on legal approvers until simultaneous subdomain outages became customer-visible. Inventory spreadsheets omitted the hostname that Every hostname matching *.example.com actually call during peak traffic.

Architecture amplifies wildcard ssl certificate expired: multiple regions, canary pools, or blue/green deploys can leave one ASG member presenting yesterday's fullchain. Shared IP default certificates silently terminate vanity hostnames without dedicated SNI rules. Mounted TLS secrets updated on disk while Envoy or nginx workers kept the old chain until signaled. A wildcard * becomes harder to debug when only a fraction of Every hostname matching *.example.com hit the stale anycast node.

Measurement gaps complete the story for wildcard ssl certificate expired. Synthetic monitors that disable certificate verification greenlit deploys that fail for real Every hostname matching *.example.com. Redirect maps hid which hop expired until operators ran openssl on apex and nested names like a.b.example.com per hostname. Dashboards celebrated TCP uptime while notAfter crossed midnight UTC without a page. Post-mortems should ask whether CT logs or stapled OCSP would have warned days earlier.

Confirm from the outside

OpenSSL

echo | openssl s_client -connect HOST:443 -servername HOST 2>/dev/null | openssl x509 -noout -dates -subject -issuer

Confirm *. SAN and check notAfter once for all children.

How to read the output

Start with openssl on apex and nested names like a.b.example.com against the live customer hostname, capturing the leaf presented after SNI selection. Interpret notBefore= and notAfter= first: past notAfter guarantees failure for simultaneous subdomain outages regardless of pretty issuer branding. Next read subject= and any X509v3 Subject Alternative Name extension for alignment with the URL bar. Finally note issuer= so you know whether renewal changed intermediates; record serial numbers in the ticket for post-deploy diffing.

curl

curl -vI --connect-timeout 10 https://HOST/ 2>&1 | grep -Ei 'expire|SSL certificate|subject:|issuer:'

Sample curl across critical subdomains after deploy.

Browser spot-check

Spot-check customer-facing subdomains in browser.

Fix checklist

Work this list in order for wildcard ssl certificate expired. Each step should produce evidence (command output, timestamps, serial numbers) you can paste into the incident ticket.

1. List all hosts using the wildcard file.
2. Plan maintenance window for mass reload.
3. Renew wildcard or migrate to ACME per-host.
4. Update secrets managers and ansible vaults.
5. Roll configs to every region.
6. Verify random sample of subdomains externally.
7. Update documentation of shared dependency.
8. Consider splitting high-value hosts off wildcard.

Roll out and verify

Procurement for wildcard ssl certificate expired begins with a reissue that lists every hostname Every hostname matching *.example.com need, including forgotten admin and callback URLs. Validate CSR/key pairs, download CA bundles, and schedule work on shared wildcard PEM on many vhosts during a staffed change window. If automation handles ACME, prove challenges use the same DNS names customers resolve publicly, not internal-only labels.

Installation for wildcard ssl certificate expired means concatenating leaf and required intermediates the way your stack documents, then touching every node that terminates the name. Reload web servers, recycle ingress pods, or update cloud listener objects so data planes read new bytes. For load balancers, sync default and per-host certificates so SNI cannot fall back to expired defaults. Repeat openssl on apex and nested names like a.b.example.com until fingerprints or serials change everywhere responders tested earlier.

Verification for wildcard ssl certificate expired must mimic strangers: external synthetics, mobile carriers, and CI jobs without corporate trust roots. Confirm simultaneous subdomain outages disappeared for Every hostname matching *.example.com on flows heavier than GET /. Restore any strict TLS, HSTS, or CDN SSL modes relaxed during firefighting. Feed the hostname into continuous notAfter monitoring with thresholds well before the next CA-enforced renewal cliff.

What to automate

Certificate files on disk lie. Automate live TLS checks on the exact hostname and port users hit, including redirects and the certificate presented after TLS terminates on a load balancer or CDN. Pair certificate notAfter with RDAP domain registration expiry so re-validation is not blocked by a lapsed registrar.

Map wildcard consumers automatically from CMDB tags. Schedule alerts at 30, 14, 7, and 1 day before expiry so on-call has runway for ACME failures, manual OV revalidation, or change windows. Services such as ssldays can run external checks and renewal reminders without replacing your CA workflow.