Validity, checked directly
Uptiva connects to the site and reads the certificate it presents. An expired or untrusted certificate becomes an invalid result rather than hiding behind an otherwise reachable web server.
Keep trust intact.
Stay ahead of expiry.
Watch certificate validity and renewal dates before a browser warning becomes the first sign of trouble. Give every important HTTPS service a clear certificate health check.
Part of your Uptiva workspace · One workspace. Every signal.
CERTIFICATE HEALTH72 days remaining
Time to renew. Room to breathe.
TodayRenewal date
- Certificate
- example.com
- Validity
- Valid
- Days remaining
- 72 days
- Next check
- Daily
Automatic renewal is useful, but it is still a process that can fail. An independent SSL monitor checks the certificate presented by your site and makes its validity and remaining lifetime visible in your workspace.
Choose the warning period and expiry notifications that give your team enough time to act. When a certificate changes, the next scheduled check reads the current certificate so you can verify that the renewal reached the service.
Keep this signal alongside the rest of your stack: organize related services, choose who receives alerts and follow recovery in the same workspace. The goal is a check that explains what changed and gives the right person a useful place to start.
SMALL DETAILS. USEFUL CONTEXT.More than
More than
an up or down.
Purpose-built checks.
Information you can act on.
An early warning window
Choose how many days before expiry the monitor should show as degraded. Set the window to match your renewal process and the time your team needs to respond.
Expiry reminders
Select the supported notification milestones before the expiry date. A reminder sequence helps a renewal task stay visible instead of relying on a single calendar entry.
Certificate identity
Review the issuer, subject, common name and issue date. These details help confirm that the endpoint is presenting the certificate you expected.
Fingerprints and dates
The details card includes certificate fingerprints and serial information alongside the expiry date. Keep the exact certificate identity available during an investigation.
A focused companion to uptime
A website can answer while its certificate is close to expiry. Pair SSL and website monitors to cover both current availability and a preventable future interruption.
WHERE IT FITSMade for the work
Made for the work
you already do.
One reliable signal.
Plenty of practical uses.
Automatic renewal checks
Monitor sites that renew through automation. A healthy renewal job is only part of the story; the live endpoint also needs to present the renewed certificate.
Client portfolios
Keep certificates for multiple properties visible in one workspace. Use recognizable names and groups so the right service is easy to find when an expiry reminder arrives.
Critical HTTPS endpoints
Watch customer portals, API gateways and other trusted entry points. Certificate health is especially useful when several people own different parts of the deployment.
FROM SETUP TO A USEFUL SIGNALStart with what
Start with what
matters most.
Use a meaningful name, choose the behavior you expect and make sure the alert reaches someone who can act. Start with one service, then add the related checks as your monitoring grows.
Open the setup guide- 01
Choose your starting point.
Create an SSL certificate monitor and enter the site address whose certificate you want to inspect.
- 02
Configure the check.
Choose a warning period, check schedule and the expiry notification milestones your team needs.
- 03
Follow the signal.
Review the validity and certificate details. After renewal, confirm that the next check sees the new expiry date.
A LITTLE MORE CONTEXTGood questions.
Good questions.
Clear answers.
The details that help you choose the right check and get a useful result.
Read the full documentationHow frequently are certificates checked?+
SSL checks support hourly or daily schedules, with new monitors starting at a daily interval. Certificates usually change much less often than ordinary HTTP responses.
What is the difference between degraded and down?+
A valid certificate inside your warning window is degraded. An invalid certificate, such as an expired or untrusted one, is down. The distinction keeps an upcoming renewal separate from a current trust problem.
Can I choose expiry reminders?+
Supported reminders are 60, 30, 14, 7, 3 and 1 day before expiry. Each selected reminder is sent once for an expiry date, and the sequence starts over after renewal.
What about self-signed certificates?+
The details show that a certificate is self-signed and the SSL monitor reports it as invalid. An HTTP monitor with a different TLS policy serves a different purpose from validating public certificate trust.
Why does an old expiry date still appear?+
The monitor picks up the new certificate on its next scheduled check. Also verify that the actual public endpoint has been updated, including any proxy or gateway in front of the application.
LESS CHECKING. MORE KNOWING.One more thing
Get started One more thing
off your mind.
Bring ssl monitoring into your workspace.