Cloudflare is building a public certificate authority to harden the web against quantum attacks

The web's HTTPS trust layer is one of the most concentrated chokepoints in critical infrastructure: a small number of certificate authorities vouch for nearly every site a browser visits, and a single mis-issuance or compromise can ripple across the open internet. Cloudflare said on September 29, 2026 that it intends to join that list, applying to become a public certificate authority and agreeing to acquire publicly trusted root key material from GlobalSign.

A certificate authority is the system that hands a website a cryptographic ID. When a browser opens an HTTPS connection, the CA's signature on the site's certificate is what tells the browser it is talking to the real site rather than an impostor. The trust layer sits underneath every secure transaction, login, and API call on the public web.

Cloudflare is not issuing certificates yet. The press release and the accompanying engineering blog describe applications to the root programs; classical issuance follows acceptance into those stores, and production issuance of post-quantum Merkle Tree Certificates is scheduled for Q1 2027.

The mechanism Cloudflare is building around is a Merkle Tree Certificate, or MTC. Instead of each certificate carrying a heavyweight signature on its own, an MTC issues a certificate as one leaf in an append-only Merkle tree, with the tree head cosigned by the CA. Standalone certificates still carry the cosigned tree head, so any client can verify them. A site that receives an authenticated tree head out of band, called a landmark, can issue shorter, landmark-relative certificates that omit the heavyweight signature. The net effect, as Cloudflare's engineering team explains, is a transparency primitive that makes every issued certificate visible in a public log while reducing the byte and CPU cost of post-quantum signatures on the wire.

Cloudflare plans to make standard MTC issuance free, run the service ACME-first, and build the issuance stack on a fork of Boulder, the open-source CA software maintained by Let's Encrypt, with independent mirroring cosignatures implemented on Azul. The GDN Online writeup of the announcement frames it as a push to make the trust layer less concentrated and to give site operators a quantum-ready path without forcing a costly rebuild.

Today's HTTPS certificates use RSA or elliptic-curve signatures that a sufficiently large quantum computer could, in principle, break. The cryptographic community expects such machines within years, though not on a settled date. Post-quantum signatures, which are typically larger and more expensive to verify, are being standardized and trialed now so the transition can happen before it is forced. Cloudflare's plan is to make the post-quantum transition opt-in rather than disruptive: site operators get a CA that issues quantum-resistant certificates on the same ACME workflow they already use, and they inherit trust from GlobalSign's existing root, which is already accepted by every major browser.

A new public CA run by a single company is not the same as a more distributed trust layer. The root-store admissions process is the real gatekeeper; until those programs accept Cloudflare's new CA, no browser will trust its certificates by default. Cloudflare has filed the applications, but acceptance timelines are not in the announcement, and root-store politics have delayed past entrants by years. The acquired GlobalSign root gets Cloudflare in the door on legacy clients faster, but it also means the new CA's classical compatibility depends on a third party's existing reputation, not a fresh design.

Cloudflare says it is designing the service so that no new tools are required, but its MTC engineering post qualifies that: clients must support ACME Renewal Information to benefit from the new path, and landmark-relative issuance only works for operators who actually receive authenticated tree heads. Broad deployment still needs ACME-RI support to land across the major ACME clients and hosting panels.

The most concrete signal that this is more than a corporate announcement is the alignment of timelines. Cloudflare has scheduled production MTC issuance for Q1 2027. Chrome, in a February 27, 2026 security roadmap, laid out its own MTC schedule: experimental traffic with classical certificate fallback running now, Q1 2027 bootstrapping, and Q3 2027 expansion. A public CA timeline and a browser-side timeline have not lined up like this before. The two programs now share a deadline, and that is the strongest evidence yet that post-quantum HTTPS is moving from specification to schedule.

The honest read is that the web is gaining a new public, transparent option for the trust layer, and that option is being designed to make post-quantum cryptography a default rather than a project. Whether it actually broadens the trust layer, or just adds one more well-funded vendor to the existing chokepoint, will be decided by the root programs over the next two quarters.