Root certificate · ANCE (Tunisia)
TunTrust Root CA
TunTrust Root CA is a root CA certificate operated by ANCE (Tunisia) (RSA 4096, valid until 2044-04-26, SHA-256 2E44102A). As of the latest CCADB data it is trusted for TLS server authentication by 3 of 4 major root stores: Chrome, Mozilla, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Included Included | Yes | — | No |
| Mozilla | Included Included | Yes | — | No |
| Apple | Not included Not included | No | — | No |
| Microsoft | Included Included | Yes | — | No |
The CCADB lists no EV policy OID for TunTrust Root CA.
Included Chrome
- Status
- Included
Included Mozilla
- Status
- Included
- Trust bits
- Websites
- EV policy OIDs
- not EV-enabled
- First included in
- NSS 3.71 / Firefox 94
- Inclusion bug
- #1587779
Not included Apple
- Status
- Not included
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client Authentication
"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
- Agence Nationale de Certification Electronique
- Subject
- CN=TunTrust Root CA,O=Agence Nationale de Certification Electronique,C=TN
- SHA-256
2E44102AB58CB85419451C8E19D9ACF3662CAFBC614B6A53960A30F7D0E2EB41- SHA-1 (Windows thumbprint)
CFE970840FE0730F9DF60C7F2C4BEE2046349CBB- SPKI SHA-256
C942262C0C7C0A95BB152B71C42556DDBE9A04FA8378373550D2B7CE27D952A3- Valid from
- 2019-04-26
- Expires
- 2044-04-26
- Key
- RSA 4096
- Signature algorithm
- sha256WithRSAEncryption
- Serial number
1302D5E2404C92468616675DB4BBBBB26B3EFC13- Country
- TN
- Trust bits (CCADB)
- Server Authentication, Client Authentication
- EV policy OIDs (CCADB)
- not EV-enabled · TLS EV capable: No
- Test websites
- valid:
https://validovssl.tuntrust.tn· expired:https://expiredovssl.tuntrust.tn· revoked:https://revokedovssl.tuntrust.tn - CCADB record
- A006586
- PEM
- ance-tunisia-tuntrust-root-ca.pem
Intermediate CAs issued by this root
The CCADB lists 3 intermediate CA certificates signed directly by TunTrust Root CA: 2 currently valid, 0 expired and 1 revoked (revoked includes those whose parent was revoked).
Showing 3 of 3: 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.
| Intermediate | Operated by | Expires | Status |
|---|---|---|---|
| TunTrust Services CA | Agence Nationale de Certification Electronique | 2039-04-26 | Valid |
| TunTrust Root CA → TunTrust Root CA | Agence Nationale de Certification Electronique | 2044-04-18 | Valid |
| TunTrust Qualified CA | Agence Nationale de Certification Electronique | 2039-04-26 | Revoked |
Cross-signed versions
No certificate in the CCADB has the same subject and public key as TunTrust Root CA with a different issuer, so a client has to carry TunTrust Root CA itself in its root store to trust it.
CRL and OCSP addresses
In the root certificate
TunTrust Root CA itself contains no CRL Distribution Points and no OCSP (Authority Information Access) extension. That is normal for a root: clients trust it directly and do not check its own revocation status.
Full CRL this CA publishes (CCADB)
http://crl.tuntrust.tn/tntrustrootca.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 2 valid intermediates signed by TunTrust Root CA; the number in brackets is how many of them use each address.
- CRL:
http://crl.tuntrust.tn/tntrustrootca.crl(1) - OCSP:
http://va.tuntrust.tn(1)
What happens when it expires
TunTrust Root CA is valid until 2044-04-26, about 17.5 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.
Check whether your device trusts it
Each platform keeps its own root store. The commands below look up TunTrust Root CA by common name (TunTrust Root CA) 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: Not included)
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 "TunTrust Root CA" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 2E44102AB58CB85419451C8E19D9ACF3662CAFBC614B6A53960A30F7D0E2EB41Windows (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 CFE970840FE0730F9DF60C7F2C4BEE2046349CBBLinux (ca-certificates follows Mozilla: Included · Trusted for TLS)
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 "TunTrust Root CA"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "TunTrust Root CA"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 "2E:44:10:2A:B5:8C:B8:54:19:45:1C:8E:19:D9:AC:F3:66:2C:AF:BC:61:4B:6A:53:96:0A:30:F7:D0:E2:EB:41"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 Agence Nationale de Certification Electronique → TunTrust Root CA.
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 ance-tunisia-tuntrust-root-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=2E:44:10:2A:B5:8C:B8:54:19:45:1C:8E:19:D9:AC:F3:66:2C:AF:BC:61:4B:6A:53:96:0A:30:F7:D0:E2:EB:41FAQ
Is TunTrust Root CA trusted by Chrome, Firefox, Safari and Windows?
As of 2026-11-10, Chrome, Mozilla, Microsoft trust it for TLS server authentication; Apple do not.
When does TunTrust Root CA expire?
On 2044-04-26, about 17.5 years after the 2026-11-10 data snapshot.
How many intermediate certificates has TunTrust Root CA issued?
The CCADB lists 3: 2 valid, 0 expired and 1 revoked. The newest valid one is TunTrust Services CA, valid until 2039-04-26.
Is TunTrust Root CA cross-signed?
No. The CCADB has no certificate with the same subject and public key signed by another CA.
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