SSL
Certificate lifecycle visibility for validation, issuance, renewal timing, and endpoint trust across governed engine surfaces.
3
Active Bindings
1
Validation Holds
1
Renewal Window
0
Revocations
Certificate Bindings
Wildcard and SAN lifecycle table for validation, issuance, and renewal windows.
| Common Name | Engine | Status | Coverage | Authority | Renewal | Expires |
|---|---|---|---|---|---|---|
| POD Engine Alpha | Issued | Wildcard plus admin SAN | Platform CA | Automatic | 82 days | |
| POD Engine Bravo | Validation pending | Wildcard staged | Platform CA | Automatic after issuance | Waiting on first issue | |
| POD Engine Charlie | Renewal window | Wildcard plus admin SAN | Platform CA | Automatic with review gate | 9 days |
Certificate Posture
Selected binding context for trust state, validation path, and renewal readiness.
Issued and bound
DNS challenge passing
Automatic with prebuilt package
Frontend, admin, and API covered
Lifecycle Timeline
Recent issuance and renewal events for the selected certificate family.
- 01Issuance completedThe wildcard certificate was issued and applied to ingress without runtime interruption.Observed 19 days ago.
- 02Validation records retainedDNS validation records stay visible for operator review and replay confidence.No renewal blockers are present.
- 03Renewal package stagedA future renewal package is already attached to the billing and audit timeline.Next review begins in 52 days.
Binding Coverage
Endpoints and dependencies currently tied to the selected certificate.
- 01Frontend endpointhttps://acmeprints.example is bound through the wildcard certificate.Traffic remains green across the storefront edge.
- 02Admin endpointhttps://admin.acmeprints.example is covered by the admin SAN binding.Governed sessions use the same certificate family.
- 03API endpointhttps://api.acmeprints.example shares the same trust envelope.Token lease refresh does not require certificate changes.