Replying to @DerVonDenBergen
See groups.google.com/g/crtsh/c/…. Still no ETA, but we're working on it.
1
The crt.sh web interface truncates large result sets for performance reasons, and I haven't yet found a way to efficiently sort by certificate expiry date before truncating.
Try crt.sh/?Identity=equifax.com…
1
81
crt.sh's (re)counting of expirations has now caught up.
Replying to @rmhrisk
crt.sh has caught up on (re)counting issuances, but has not yet caught up on (re)counting expirations. See groups.google.com/g/crtsh/c/…
1
1
149
Replying to @julianor
crt.sh has fallen significantly behind on ingesting new log entries (see crt.sh/monitored-logs). However, I was finally able to deploy some performance improvements this week, and I'm hoping the ingestion backlog will disappear within the next month or so.
1
1
82
crt.sh is currently way behind on ingesting log entries, unfortunately (see crt.sh/monitored-logs). Performance improvements coming soon.
1
51
Replying to @ericlaw
Please try it now, using either the default "q=" search type (which is what the crt.sh/ front page search interface uses) or the more specific "cnlspkisha256=" search type.
e.g., crt.sh/?cnlspkisha256=sha256…
Implemented by github.com/crtsh/certwatch_d…
Replying to @ericlaw
Is the prefix always "sha256/", or are there other options?
Is the remainder of the string a base64-encoded certificate thumbprint? Or something else?
1
77
Replying to @Martijn___ @jschauma
The certificate_identity table is a historical artifact from the original crt.sh database, which had int32 certificate IDs. As part of rebuilding the database to have int64 IDs, I switched to using postgres's Full Text Search instead.
1
1
