Since the main purpose of Pebble is testing, and since Pebble already keeps track of revoked certificates, it would be useful if Pebble had a simple endpoint that reports the status of a certificate. It makes sense for Pebble to do this, since there is no other way (since there is no CRL or OCSP).
The certificate could be identified by its hash (SHA256) and the response would be “valid”, “revoked”, or “unknown” (for certificates not found in Pebble’s internal database).
I don’t think this would involve much extra code in Pebble, and it would be valuable for unit testing a client, since it would become possible to check whether a certificate had been properly revoked.
What do you think?