A certificate observation, made clear.
See the names, issuer and validity dates behind an observed certificate. Understand what you know — and what still needs an endpoint check.
example.com
Registered through the Certbot Hook. The example observations below match names under this root.
Observed certificates
Open a record to see its matching names and dates.
api.example.comIssuer: Example CA (fictional)First detected by BamGuard: 16 Oct 2026, 08:12 UTCValid until: 14 Jan 2027
- Matching names
- api.example.com
- Not before
- 16 Oct 2026
- Valid until
- 14 Jan 2027
- State
- Certificate observed
First detected is when BamGuard observed the metadata, not necessarily when the certificate was issued. Validity describes this certificate, not what an endpoint currently serves.
www.example.comIssuer: Example CA (fictional)First detected by BamGuard: 12 Oct 2026, 09:40 UTCValid until: 10 Jan 2027
- Matching names
- example.com, www.example.com
- Not before
- 12 Oct 2026
- Valid until
- 10 Jan 2027
- State
- Certificate observed
First detected is when BamGuard observed the metadata, not necessarily when the certificate was issued. Validity describes this certificate, not what an endpoint currently serves.
*.example.comIssuer: Example CA (fictional)First detected by BamGuard: 5 Oct 2026, 14:05 UTCValid until: 3 Jan 2027
- Matching names
- *.example.com
- Not before
- 5 Oct 2026
- Valid until
- 3 Jan 2027
- State
- Certificate observed
First detected is when BamGuard observed the metadata, not necessarily when the certificate was issued. Validity describes this certificate, not what an endpoint currently serves.
An Observation does not identify its monitor. These example records do not assert CT inclusion or a currently deployed certificate.
Certificate observed
Matching certificate metadata was observed for api.example.com.
- First detected by BamGuard
- 16 Oct 2026, 08:12 UTC
- Valid until
- 14 Jan 2027
Turn an observation into a useful question.
A new matching certificate is a reason to review its names, issuer and validity. In your account, Observation notifications and configurable email preferences help bring that evidence to your attention.
To confirm rollout, check the certificates served by your web servers, load balancers and CDNs. A record in an inventory cannot prove every client sees that certificate.
Read the observed vs. deployed guideBring visibility to your own certificates.
The real setup starts with your account and the Certbot Hook. Certificate private keys stay in your infrastructure.
14-day Starter trial. Payment details required. A paid Starter subscription begins unless cancelled. Signup availability is controlled by BamGuard.