Root certificate · Sectigo
AAA Certificate Services
AAA Certificate Services is a root CA certificate operated by Sectigo (RSA 2048, valid until 2028-12-31, SHA-256 D7A7A0FB). As of the latest CCADB data it is trusted for TLS server authentication by 2 of 4 major root stores: Apple, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Removed Removed | No | — | No |
| Mozilla | Included Included | No | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | No |
The CCADB lists EV policy OID 2.23.140.1.3, 1.3.6.1.4.1.6449.1.2.1.5.1 for this root, but Mozilla does not mark it as EV-enabled.
Removed Chrome
- Status
- Removed
Included Mozilla
- Status
- Included
- Trust bits
- EV policy OIDs
- not EV-enabled
- First included in
- Firefox 1
- Inclusion bug
- #249710
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth, emailProtection
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client Authentication, Code Signing, Encrypting File System, IP Security Tunnel Termination, IP Security User, Secure Email, Time Stamping
"Trusted for TLS" means the store includes the root with the server-authentication trust bit (Mozilla "Websites", Apple serverAuth, Microsoft Server Authentication EKU). Microsoft "NotBefore" means only certificates issued before a cutoff date are still trusted. "Constrained" means the store applies extra restrictions.
Details
- CA owner
- Sectigo
- Subject
- CN=AAA Certificate Services,O=Comodo CA Limited,L=Salford,ST=Greater Manchester,C=GB
- SHA-256
D7A7A0FB5D7E2731D771E9484EBCDEF71D5F0C3E0A2948782BC83EE0EA699EF4- SHA-1 (Windows thumbprint)
D1EB23A46D17D68FD92564C2F1F1601764D8E349- SPKI SHA-256
BD153ED7B0434F6886B17BCE8BBE84ED340C7132D702A8F4FA318F756ECBD6F3- Valid from
- 2004-01-01
- Expires
- 2028-12-31
- Key
- RSA 2048
- Signature algorithm
- sha1WithRSAEncryption
- Serial number
1- Country
- GB
- Trust bits (CCADB)
- Server Authentication, Client Authentication, Code Signing, Secure Email, Encrypting File System, Time Stamping, IP Security Tunnel Termination, IP Security User
- EV policy OIDs (CCADB)
- 2.23.140.1.3, 1.3.6.1.4.1.6449.1.2.1.5.1 · TLS EV capable: Yes
- Test websites
- valid:
https://aaacertificateservices.comodoca.com/· expired:https://aaacertificateservices.comodoca.com:442/· revoked:https://aaacertificateservices.comodoca.com:444/ - CCADB record
- A000069
- PEM
- sectigo-aaa-certificate-services.pem
Intermediate CAs issued by this root
The CCADB lists 95 intermediate CA certificates signed directly by AAA Certificate Services: 53 currently valid, 8 expired and 34 revoked (revoked includes those whose parent was revoked). 3 of the valid ones run past the expiry date of the root itself (2028-12-31).
Showing 20 of 95: valid certificates first, newest first. Each name links to its crt.sh entry by SHA-256; an arrow marks a cross-certificate for another root on this site.
Cross-signed versions
No certificate in the CCADB has the same subject and public key as AAA Certificate Services with a different issuer, so a client has to carry AAA Certificate Services itself in its root store to trust it.
CRL and OCSP addresses
In the root certificate
- CRL:
http://crl.comodoca.com/AAACertificateServices.crl - CRL:
http://crl.comodo.net/AAACertificateServices.crl
Full CRL this CA publishes (CCADB)
http://crl.comodoca.com/AAACertificateServices.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 53 valid intermediates signed by AAA Certificate Services; the number in brackets is how many of them use each address.
- CRL:
http://crl.comodoca.com/AAACertificateServices.crl(53) - OCSP:
http://ocsp.comodoca.com(53)
What happens when it expires
AAA Certificate Services is valid until 2028-12-31, about 2.1 years after this data snapshot (2026-11-10). From that day, browsers and operating systems that check trust-anchor expiry stop accepting chains that end at this root, so any certificate that can only chain to it fails validation. Android is a known exception: it does not enforce the expiry date of trust anchors. 3 of its valid intermediates expire later than the root, so their operators need another path, such as a cross-sign from a newer root, before 2028-12-31.
Check whether your device trusts it
Each platform keeps its own root store. The commands below look up AAA Certificate Services by common name (AAA Certificate Services) or fingerprint. The store status in each heading comes from the CCADB snapshot; your device can differ if it is out of date or managed by an administrator.
macOS (Apple store: Included · Trusted for TLS)
Search the system roots keychain by common name. -Z prints the SHA-256 hash, which must match the fingerprint on the last line.
security find-certificate -a -c "AAA Certificate Services" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: D7A7A0FB5D7E2731D771E9484EBCDEF71D5F0C3E0A2948782BC83EE0EA699EF4Windows (Microsoft store: Included · Trusted for TLS)
Windows identifies roots by SHA-1 thumbprint. It installs third-party roots on demand through Automatic Root Certificates Update, so "not found" can also mean the root has not been needed yet; certutil -generateSSTFromWU roots.sst downloads Microsoft's full list.
certutil -verifystore Root D1EB23A46D17D68FD92564C2F1F1601764D8E349Linux (ca-certificates follows Mozilla: Included)
Debian, Ubuntu, Fedora and RHEL build their ca-certificates package from Mozilla's root store. Use trust list on p11-kit systems, or search the PEM bundle on Debian and Ubuntu.
# Fedora / RHEL / Arch (p11-kit)
trust list --filter=ca-anchors | grep -iF -A2 "AAA Certificate Services"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "AAA Certificate Services"Java
Java ships its own cacerts keystore; JDK 9 and later accept -cacerts and the default store password is changeit. Search for the SHA-256 fingerprint in colon form.
keytool -list -cacerts -storepass changeit | grep -i "D7:A7:A0:FB:5D:7E:27:31:D7:71:E9:48:4E:BC:DE:F7:1D:5F:0C:3E:0A:29:48:78:2B:C8:3E:E0:EA:69:9E:F4"Android
Android's system store is maintained by Google separately from the four CCADB stores above. Open Settings → Security & privacy → More security settings → Encryption & credentials → Trusted credentials → System (menu names vary by vendor and version) and look for Comodo CA Limited → AAA Certificate Services.
Which root does my site chain to?
List the chain your server sends and compare the last issuer with this root; the fingerprint check confirms a local copy.
# show subject (s:) and issuer (i:) of every certificate the server sends
openssl s_client -connect example.com:443 -servername example.com -showcerts </dev/null 2>/dev/null \
| grep -E '^ *[0-9]+ s:|^ *i:'
# subject and SHA-256 fingerprint of the downloaded PEM file
openssl x509 -in sectigo-aaa-certificate-services.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=D7:A7:A0:FB:5D:7E:27:31:D7:71:E9:48:4E:BC:DE:F7:1D:5F:0C:3E:0A:29:48:78:2B:C8:3E:E0:EA:69:9E:F4FAQ
Is AAA Certificate Services trusted by Chrome, Firefox, Safari and Windows?
As of 2026-11-10, Apple, Microsoft trust it for TLS server authentication; Chrome, Mozilla do not.
When does AAA Certificate Services expire?
On 2028-12-31, about 2.1 years after the 2026-11-10 data snapshot. 3 of the valid ones run past the expiry date of the root itself (2028-12-31).
How many intermediate certificates has AAA Certificate Services issued?
The CCADB lists 95: 53 valid, 8 expired and 34 revoked. The newest valid one is SSL.com TLS RSA Root CA 2022, valid until 2028-12-31.
Is AAA Certificate Services cross-signed?
No. The CCADB has no certificate with the same subject and public key signed by another CA.
Other roots from Sectigo
- COMODO Certification Authority RSA 2048 · 2029-12-31
- COMODO Certification Authority RSA 2048 · 2030-12-31
- COMODO ECC Certification Authority ECDSA P-384 · 2038-01-18
- COMODO RSA Certification Authority RSA 4096 · 2038-01-18
- Entrust Root Certification Authority RSA 2048 · 2026-11-27
- Entrust Root Certification Authority - EC1 ECDSA P-384 · 2037-12-18
- Entrust Root Certification Authority - G2 RSA 2048 · 2030-12-07
- Entrust Root Certification Authority - G4 RSA 4096 · 2037-12-27
- Entrust.net Certification Authority (2048) RSA 2048 · 2029-07-24
- Sectigo Public Server Authentication Root E46 ECDSA P-384 · 2046-03-21
- Sectigo Public Server Authentication Root R46 RSA 4096 · 2046-03-21
- USERTrust ECC Certification Authority ECDSA P-384 · 2038-01-18
- USERTrust RSA Certification Authority RSA 4096 · 2038-01-18
Sources
- CCADB — Resources (TLS Server Authentication report, All Included Root Certificate Trust Bit Settings)
- CCADB — All Certificate Information (root and intermediate), CSV V5
- CCADB — Mozilla Included CA Certificate Report
- CCADB — Chrome / Mozilla / Apple / Microsoft TLS Server Authentication CSV