CertLens support

For the CertLens browser extension (the consumer build). CertLens Fleet is supported through your organization.

The inventory stays empty

Chrome hands certificates to extensions only when its WebRequestSecurityInfo feature is on, and it ships off by default. Open chrome://flags/#web-request-security-info (paste it into the address bar), set Enable SecurityInfo in WebRequest API to Enabled, click Relaunch, then browse any HTTPS site. The dashboard's Capture tab reports whether certificates are arriving and shows the same steps until they do. Chrome 144 or later is required; older versions cannot expose certificates to extensions at all.

Report a problem

Open an issue at github.com/invenity-labs/certlens/issues. Issues are public; do not paste anything you would not want seen. If a report needs a private channel, say so in the issue and we will arrange one.

What to include

• Your Chrome version (chrome://version) and whether WebRequestSecurityInfo is enabled in chrome://flags. The Capture tab in the dashboard shows both.
• What you expected and what you saw. A screenshot of the dashboard helps.
• For a finding you think is wrong: the certificate, exported as PEM from its detail page (Download PEM), or the finding's rule id from the Findings tab. A certificate is public information; the hostname it was served for may not be, so redact if you need to.
• For a page that was blocked or bannered: the hostname and the issuer shown in the banner.

What CertLens will not ask for

Nothing that identifies you. CertLens keeps no account and sends no telemetry, so there is nothing on our side to look up; everything needed to reproduce a problem is on your machine and in your hands.

Privacy

The privacy policy describes exactly what CertLens records and what leaves your machine, and when.