A certificate or client secret that lapses at 2 AM takes a service down with no warning and no obvious cause. CloudMonitor reads the expiry dates across your environment, or your clients', and tells you weeks ahead, not after the page goes dark.
Secrets, keys and certificates are created once and forgotten. A client secret on an app registration, a certificate on a load balancer, an API key in a vault: each has an end date, and the person who set it up has often moved on by the time it arrives.
The failure is quiet until it is loud. Nothing degrades beforehand. A sign-in flow, a payment callback or a customer-facing site simply stops working at the exact moment of expiry, and the first alert is a customer.
Native consoles each show expiry in their own corner, one platform at a time. Nobody opens all of them on a schedule, so the date that matters is the one nobody is looking at.
Every platform CloudMonitor connects to, in the same order on every page, with what it checks for this problem today. Where nothing is checked yet, the table says so.
| Platform | What CloudMonitor checks for this problem | Status |
|---|---|---|
| Microsoft Azure | Key Vault: Secret, certificate and key expiry; vault posture Front Door & CDN: Custom-domain certificate expiry and validation, disabled endpoints and origins, WAF mode API Management: Gateway certificate expiry, stv1 retirement, Developer tier in production | Live |
| Microsoft 365 & Entra ID | App registrations: Expiring secrets and SAML certs, consent risk Intune: Apple push, VPP and DEP token expiry | Live |
| Amazon Web Services | Certificate Manager: Certificate expiry Secrets Manager & SSM: Rotation and age (metadata only) | Beta |
| Google Cloud | Secret Manager: Rotation and age Certificates & Cloud DNS: Certificate expiry, dangling records | Live |
| Kubernetes | Version support, node health and workload checks only. No secret or certificate expiry check yet. | No check yet |
| Containers & registries | Image and host posture only. No secret or certificate expiry check yet. | No check yet |
| On-prem servers & Exchange | Linux servers (SSH): Disk, pending reboot, patch age, certificate files Windows servers (WinRM): Disk, pending reboot, patch age, certificate store Exchange certificates: Every Exchange certificate, the auth certificate included Internal TLS endpoints: Certificate expiry on any host and port, no credential | Beta |
| MuleSoft Anypoint | Runtime status and alerts only. No secret or certificate expiry check yet. | No check yet |
| Domains, DNS & email | TLS certificates: Expiry, TLS 1.0/1.1, weak ciphers Domain registration: Registration expiry (RDAP/WHOIS) | Live |
| Uptime & heartbeats | HTTP(S) endpoints: Reachability and TLS handshake every 5 minutes on paid plans Each endpoint check reads the certificate it is served and reports days left, with the status code. | Live |
How deep each platform goes. Live means scheduled for every connected account; Beta means scheduled and verified against emulated APIs only. Azure is the most complete and is run against real accounts every day. The AWS and Google Cloud scanners have been verified against emulated APIs, not yet against live customer accounts. Kubernetes, MuleSoft and the on-prem collector are narrower still.
Access is read-only and least-privilege, and there are no agents to install on your cloud accounts.
Full setup guide: connectors.
Vault secrets, keys and certificates, application client secrets and SAML certificates, load balancer and gateway certificates, on-prem server certificates (including Exchange), public TLS certificates on your domains and domain registration dates. The table above lists exactly what each platform contributes.
Alerts step up at 90, 60, 30, 14, 7 and 1 day before expiry, and again on the day itself. Items under 30 days are warnings, under 7 days are critical, and past expiry is marked expired.
Every connected account gets a full scan at least once a day, so expiry findings appear after the next nightly scan. Public certificate and domain checks run on their own schedule with no connection needed.
No. Access is read-only and least-privilege, and there are no agents to install. For AWS Secrets Manager and Systems Manager it reads rotation and age metadata only.
Yes. Connect each client environment separately; the MSP add-on adds a cross-client worklist. Pricing counts units across everything you connect, and the details are on the pricing page.
No, and the table says so. Depth differs by platform: Azure is the most complete and is run against real accounts every day. The AWS and Google Cloud scanners have been verified against emulated APIs, not yet against live customer accounts.
14-day free trial. No credit card needed to start, and it never turns into a paid plan on its own.