Crt.sh seems to have great problems

FYI:
crt.sh seems to have some problem. It issues gateway error randomly half of the requests, and also my certificate with serial 0394eb48c7e1cf5f79f119689dc931e8a9c9 (fingerprint: 9f7bd524588aac785b796ba9c3f68bd6d28a62eb) isn’t there

I don’t know who operates crt.sh, is it LetsEncrypt or somebody else?

1 Like

FYI: Sectigo (Formerly Comodo) owns crt.sh

crt.sh’s google group: https://groups.google.com/forum/#!forum/crtsh

Thank you

2 Likes

There are a number of log aggregators around, you’re not entirely reliant on crt.sh.

e.g. Your cert appears at https://censys.io/certificates?q=parsed.fingerprint_sha1%3A+9f7bd524588aac785b796ba9c3f68bd6d28a62eb

2 Likes

In this case, Sectigo is formerly, not formally, Comodo. :slight_smile:

It’s a wonderful service, but it’s definitely suffered from recurring periods of certificate import backlogs and search timeouts.

2 Likes

My bad😂
Looks like my brain stopped working tonight…

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.