badssl.com: Subdomain with ERR_CERTIFICATE_TRANSPARENCY_REQUIRED
It’d be great to have a reliable endpoint for demonstrating and testing NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED errors, like this one:

It can be an ordinary DV certificate, and hopefully shouldn’t be too expensive – perhaps Symantec would even donate one. I’m not sure if there’s any meaningful difference in having an endpoint with SCTs for non-compliant-ly redacted certs (like the above example) or for an endpoint with no SCTs at all. Whatever’s easier.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 4
- Comments: 21
Commits related to this issue
- Add invalid-expected-sct cert for #215. — committed to chromium/badssl.com by lgarron 8 years ago
- Serve invalid-expected-sct.badssl.com . Addresses #215. — committed to chromium/badssl.com by lgarron 8 years ago
Alright, we’re live. Thanks so much, @AGWA.
@marumari, this error is only in Chrome. How do you weigh on putting this subdomain on the home page?