Public Audit Log

Certificate Transparency

Key registrations, transfers and relay announcements are all appended to one tamper-evident Merkle tree. Anyone can check that an entry is in the tree without seeing the payload, the way HTTPS certificate transparency logs work.

What is in this log, and whose it is You are looking at the log of one relay, health.paramant.app, the one the web app on this site sends through. Each of the relays we run keeps its own log, so this is not a total. Most of the entries below are not transfers at all: they are our own relays announcing themselves. Every entry here is something a relay said about itself, and for a long time each of them said it again on every restart, which is why the number below is as large as it is. A relay that announces itself and has nothing new to say no longer writes a line. Either way, the number of entries is not a measure of how much the service is used.
Persistent log: survives relay restarts Hashes are written to disk (/data/ct-log.json) on each registration and reloaded on startup. No payload content is ever stored: only cryptographic hashes. The log resets only when the relay volume is deleted.
n/a
Log entries
n/a
Key registrations
n/a
Transfer proofs
n/a
Relay announcements
n/a
Merkle Root
n/a
Relay
n/a
Last Entry

Verify a hash

# Leaf Hash Tree Hash Device Hash Timestamp
Loading log…