Hmmmm, shouldn't all certificates end up on https://crt.sh ?
-
Hmmmm, shouldn't all certificates end up on https://crt.sh ? I mean I get it if there is a wildcard cert that not all hostnames end up on there. But there is no wildcard cert and I see a certificate for a different hostname... why isn't it on crt.sh?
-
Hmmmm, shouldn't all certificates end up on https://crt.sh ? I mean I get it if there is a wildcard cert that not all hostnames end up on there. But there is no wildcard cert and I see a certificate for a different hostname... why isn't it on crt.sh?
@floyd The page doesn't even load properly for me. I get "502 Bad Gateway".
-
@floyd The page doesn't even load properly for me. I get "502 Bad Gateway".
@mark22k yeah, that part is kind of expected sometimes...
but it's still "the" certificate transparency website -
Hmmmm, shouldn't all certificates end up on https://crt.sh ? I mean I get it if there is a wildcard cert that not all hostnames end up on there. But there is no wildcard cert and I see a certificate for a different hostname... why isn't it on crt.sh?
@floyd did you try searching through their postgres instance?
-
@floyd did you try searching through their postgres instance?
@pop_eax nope, not yet, I should read up about that then?
-
@pop_eax nope, not yet, I should read up about that then?
@floyd sometimes I had better luck using it.
psql -h crt.sh -p 5432 -U guest certwatch -
R relay@relay.infosec.exchange shared this topic
