ABOUT QWACS / THE BUSINESS BEHIND THE WEBSITE

What is a QWAC?
Your website’s
verified business ID.

A Qualified Website Authentication Certificate connects your website to a real, independently verified organization.

The SSL lock tells you the connection is secure. A QWAC helps people and AI agents see who’s on the other end.

Get to know website identity
QUALIFIED WEBSITE IDENTITY
CERTIFICATE ISSUED TOYour Company Ltd.your-website.com
Registration number
123-45-6789
Registered location
Paris, France
VERIFIED BYVerification Authority Ltd.

Who created QWACs?

The European Union established the QWAC framework in 2014, but its reach is global. QWACs can be issued to businesses around the globe that meet a qualified provider’s verification requirements.

Those providers check your organization and its connection to the domain, under government supervision. The framework dates to 2014; broad support across major browsers arrived in 2026.

2014EU framework established
2026Broad browser support
THE FRAMEWORKEuropean UnionCommon rules for trusted website identity, valid for global businesses
THE VERIFICATIONA qualified providerChecks your organization and website
THE RESULTYour QWACA signed identity that can be checked

Which browsers support QWACs?

In 2026, Chrome, Firefox, and Safari support QWACs, bringing verified website identity into the browser.

Chrome

Firefox

Safari

And the browsers used by agents? Modern “headless” Chrome shares Chrome’s browser capabilities. It runs without a visible window, giving browser-based agents access to the same certificate-verification foundation.

How can an agent
verify my website’s identity?

An agent can use its browser and certificate-inspection tools to examine the signed identity attached to your website, then compare it with the business it expects.

  1. 1

    Visit the website

    The browser connects securely and finds the QWAC, served with SSL or linked alongside it.

  2. 2

    Check the evidence

    Verification checks the signature, validity, qualified issuer, and link to this website.

  3. 3

    Identify the business

    The agent can examine the legal name, registration details, location, and verifying authority.

See why identity matters for SEO & AEO

How is a QWAC different
from SSL, OV, or EV?

SSL secures the connection. OV and EV add organization checks to an SSL certificate. A QWAC adds qualified status under EU rules—and can also provide identity separately from your SSL certificate.

No business identity

SSL only

SECURE CONNECTION

Encrypts the connection and confirms control of the domain. The business behind it remains unidentified.

Good

OV

VERIFIED ORGANIZATION

Organization Validation adds a checked business name to your SSL certificate.

Better

EV

EXTENDED VALIDATION

Extended Validation adds more extensive checks of the organization, its legal existence, and the applicant’s authority.

Best for qualified identity

QWAC

QUALIFIED IDENTITY

Identity proof from a government-supervised qualified trust service provider, recognized through the EU’s trusted lists.

Explore the full certificate comparison

How can I deploy a QWAC?

Get your certificate from a qualified provider, then choose how to serve it. QWAC.com helps connect your issuer, your hosting, and your certificate lifecycle.

SSL certificateSecure connectionQWACVerified organizationyour-website.com
Two certificates. Independent lifecycles.

Alongside your existing SSL

Keep your SSL setup. Publish a separate QWAC with a signed link to your SSL certificate. Each can renew on its own schedule.

SSL certificateSecure connectionQWAC identityYour verified organizationyour-website.com
One certificate. Encryption and identity together.

Together in one certificate

Install a QWAC that also serves as your SSL certificate, through your hosting provider. Encryption and verified identity travel together.

Choose your issuer. Connect your host. Keep your identity current.Find your hosting guide
A REAL BUSINESS. A VERIFIABLE WEBSITE.

Give your website an identity.

Get started
Sources & browser documentation