TrustBridge
Certificate Authority
TrustBridge
Certificate Authority
TrustBridge issues digital certificates — the credentials that prove a website, a program, an email, or a device is really what it claims to be. It's built and operated with the same care a public certificate authority uses: a clear policy anyone can read, published proof of what's been issued, and a real way to check whether a certificate is still valid.
The certificate that makes a browser show a secure connection — proves a site is who it says it is.
Proves a piece of software actually came from us and hasn't been tampered with since it was signed.
Lets an email be digitally signed or encrypted, so a recipient can verify who really sent it.
A certificate installed on a device can prove that device's identity on its own — no password needed.
Anyone can download our root certificate, verify its fingerprint, and read exactly how we operate — see /roots and our policy.
We support the same automated domain-proof process (ACME) that services like Let's Encrypt use, so a certificate can only be issued to someone who actually controls the domain.
If a certificate needs to be revoked, that's published immediately and stays checkable for as long as the certificate would otherwise have been valid.
TrustBridge starts as a private certificate authority — the devices and browsers that use it are set up to trust it directly, the same way any organization's internal PKI works. Everything behind it — a real published policy, an audit trail, proper revocation checking — is being built the way a public certificate authority is expected to operate, since that kind of trust is earned over time, not something you can bolt on later. See our policy for the current state of that work.