You know before your SSL certificate expires and visitors see a warning
Daily checks warn you 15 days ahead by default, and again as the date gets closer, so there is time to renew.
What every daily check inspects
Each daily SSL/TLS check runs the full certificate through the same set of validations, so expiry risk is caught ahead of time and failed checks are surfaced on the next daily run.
An expiring certificate is flagged weeks ahead; any other failed check is surfaced on the next daily run, and SSL incidents from the period also appear in the workspace report.
SSL analysis grades every part of your certificate
Each daily check validates the chain, expiry, TLS protocol, cipher, and signature, and flags anything worth attention, such as a certificate without a published OCSP endpoint.
OCSP endpoint is not published
Certificate chain is valid
TLS protocol version: TLS 1.3
Cipher strength: 256 bits
Certificate expires in 33 days
How WebPixie watches your SSL
WebPixie validates every monitored SSL certificate daily. Each check validates the served certificate against the trusted root CAs and confirms it matches your hostname, so an untrusted, self-signed, expired, or hostname-mismatched certificate is caught on the daily check. The same check verifies the full chain from leaf to intermediate to root and performs cryptographic signature verification for RSA, EC/ECDSA, Ed25519, and Ed448. It also resolves your domain to every IP it points to and checks that each one serves the same, working certificate, so a mismatch behind a load balancer is surfaced. To spot unauthorized issuance, the Certificates Manager (included when SSL monitoring is on) lists the certificates seen for your domain in public Certificate Transparency logs.
The check surfaces the TLS version, cipher suite, key strength, and Subject Alternative Names, and queries OCSP (falling back to CRL) to confirm the certificate has not been revoked. When a certificate approaches renewal, an alert fires 15 days before expiration by default.
There is nothing to install. WebPixie reads the certificate directly during the TLS handshake from its monitoring servers. As soon as you add your domain, daily SSL checks begin.
The full configuration options are in the SSL monitoring docs.
15 days of notice before a certificate expires
Auto-renewal can fail quietly
Expired SSL certificates trigger browser security warnings that block customers from your site. WebPixie sends expiry warnings 15 days before expiration by default. The warning becomes more urgent at 7 and 3 days. Daily revalidation also catches the case where auto-renewal fails silently and the certificate moves toward expiry anyway.
Full certificate chain validation
Leaf to intermediate to root, with cryptographic verification
A certificate with a valid expiry date can still fail validation if intermediates are missing or signatures are mismatched. WebPixie validates the complete chain on every daily check, with cryptographic signature verification for RSA, EC/ECDSA, Ed25519, and Ed448.
Certificate consistency across every IP
Multi-IP resolution, wildcard and SAN coverage
A domain can resolve to several IPv4 and IPv6 addresses, especially behind a load balancer. WebPixie checks the certificate served by each resolved IP against the first IP as a reference, so a different or non-working certificate is surfaced for review. SAN extraction also covers wildcard and multi-domain certificates.
TLS configuration and cipher strength monitoring
Versions, suites, key exchange, key strength
A valid certificate does not guarantee a secure connection. WebPixie reports the TLS version negotiated, the cipher suite in use, the key exchange algorithm, and the key strength for every monitored endpoint. Servers on older TLS versions are still checked and reported, and a weak cipher or a connection without forward secrecy is flagged.
You can set up SSL monitoring in about a minute
Free plan, no credit card. Daily SSL checks on every plan.
Everything you need to monitor a website. In one workspace.
A quick look at other WebPixie features.
Why teams choose WebPixie for SSL
Setup takes about a minute
No agent to install and no access to your server needed. You enter a domain and daily SSL checks start running from WebPixie’s monitoring servers.
Your whole site in one workspace
SSL monitoring sits next to uptime, DNS, domain, and link health in one dashboard. Scored technical checks across the data WebPixie collects, such as security headers, SSL configuration and DNS configuration, roll into your WebPixie Site Score.
Alerts that reach your team
Expiry and certificate-check alerts go out by email on every plan, and through integrations such as Slack and webhooks on higher plans, so an expiry date never catches the team by surprise.
Frequently Asked Questions
Common questions about SSL monitoring.
Yes. WebPixie checks your certificate every day and, by default, emails you 15 days before it expires, so there is time to renew it before visitors see a warning. The certificate is what puts the padlock next to your address in the browser. When it expires or stops being trusted, visitors get a full-page "Your connection is not private" warning instead of your site, and many leave rather than click past it. SSL monitoring raises the warning's urgency at 7 days and again at 3 days, and it also alerts you when a daily check finds the certificate untrusted or issued for the wrong address. Many hosts renew certificates automatically, but automatic renewal can fail after a move or a settings change, which is exactly the case this catches. The renewal itself happens at your hosting company or website platform, so the alert can go to whoever manages it. On paid plans each warning is also tracked in incident management; you can compare plans on the pricing page.
WebPixie surfaces certificate validity, chain consistency, expiration, TLS configuration, and certificate identity details for each monitored site. SSL monitoring validates the served certificate against the trusted root CAs and confirms the hostname matches; it then extracts the full certificate chain from leaf to intermediate to root and verifies cryptographic signatures for RSA, EC/ECDSA, Ed25519, and Ed448 certificates. It also reports TLS version, cipher suite, key exchange, key strength, Subject Alternative Names, and Extended Key Usage OIDs, and queries OCSP (falling back to CRL) to confirm the certificate has not been revoked. Expiration tracking is included, with default warnings 15 days before a certificate expires so teams have time to renew. SSL check failures and expiration events can create incidents through incident management, depending on your plan. Teams managing several domains can use the Certificates Manager to review Certificate Transparency inventory across domains and subdomains. The certificates docs have the full field reference.
No. WebPixie monitors SSL certificates; it does not issue or renew them. Renewal stays with your certificate authority, such as Let’s Encrypt, your hosting provider, or another CA. The recommended workflow is automatic renewal at your CA paired with SSL monitoring to confirm the renewal actually happened. Daily revalidation catches the common failure where a Let’s Encrypt auto-renewal breaks silently and the original certificate keeps moving toward expiry. WebPixie sends an expiry warning 15 days before expiry by default, and a failed check can open a tracked incident through incident management on supported plans. Teams managing many certificates can review public CT-log inventory in the Certificates Manager.
Yes. WebPixie monitors both wildcard certificates, which cover *.example.com, and SAN certificates, which cover several specific domains under one certificate. On every daily check, SSL monitoring extracts the Subject Alternative Names and confirms the monitored hostname is covered by the certificate, alongside full chain validation and expiry tracking. This is useful for teams running many subdomains under a single wildcard or multi-brand certificates that list several domains. If you manage several certificates across domains and subdomains, the Certificates Manager gives you a CT-log inventory in one place, and a failed SSL check can open a tracked incident through incident management on supported plans.
Certificate Transparency (CT) is a public, append-only logging system that certificate authorities write to whenever they issue a certificate, so anyone can audit which certificates exist for a domain. It was created to catch mis-issuance: before CT, a certificate authority could issue a certificate for your domain, by mistake or after a compromise, and you might never find out. Because every issuance is now recorded in public logs, an unexpected certificate becomes visible instead of silent. This matters for security, because an attacker holding a valid certificate for your domain can impersonate your site convincingly and intercept traffic while the browser padlock still looks normal. CT does not prevent a bad certificate from being issued; its value is making that issuance discoverable so you can respond. WebPixie surfaces CT data for review in the Certificates Manager, while the per-site chain and expiry checks that actually alert you live in SSL monitoring.
Ready to watch your certificates?
Free plan, no credit card. Daily checks with 15-day expiry warnings.
From the blog









