Adding a 2-QWAC is the low-risk way to get website identity (and Cloudflare is about to make it easier)
A 2-QWAC adds verified identity without touching your live HTTPS, unlike EV or 1-QWAC. Plus why Cloudflare's CA plans point to 2-QWACs.
Adding a 2-QWAC is the lowest-risk way to put verified business identity on your website. It sits alongside your existing TLS certificate (Let’s Encrypt, for example) rather than replacing it. If the 2-QWAC expires or its binding fails, your site keeps loading and only the identity information goes missing. An EV certificate or 1-QWAC can’t make that promise.
That’s the whole theme of this article: risk. Your current HTTPS certificate keeps encrypting traffic and keeping the lights on. The 2-QWAC answers a different question (which organisation stands behind this website?) without ever being on the critical path. We’ll also look at why Cloudflare’s move into the CA business makes 2-QWACs look like where things are heading.
The short version: low risk, because nothing gets replaced
A Qualified Website Authentication Certificate, or QWAC, provides authenticated information about a website or its operating organisation. A 2-QWAC is designed to provide that identity information alongside the certificate already handling HTTPS.
Encryption and organisational identity are separate jobs. Let’s Encrypt, for example, can keep handling the encrypted connection between a browser and your site, while a 2-QWAC provides an additional identity signal for a human or an agent without becoming the certificate that keeps the connection alive.
Imagine an ecommerce site already running behind Let’s Encrypt. The operator wants verifiable business identity for search and answer experiences, but doesn’t want to replace a working deployment simply to add it. A 2-QWAC lets the team keep the existing TLS workflow and add the identity layer separately.
The takeaway is straightforward: if uptime matters more than changing certificate architecture, keep the existing TLS certificate and add the 2-QWAC beside it. The guide to authentication certificates explains the wider terminology without making you decode a small alphabet soup first.
Why 1-QWAC and EV certificates carry more risk
The risk rises when an EV certificate or 1-QWAC becomes the certificate protecting the live website. Deployment then joins the availability chain. A configuration mistake, incomplete renewal, incorrect installation, or missed restart can affect whether visitors reach the site at all.
An EV certificate, or Extended Validation certificate, is a TLS certificate that includes stronger organisational validation than basic domain validation. A 1-QWAC is similarly used as the primary website authentication certificate. In both cases, the certificate sits directly in the path of the HTTPS connection.
That makes the 2-QWAC vs EV comparison partly an operations question. It isn’t only which certificate contains more identity information. It’s also which failure affects the checkout page at 2 a.m. on a Sunday.
For example, a team might renew a primary EV certificate but deploy the replacement to one load balancer rather than all of them. Some visitors see the new certificate, while others hit an expired one. A failed or expired EV or 1-QWAC renewal can break the website completely when the replacement isn’t correctly deployed.
With a 2-QWAC, the existing TLS path stays in place. The identity feature can fail without turning a certificate-management problem into an availability incident. Our QWAC and EV comparison goes deeper.
The 2-QWAC deployment model: leave the working TLS setup alone
The practical model is pleasantly boring. Keep Let’s Encrypt or another existing TLS provider responsible for HTTPS, then add the 2-QWAC through the supported identity workflow for your architecture.
Operators should expect to do three things:
- Record which certificate currently handles live HTTPS.
- Confirm how the 2-QWAC binds identity information to the website.
- Assign an owner for identity status, renewal, and failure alerts.
They don’t need to replace a working certificate merely because they want verifiable organisational identity, and they shouldn’t alter current TLS automation without a specific architectural reason. The safest deployment is the one that changes the fewest working parts.
For a site using Cloudflare, CloudFront, Netlify, or Vercel, the exact setup depends on the platform’s supported integration and the site’s certificate architecture. Check the deployment instructions before changing DNS, edge settings, or certificate automation. QWAC.com’s Cloudflare integration is one example of a managed deployment path.
For a typical rollout, first document the current HTTPS certificate and renewal owner. Next, add the identity layer without disabling existing automation. Finally, test two separate outcomes: normal HTTPS access and identity availability. They can fail separately, so check them separately.
Annual renewal beats a 47-day renewal treadmill
Renewal gets less dramatic when the calendar gives operators room to plan. The simple comparison: 2-QWAC certificates need annual renewal rather than renewal every 47 days.
A 47-day cycle creates repeated operational work. Teams must remember validation steps, watch automation, confirm deployment, and investigate failures several times a year. Even a well-run process creates more chances for a person, vendor, or integration to miss a handoff.
Annual QWAC renewal gives a platform team a cleaner planning window. Put the date into the same annual maintenance calendar as domain ownership checks, access reviews, and business-identity validation. Assign a named owner rather than leaving the task with “the web team,” a group that can include everyone and therefore nobody.
Annual does not mean set-and-forget. The organisation still needs to monitor expiry, confirm the binding, and check that the identity information remains available to the intended human or agent. A renewal task without an alert is a calendar decoration.
Consider a small agency managing several client sites. With a primary certificate, every failed 47-day renewal can become a client-facing outage. With a 2-QWAC, the agency can schedule renewal annually while leaving each client’s existing HTTPS automation untouched. That means fewer high-pressure changes, even though the agency still owns the task.
What happens when a 2-QWAC expires or its binding fails?
A 2-QWAC expiry or binding failure removes the identity information while the website continues operating normally. Visitors can still reach the site through the existing TLS layer, assuming that certificate and its own automation remain healthy.
A human or agent may no longer be able to verify the organisation through the QWAC. That matters for trust, automated decision-making, and any workflow that depends on identity data. Still, the blast radius is narrower than an expired primary EV or 1-QWAC certificate.
Picture a marketing site running on Let’s Encrypt. Its 2-QWAC expires during a holiday weekend. The site remains available, pages load, and HTTPS keeps working. The identity information is unavailable until the team restores the 2-QWAC. No checkout outage appears simply because the identity layer needs attention.
The same event involving a primary EV or 1-QWAC can produce a browser certificate error or prevent visitors from establishing the expected secure connection. One failure affects identity availability; the other can affect website availability.
Teams should still respond promptly. Record the incident, check whether the binding or certificate caused it, restore the identity signal, and verify it independently. A 2-QWAC reduces incident severity; it doesn’t make identity availability optional.
Cloudflare wants to be a CA, and that’s good news for 2-QWACs
On September 29, 2026, Cloudflare announced plans to become a public certificate authority. To get there, it agreed to acquire an established, publicly trusted root CA’s key material from GlobalSign, with the deal expected to close within two months of the announcement. It has also applied to the Chrome, Apple, Microsoft, and Mozilla root programs.
Why does a CDN buying a root matter for identity? Because Cloudflare already sits in front of a huge slice of the web. A company that runs the edge and can issue certificates itself is well placed to make certificate management something that quietly happens in the background, not a project that needs a calendar invite and a nervous engineer.
That’s the environment where the 2-QWAC shines. Identity becomes one more thing a platform can add beside the TLS it already manages, with no change to how your site is served. A model where identity is a separate, low-stakes layer fits that world better than one where you swap the certificate protecting every request.
Treat this as a reasoned read of the direction, not a promise. Cloudflare has not announced 2-QWAC products as part of this plan, and its CA hasn’t started issuing certificates yet. But as platforms take on more of the certificate lifecycle, the safest way to add verified identity is the one that leaves the live connection alone. That’s the 2-QWAC.
A practical operator’s checklist for choosing between 2-QWAC, 1-QWAC, and EV
Treat the decision as an architecture choice, not a branding contest. Start with the failure mode your business can tolerate.
| Option | Deployment position | Renewal cadence | Failure impact |
|---|---|---|---|
| 2-QWAC | Identity layer alongside existing TLS | Annual | Identity information becomes unavailable; the site continues operating normally |
| 1-QWAC | Primary website authentication certificate | Depends on certificate terms and process | A failed or expired renewal can break the website |
| EV certificate | Primary TLS certificate with organisational validation | Depends on certificate terms and process | A failed or expired renewal can break the website |
For an already-working website, the 2-QWAC is the sensible default. A primary EV or 1-QWAC makes sense only when the architecture or a specific requirement demands that certificate sit directly in the HTTPS path. The trade-off is clear: the 2-QWAC separates identity from the live connection, while a primary certificate can make identity availability part of uptime.
- Keep the current TLS certificate if a certificate change could threaten uptime.
- Choose a 2-QWAC when you need verifiable organisation identity without replacing the existing HTTPS workflow.
- Choose a primary EV or 1-QWAC only after testing deployment, rollback, monitoring, and renewal ownership.
- Assign one person or team to QWAC renewal and one escalation path for failures.
- Validate the architecture and your identity requirements before production deployment.
QWACs may support SEO and AEO use cases, but no certificate guarantees rankings, answer visibility, browser interface behaviour, or regulatory outcomes. Our page on QWACs for SEO and AEO is the sensible next stop for that part of the decision.
The takeaway: identity shouldn’t hold your website hostage
A 2-QWAC gives website operators a way to add verifiable business identity while the existing TLS layer keeps doing its HTTPS job. Let’s Encrypt can stay in place. Annual renewal replaces a 47-day cycle. An expired or unbound 2-QWAC removes identity information without taking the website offline.
That makes the 2-QWAC the natural fit for teams that care about uptime and still need clearer organisational identity for humans and agents, and Cloudflare’s CA plans suggest the wider ecosystem is moving the same way. Start by documenting the current certificate path, then check the supported deployment options for your platform.
Explore QWAC options, managed integrations, and QWAC pricing before assigning the renewal owner and moving into production.