Remember when half the web still ran on plain old http, and then browsers started slapping “Not Secure” warnings on any page without a padlock? Site owners grumbled. Certificates cost money and took effort. Then free, automated certificates showed up, the grumbling stopped, and encryption quietly became the default. Most people never noticed the switch happened at all.
Something similar is starting now, except this time the thing being defended against doesn’t fully exist yet.
On September 29, 2026, Cloudflare announced from San Francisco that it intends to become a public Certificate Authority. Not just any CA, either: it plans to issue quantum-safe TLS certificates, using a format called Merkle Tree Certificates. Production issuance of those certificates is scheduled for the first quarter of 2027. The service will run on an open-source platform, and Cloudflare is acquiring a trusted certificate root from GlobalSign so the new certificates are recognized from day one rather than waiting years for browser trust to accumulate.
If you write software, this is infrastructure news. If you use AI agents, it’s closer to home than it sounds.
What a certificate actually does for you
A TLS certificate is the thing that makes the padlock appear. It does two jobs. It proves that the site you’re talking to is really that site, and it sets up the encryption that keeps the conversation private on the way there.
The proof part depends on math. A Certificate Authority signs the certificate with a cryptographic signature, and your browser checks that signature. Today’s signatures are built on problems that regular computers find impractically hard to solve. A sufficiently capable quantum computer would find some of those same problems much easier. Post-quantum cryptography swaps in math that quantum machines are widely believed to struggle with just as much as classical ones.
Cloudflare says its CA will issue both traditional and post-quantum certificates. That dual approach matters, because the web can’t flip a switch. Old clients need the certificates they already understand, and new clients need the ones designed for what’s coming.
Why this lands differently in the age of AI agents
Here’s where my corner of the internet comes in. When you browse, you’re one person making a handful of connections, and you can glance at the address bar if something feels off. An AI agent working on your behalf behaves nothing like that.
An agent booking travel, reconciling invoices, or monitoring a dozen dashboards opens connection after connection, often to services you never personally visited. It has no eyes and no instinct. It can’t notice that a domain looks slightly wrong. The only thing standing between your agent and an impostor server is the certificate check, performed automatically, thousands of times, with no human in the loop.
That changes the stakes in two ways.
Trust becomes fully mechanical
Agents delegate judgment to cryptography. If the signature verifies, the agent proceeds. There’s no second opinion. So the strength of that signature scheme is the whole of the security story, not one layer among several.
Handshake overhead stops being trivia
Every secure connection starts with a handshake, and certificates travel across the wire during it. Post-quantum signatures are generally larger than what we use today, which is precisely the problem Merkle Tree Certificates are designed around. Cloudflare’s stated aim with MTCs is quantum-safe TLS that stays fast. For a human clicking one link, a few extra kilobytes wouldn’t register. For an agent doing hundreds of handshakes in a workflow, overhead compounds into real latency and real cost.
Why 2027 is the point, not the delay
A reasonable reaction is: nobody has a quantum computer that can break TLS today, so why bother now?
Because encrypted traffic can be recorded now and decrypted later. Anything captured today with long-term value, like medical records, legal correspondence, or source code, stays sensitive for years. And certificate ecosystems move slowly. Roots need trust, software needs updates, operators need time to migrate. Buying an established root from GlobalSign is Cloudflare skipping the slowest part of that timeline on purpose.
Doing this in the open, on an open-source platform, is the other notable choice. Certificate authorities are load-bearing for the entire web, and the ones that have earned the most goodwill are the ones that let outsiders inspect how they work.
What this means for you
Practically speaking, almost nothing you need to do. You won’t configure a Merkle Tree Certificate, and your agents won’t ask your permission to use one. The padlock will look exactly the same.
What’s useful is knowing the shape of it. As you hand more decisions to automated systems, the quality of the plumbing underneath them becomes your security posture, whether you think about it or not. Announcements like this one are worth tracking, not because you’ll touch the technology, but because they tell you whether the ground your agents walk on is being maintained.
The http-to-https migration felt like a chore while it happened and like obvious common sense afterward. This one will probably follow the same arc. The best version of a security upgrade is the one you never notice, because someone started on it early.
🕒 Published: