The problemWhy certificates break trust
The solutionYour keys, checked by many
Who runs itNo single party in charge
Questions & answersShort answers, no jargon
Five short sections. By the end you'll understand what's wrong with the padlock, and exactly what ConsensusPKI does differently.
When you visit your bank's website, your browser checks a certificate — a signed statement saying "this really is yourbank.com". The signature comes from a certificate authority: a company or government body your browser has decided to trust.
Here's the catch: your browser trusts hundreds of these authorities, and any of them can sign for any website in the world. Your bank has a business relationship with one of them. The other few hundred have never heard of your bank — but their signature on a fake "yourbank.com" certificate works just as well.
So the security of every website equals the security of the weakest, worst-run authority on the list. When one is hacked, coerced, or simply makes a mistake, an attacker can impersonate any site — and to your browser everything looks normal, padlock and all.
In 2011, attackers breached the Dutch authority DigiNotar and issued over 500 fake certificates — for webmail, social networks and government services. They were used to intercept the private communications of an estimated 300,000 people before anyone noticed. The company went bankrupt; the design flaw it exposed is still with us.
The industry's response was Certificate Transparency: every certificate ever issued gets written into public logs that anyone can inspect. It's a real improvement — forgeries can now be discovered.
Makes issuance visible. A domain owner who watches the logs can spot a certificate they never asked for.
It doesn't stop anything. A forged certificate, once logged, is accepted by every browser. Detection can take days; damage takes minutes.
Transparency assumes someone is watching, notices in time, and can get the certificate revoked before it's abused. Prevention would be better than any of that.
ConsensusPKI starts from a simple principle: nobody should be able to speak for your website except you. Every domain gets a long-lived key held by its owner, and a certificate only counts if it carries the owner's own signature.
Authorities don't disappear — they get a better job. Instead of having the power to issue anything for anyone, they become validators: they check that the person registering a domain key really controls that domain, from many network locations at once, chosen unpredictably so an attacker can't position themselves in advance.
The result flips the security model. Today, compromising one authority breaks every website. In ConsensusPKI, compromising every validator still doesn't let anyone impersonate an established site — because they don't have the owner's key. That claim isn't marketing: it's a theorem, and it's machine-verified.
A public record is only as good as your certainty that everyone sees the same one. ConsensusPKI solves this without blockchains or mining: every hour, the log's new state is co-signed by independent witnesses — browser makers, network operators, civil-society organisations, in different countries and jurisdictions.
A record state only counts with signatures from a majority of witnesses (14 of 20 in the reference design). Two conflicting versions can't both get a majority — any two majorities share an honest witness who refuses to sign twice.
Witnesses don't compete or compute puzzles. They check consistency and sign — once an hour. The whole scheme runs on less power than an office laptop.
Every hourly state provably extends the previous one. Rewriting history, or showing different views to different people, produces cryptographic evidence of exactly who lied.
When you visit a site, the site hands your browser a small proof — a few kilobytes — showing its certificate is in the witnessed public record. Your browser checks it entirely on your device, against the hourly record state it already has.
No phone-home. No "is this certificate still valid?" query to a server that would learn every site you visit. No outage of some central service that could take your browsing down with it. Nothing to be slow, and nothing to spy on you.
The design's real innovation is what each participant cannot do.
Hold the key that authorises everything for their own domain — and nothing for anyone else's.
Confirm domain control from many vantage points. They authorise publication — never the certificate itself.
Maintains the public record. It can't forge entries (no owner keys) and can't lie about history (witnesses check).
Co-sign the hourly state. Individually powerless; only a majority together can make a record count.
Everything above works today with classical cryptography — and keeps working when post-quantum signatures take over. Records can run both side by side, upgrades are one-way by design, and the proofs stay small because the heavy signatures never travel with your connection.