We use privacy-by-default, cookieless analytics.

Optional analytics cookies are used only if you accept them.

Read our Terms of Use and Privacy Policy.

FAQEU eIDAS

What is a QWAC under eIDAS?

A QWAC is a qualified certificate for website authentication: it links a website to the natural or legal person named in the certificate and must be issued by a qualified trust service provider under eIDAS.

This FAQ helps separate the legal qualified-certificate status from ordinary TLS deployment, trusted-list checks, browser recognition duties, and the evidence needed before relying on a QWAC.

Back to main artifactReview sources
Author
Sorena AI
Published
May 9, 2026
Updated
Jul 25, 2026
Questions
3

Structured answer sets in this page tree.

Primary sources
14

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated Jul 25, 2026
Overview

Under eIDAS, a is a qualified , issued by a and containing the identity, domain, validity, issuer-signature, and status-service information required for that certificate type. An ordinary website TLS certificate does not gain QWAC status from a compliance label.

Search this module

Find a question or answer quickly

3 of 3 questions
Question 1

What does a QWAC prove under eIDAS?

A makes it possible to authenticate a website and link that website to the natural or legal person to whom the certificate is issued. A adds the eIDAS qualified layer: the certificate must be issued by a and meet Annex IV requirements.

A working TLS connection does not complete the check. The evidence should show who the certificate identifies, which domain names are covered, which issued it, and where relying parties can check certificate validity or revocation status.

  • Confirm that the certificate is explicitly indicated as a qualified .
  • Check that the subject identity, address elements, and domain names match the website or service being authenticated.
  • Record the certificate validity period, serial or certificate identity code, issuer, and status-service location.
  • Treat evidence as website identity evidence, not as proof that the whole transaction, application, or message payload has been sealed or signed.

What is a under the EU eIDAS Regulation?

A is a qualified . eIDAS defines it as a website-authentication certificate issued by a that meets Annex IV. It links the website to the named natural or legal person and carries required certificate information such as qualified-certificate indication, issuer identity, subject identity, domain names, validity period, certificate identity code, issuer signature or seal, and certificate-status service information.

Is a the same as an ordinary TLS certificate?

No. A can be used in the website-authentication context, but its eIDAS significance comes from qualified status, the , and Annex IV content. A normal TLS certificate may secure a connection without being a qualified under eIDAS.

Citations
Question 2

How should a relying party validate a QWAC?

Validation should combine certificate checks with eIDAS status checks. First confirm that the issuer and service are qualified for the relevant trust service on an EU , because eIDAS allows a to provide a qualified trust service after qualified status appears in the trusted lists.

Then validate the certificate itself: domain match, certificate chain, validity period, certificate-status endpoint, revocation status, and the -specific qualified-certificate statements. eIDAS requires qualified trust service providers issuing qualified certificates to publish revocation status and provide validity or revocation information to relying parties.

  • Use the EU and national trusted-list information to confirm the QTSP and qualified service status.
  • Check the website domain against the certificate's domain-name information before treating it as the authenticated endpoint.
  • Use the certificate validity-status service, such as the CRL or OCSP location identified in the certificate profile, before relying on the certificate.
  • Keep validation logs that show the certificate examined, trusted-list result, revocation or validity status, validation time, and any exception decision.

Where do EU trusted lists fit into validation?

Trusted lists are the source for and qualified service status. eIDAS requires Member States to establish, maintain, and publish trusted lists for the qualified trust service providers and qualified trust services for which they are responsible. A review should therefore verify both the certificate contents and the issuer/service status shown through the trusted-list framework.

What records should a team keep after validating a ?

Keep the certificate or fingerprint, covered domain names, issuer and QTSP name, trusted-list status result, validation timestamp, revocation or validity-status result, renewal or expiry date, and the system or website that relied on the certificate. Those records make later renewal, incident, and relying-party reviews traceable.

Citations
ETSI TS 119 612 - Trusted Lists

Specifies trusted-list structure and service information used by validators to interpret qualified trust service provider and qualified service status.

Question 3

What changed for browsers and QWACs under eIDAS 2?

The eIDAS 2 amendments add browser-facing duties for qualified certificates for website authentication. Providers of web browsers must recognise QWACs issued in accordance with Article 45 and display the identity data and additional attested attributes in a user-friendly way. The small-enterprise exception applies only to the support and interoperability duty.

That browser rule should not be read as a guarantee that every deployed browser, user interface, certificate store, or relying-party application already presents identity information in the same way. For implementation work, keep the distinction clear: the certificate may satisfy eIDAS QWAC requirements, while browser support and display behaviour are separate deployment and interoperability checks.

Commission Implementing Regulation (EU) 2025/2527 is in force but applies from 6 January 2027. It sets different reference standards for QWACs used for TLS authentication outside a web-browser and for other QWACs, including browser contexts. Before that application date, do not present those listed 2025 standards as already mandatory under the implementing regulation.

  • For website owners, confirm whether the intended browser and client environment recognises and displays the identity information needed for the user journey.
  • For relying-party systems, do not rely on browser display alone; keep machine-readable validation evidence for issuer, service status, certificate status, and domain match.
  • For incidents, remember that eIDAS allows browser precautionary measures only for substantiated concerns about security breaches or loss of integrity of an identified certificate or set of certificates.
  • For procurement, ask certificate providers how the profile, trusted-list status, revocation publication, and renewal process will be evidenced.

Does eIDAS require browsers to recognise QWACs?

Yes, Article 45 as amended requires providers of web browsers to recognise qualified certificates for website authentication issued in accordance with Article 45 and to display attested identity data and additional attested attributes in a user-friendly manner. The limited exception for microenterprises and small enterprises during their first five years as providers of web-browsing services applies to the support and interoperability duty.

Can a replace an electronic seal or signature under eIDAS?

No. A authenticates a website endpoint and links it to the named person or legal entity. It is not the same artifact as a qualified electronic seal or qualified electronic signature, which are used for different eIDAS trust-service purposes and evidence models.

Citations
Recommended next step

Turn QWAC validation into a reusable evidence pack

Sorena can help structure QWAC checks around the certificate, QTSP trusted-list status, revocation evidence, browser assumptions, and renewal ownership without treating a normal TLS certificate as eIDAS-qualified.

Research workflow
Open Research Copilot for eIDAS

Ask questions tied to cited sources about QWACs, qualified trust service providers, trusted lists, and validation evidence using the cited sources on this page.

Explore next step
Talk to Sorena
Review a QWAC workflow

Check whether your website-authentication process separates certificate deployment, qualified status, trusted-list evidence, revocation checks, and browser assumptions.

Explore next step
Primary sources

References and citations

ETSI EN 319 412-4 - certificate profile for website authentication
etsi.org
Referenced sections
  • Explains the website-certificate profile for TLS-accessed websites, useful for distinguishing website authentication from other eIDAS certificate purposes.
"certificate profile for web site certificates that are accessed by the TLS protocol"
ETSI EN 319 412-4 - website certificate profile
etsi.org
Referenced sections
  • Technical profile source for website certificates accessed through TLS, used to explain the website-authentication layer without treating QWAC as a substitute for seals or signatures.
"Certificate profile for web site certificates"
ETSI EN 319 412-5 - certificate type QCStatement
etsi.org
Referenced sections
  • Supports the distinction between website-authentication certificates, electronic-signature certificates, and electronic-seal certificates through certificate-type QCStatements.
"electronic signature, electronic seal or web site authentication"
ETSI EN 319 412-5 - QCStatements
etsi.org
Referenced sections
  • Technical certificate-profile source mapping eIDAS Annex IV QWAC requirements to certificate fields and QCStatements.
"EU qualified certificates for website authentication"
ETSI EN 319 412-5 - QCStatements for EU qualified certificates
etsi.org
Referenced sections
  • Maps eIDAS Annex IV QWAC requirements to certificate-profile fields, including qualified-certificate indication, subject identity, domain names, validity, serial number, and status-service locations.
"Mapping with Annex IV of Regulation (EU) No 910/2014"
ETSI TS 119 612 - Trusted Lists
etsi.org
Referenced sections
  • Specifies trusted-list structure and service information used by validators to interpret qualified trust service provider and qualified service status.
"Trusted Lists"
Regulation (EU) No 910/2014 (eIDAS)
eur-lex.europa.eu
Referenced sections
  • Primary legal source for QWAC definitions, Annex IV content, trusted lists, QTSP qualified status, and certificate validity or revocation-status duties.
"qualified certificate for website authentication"
Related guides

Explore more topics

eIDAS 2 deadlines and compliance calendar for EUDI Wallet and trust services
eIDAS 2 calendar separating binding EUDI Wallet, reporting, and trust-service dates from implementation milestones and technical programme updates.
eIDAS 2.0 vs eIDAS: EUDI Wallet and trust-service changes
Compare the original eIDAS electronic identification and trust-service framework with the eIDAS 2.0 amendments for EUDI Wallets, relying parties, attestations, QWACs, and supervision.
eIDAS Certificates and Authentication: qualified certificates, QWACs, and validation checks
Official source guide to eIDAS qualified certificates, website authentication certificates, trusted lists, relying-party checks, and validation evidence.
eIDAS checklist and evidence pack for trust services, signatures, and EUDI Wallet relying parties
Build an eIDAS evidence pack for qualified trust services, electronic signatures, trusted-list checks, certificate validation, supervisory records, and EUDI Wallet relying-party controls.
eIDAS compliance guide for trust services, QTSPs, signatures, and EUDI Wallet relying parties
Official source eIDAS compliance guide for trust-service classification, QTSP supervision evidence, qualified signatures, seals, time stamps, certificates, trusted-list validation, and EUDI Wallet relying-party records.
eIDAS electronic signatures: SES, AES, QES legal effect and evidence
An official source guide to eIDAS electronic-signature legal effect: SES, AES, QES, qualified certificates, QTSP trusted-list checks, validation, recognition, and evidence records.
eIDAS penalties and fines for trust service providers
Guide to eIDAS Article 16 fine floors, national penalty rules, supervisory action, qualified-status withdrawal, and trusted-list evidence.
eIDAS QES validation checks for relying parties
How to validate a qualified electronic signature under eIDAS: certificate, QTSP, trusted-list, QSCD, integrity, validation result, and evidence records.
eIDAS Qualified Trust Services: QTSP Selection
How to select an EU eIDAS qualified trust service provider: identify the qualified service type, verify trusted-list status, review supervision evidence, and retain certificate-policy records.
eIDAS remote signature and cloud HSM controls for QTSPs
Source-grounded guide to eIDAS remote signature controls: remote QSCD scope, server-side signing, QTSP evidence, signer authentication, certificate validation, and trusted-list checks.
eIDAS signature legal effect selector: SES, AES, AES-QC, or QES
Compare eIDAS signature levels by legal effect, governing form rules, qualified certificate status, QTSP evidence, QSCD use, validation, and public-service recognition.
eIDAS trust service role scoping workflow: TSP, QTSP, validator, relying party, or QTSP customer
Classify an eIDAS role by evidence: trust service provider, qualified trust service provider, signature or seal validator, EUDI Wallet relying party, relying party, or customer of a QTSP.
eIDAS trusted list validation: LOTL, QTSP status, and evidence
How to validate EU eIDAS trusted-list evidence: start from the Commission LOTL, confirm QTSP and qualified-service status, check certificate path and revocation data, and retain validation reports.
eIDAS vs ESIGN and UETA: EU qualified signatures vs U.S. e-signature laws
Compare eIDAS with ESIGN and UETA for electronic signatures, qualified certificates, trust services, cross-border recognition, validation evidence, and source gaps.
eIDAS vs ETSI EN 319 401: legal supervision and TSP policy requirements
Compare eIDAS and ETSI EN 319 401 for trust services: legal scope, QTSP supervision, conformity assessment, audits, incident evidence, and operational controls.
eIDAS vs GDPR for identity data: wallet, trust-service, and privacy obligations
Compare eIDAS identity, trust-service, and EUDI Wallet rules with GDPR duties for personal-data processing, minimisation, lawful basis, evidence, security, and user rights.
eIDAS vs NIS2 for trust service providers: QTSP and cybersecurity obligations
Compare eIDAS trust-service and QTSP duties with NIS2 cybersecurity risk-management, incident reporting, supervision, and evidence duties for trust service providers.
Electronic Attestations of Attributes under EU eIDAS: EAA, QEAA, issuers, wallets, and validation
Official source guide to electronic attestations of attributes under amended EU eIDAS: EAA, QEAA, public-sector authentic-source attestations, wallet use, issuer checks, relying-party validation, revocation, and legal effect.
EU eIDAS Applicability Test for Trust Services, Wallets, and Certificates
An official source eIDAS scope test for QTSPs, trust services, electronic signatures, seals, timestamps, QWACs, EUDI Wallet relying parties, and cross-border recognition evidence.
EU eIDAS attribute attestations: EAA, QEAA, wallet, and relying party checks
What electronic attestations of attributes mean under eIDAS, how QEAAs differ from public-sector and non-qualified attestations, and what issuers, wallets, and relying parties should verify.
EU eIDAS checklist for signatures, trust services, and wallets
Checklist for eIDAS trust-service and EUDI Wallet controls: qualified status, trusted lists, certificates, signatures, seals, timestamps, validation evidence, and relying-party records.
EU eIDAS FAQ: signatures, QTSPs, trusted lists, QWACs, wallets, and validation
FAQ on eIDAS trust services and the European Digital Identity framework, covering advanced and qualified electronic signatures, QTSP status, trusted lists, QWACs, EUDI Wallet relying parties, attestations of attributes, and validation evidence.
EU eIDAS QTSP authorization and supervision guide
How qualified trust service providers obtain and keep qualified status under eIDAS, including conformity assessment reports, supervision, trusted lists, incidents, and evidence.
EU eIDAS QTSP Due Diligence Workflow for Trusted Lists, Certificates, and Evidence
Check a qualified trust service provider under eIDAS by validating trusted-list status, qualified service scope, certificates, policies, supervision, audits, and retained evidence.
EU eIDAS Requirements for Trust Services, Signatures, Seals, Wallets, and Evidence
Official source guide to core eIDAS requirements for trust service providers, qualified trust services, electronic signatures, seals, time stamps, trusted lists, and EUDI Wallet relying parties.
EU eIDAS Trusted Lists FAQ: LOTL, QTSP status, and validation evidence
How EU eIDAS Trusted Lists and the Commission LOTL support QTSP and qualified trust-service validation, with practical evidence checks for relying parties.
EUDI Wallet readiness for service providers under eIDAS
Readiness guide for organisations preparing to request or verify data from European Digital Identity Wallets: roles, registration, ARF alignment, selective disclosure, implementing acts, and evidence.
EUDI Wallet Relying Parties under eIDAS
What EUDI Wallet relying parties must do under eIDAS, when the harmonised registration rules apply, and how to control requested data, identification, validation, and evidence.
EUDI Wallet Relying Party Onboarding Workflow under eIDAS
Prepare an eIDAS wallet-relying-party registration, intended-use record, access-certificate controls, attribute request, validation evidence, and intermediary safeguards.
EUDI Wallet Relying Party Registration Under eIDAS
What eIDAS Article 5b and the EUDI Wallet ARF say about wallet relying party registration, intended uses, attribute requests, certificates, evidence, and Member State gaps.
EUDI Wallet Technical Architecture Guide under eIDAS
Technical guide to the EUDI Wallet architecture: ARF roles, wallet units, PID and attestations, relying parties, trust model, certificates, protocols, privacy, and security controls.
QES vs AdES under EU eIDAS: legal effect, certificates, QTSPs, and validation evidence
Compare qualified electronic signatures (QES) and advanced electronic signatures (AdES) under EU eIDAS, including legal effect, qualified certificates, QTSP status, QSCDs, and validation evidence.
QWACs under eIDAS: website authentication certificates
A source-grounded guide to qualified website authentication certificates under eIDAS, covering Annex IV data, trusted lists, browser recognition, validation evidence, and QTSP checks.
What eIDAS Covers: eID, Trust Services, EUDI Wallet, and QWACs
A source-grounded guide to the systems and services covered by EU eIDAS: notified electronic identification, trust services, signatures, seals, time stamps, registered delivery, website authentication, trusted lists, the EUDI Wallet, and attribute attestations.
What is a qualified trust service provider under eIDAS?
How to verify QTSP status under eIDAS using the qualified service, supervisory body decision, trusted list entry, conformity assessment evidence, and service-specific records.