Certificate transparency & re-key log
TLS hubs (adcs://) are identified by their certificate keyprint. When a listed hub begins presenting a different keyprint, we pause publishing its keyprint and record the change here. A re-key is routine, but an unexpected change can indicate a man-in-the-middle — owners confirm a legitimate re-key out-of-band.
| Hub | When | Recorded keyprint | New keyprint |
|---|---|---|---|
| DCHUB.ONE | 19h ago | SHA256/3OGGAUC5C6RCZEXS2PDY5R7VCIM7YTF5JZ74YBJW3V2M3FB72BCQ | SHA256/G2NBAA2JUQXCK3MICDYQE5PHPORBQRKXABY62OAVQF2B7KJD76KA |
Accepted re-keys
Keyprint changes the hub owner or list operator has confirmed as legitimate. Kept permanently (latest 200) so a hub's certificate history stays auditable.
| Hub | Seen | Accepted | Old keyprint | New keyprint |
|---|---|---|---|---|
| adcs://dchub.one:411 | 14d ago | 14d ago | SHA256/I2Y2GXQFBAUOZHVDIXDUB3YXHJZUXDAYJLEWCCWCBDSEYZNCDZTQ | SHA256/3OGGAUC5C6RCZEXS2PDY5R7VCIM7YTF5JZ74YBJW3V2M3FB72BCQ |
Certificates expiring soon
TLS hubs whose certificate expires within 14 days (or already has). An expired certificate breaks clients that verify it — hub owners, renew in time.
| Hub | Issuer | Expires |
|---|---|---|
| [sTiFF-Meister] | www.it-admin.se | EXPIRED 691d ago |
| AirDC++ Web Client Dev | web-dev.airdcpp.net | EXPIRED 644d ago |
Related: Hub list · Statistics · Clients · Downloads · FAQ