Every certificate issued for your domain, including ones you didn't request
WebPixie reads public Certificate Transparency logs and lists the certificates and subdomains it finds, so you can review them and add forgotten subdomains to monitoring.
You can discover subdomains you are not monitoring yet
The same Certificate Transparency data reveals subdomains across your domain, collected from CT log entries and your main certificate's SANs. You can add any of them to monitoring in one click.
Subdomain discovery is sourced from public CT logs and certificate SANs; it does not brute-force or scan your infrastructure.
How the Certificates Manager works
The Certificates Manager periodically pulls public Certificate Transparency (CT) logs for each domain you monitor and lists certificates seen for it and its subdomains. For each entry you get the common name, identity (SAN), validity window (not before and not after), issuer, and serial number.
CT logs give you a public record of certificates reported by public CAs, so this is where you can spot a certificate you did not expect: a mistaken issuance, a compromised CA, or an unauthorized certificate for your brand. CT data is shown for review; the alerts come from SSL monitoring.
It is enabled automatically when SSL monitoring is on, with nothing extra to install. The per-site certificate checks (chain, expiry, TLS, cipher) live in SSL monitoring; the Certificates Manager is the CT-log view across your domains and subdomains.
The full configuration options are in the Certificates Manager docs.
Certificates seen for your domain
A Certificate Transparency log inventory
Certificates can be issued for your domain by any public CA, from anywhere. The Certificates Manager lists certificates seen in CT logs for your domain and its subdomains, each with its common name, SAN, validity window, issuer, and serial number, so you have one place to review what exists.
You can spot unexpected or unauthorized issuance
Review of certificates you did not request
An attacker who obtains a valid certificate for your domain can impersonate your site convincingly. When a certificate you did not request appears in public CT logs, you can investigate a mistaken issuance, a compromised CA, or an outright unauthorized certificate.
Subdomain discovery from your certificates
Surfaced from CT logs and certificate SANs
The same CT data reveals subdomains you may not be monitoring yet, collected from CT log entries and the SANs on your main certificate. Each discovered subdomain comes with an Add Site action, so turning a discovery into a monitored site is one click.
Works with SSL monitoring
Enabled automatically, no separate setup
The Certificates Manager turns on with SSL monitoring, with nothing extra to configure. The per-site chain, expiry, TLS, and cipher checks live in SSL monitoring; the Certificates Manager is the Certificate Transparency view that sits alongside them.
You can review your CT certificate inventory in about a minute
Free plan, no credit card. Included 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 certificate management
Setup takes about a minute
No agent to install. The Certificates Manager turns on with SSL monitoring; once you add a domain, WebPixie pulls its Certificate Transparency history.
Your whole site in one workspace
The certificate inventory sits next to uptime, SSL, DNS, domain, and link health, with one dashboard across all of them.
Built on SSL monitoring
Per-site validation and expiry alerts come from SSL monitoring; the Certificates Manager is where you review the Certificate Transparency inventory.
Frequently Asked Questions
Common questions about the certificate manager.
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.
Yes. Because the Certificates Manager reads Certificate Transparency logs, it surfaces certificates seen for your domain and subdomains even when they were not requested through your own process. An unexpected certificate can signal a misconfiguration or an unauthorized issuance, and seeing it in the log is the first step to acting on it, so you can tell a legitimate renewal from something that warrants review. It turns on automatically with SSL monitoring and lists each certificate's common name, SAN, validity window, issuer and serial number. This view is for review: WebPixie does not send an alert when a new certificate appears in the logs. The same data set powers subdomain discovery: subdomains found in Certificate Transparency logs and in your main certificate's SANs are listed with an action to start monitoring each one. WebPixie reports what the public record shows; it does not issue, renew, or revoke certificates, which stays with your certificate authority. This complements the per-site checks in SSL monitoring, and you can compare plan limits 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.
Ready to review your CT certificate inventory?
Free plan, no credit card. Certificate Transparency log inventory across all domains.
From the blog









