Root certificate · Visa

Visa TLS Root CA

Visa TLS Root CA is a root CA certificate operated by Visa (RSA 4096, valid until 2034-03-06, SHA-256 E6432FCE). As of the latest CCADB data it is trusted for TLS server authentication by 1 of 4 major root stores: Microsoft.

Data updated Nov 10, 2026

Root store status

Root store	Status	Trusted for TLS	Distrust for TLS after	Constrained
Chrome	Not included Not included	No	—	No
Mozilla	Not included Not included	No	—	No
Apple	Not included Not included	No	—	No
Microsoft	Included Included	Yes	—	No

The CCADB lists no EV policy OID for Visa TLS Root CA.

Not included Chrome

Status: Not included

Not included Mozilla

Status: Not included

Not included Apple

Status: Not included

Included Microsoft

Status: Included
Trusted EKUs: Server 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: Visa
Subject: CN=Visa TLS Root CA,O=VISA,C=US
SHA-256: E6432FCE6B48F4E889B2FE183F8B480F72ECF80F57389B0E9C6E89CF04AD69D1
SHA-1 (Windows thumbprint): 49CC90C9986F1BD349692A759366B36DC5C2458D
SPKI SHA-256: C44B349E5BACC94A9AE8CAFA241CCA42B6A589EDAB8644142DB561BCB778E59C
Valid from: 2024-03-07
Expires: 2034-03-06
Key: RSA 4096
Signature algorithm: sha384WithRSAEncryption
Serial number: 65F10E000000C5D39E949C8AB8B726
Country: US
Trust bits (CCADB): Server Authentication
EV policy OIDs (CCADB): not EV-enabled · TLS EV capable: No
Test websites: valid: https://3dseccg2test.visaca.com:8447 · expired: https://3dseccg2test.visaca.com:8446 · revoked: https://3dseccg2test.visaca.com:9446
CCADB record: A011593
PEM: visa-tls-root-ca.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 2 intermediate CA certificates signed directly by Visa TLS Root CA: 2 currently valid, 0 expired and 0 revoked (revoked includes those whose parent was revoked).

Showing 2 of 2: 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
Visa TLS Issuing CA	Visa	2034-03-04	Valid
Visa TLS Issuing CA	Visa	2034-03-05	Valid

Cross-signed versions

No certificate in the CCADB has the same subject and public key as Visa TLS Root CA with a different issuer, so a client has to carry Visa TLS Root CA itself in its root store to trust it.

CRL and OCSP addresses

In the root certificate

Visa TLS 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)

https://enroll.visaca.com/VisaTLSRootCA.crl

Used by the intermediates it issued

Addresses found in the CRL Distribution Points and OCSP fields of the 2 valid intermediates signed by Visa TLS Root CA; the number in brackets is how many of them use each address.

CRL: http://enroll.visaca.com/VisaTLSRootCA.crl (2)

None of the valid intermediates under this root lists an OCSP responder.

What happens when it expires

Visa TLS Root CA is valid until 2034-03-06, about 7.3 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 Visa TLS Root CA by common name (Visa TLS 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 "Visa TLS Root CA" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: E6432FCE6B48F4E889B2FE183F8B480F72ECF80F57389B0E9C6E89CF04AD69D1

Windows (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 49CC90C9986F1BD349692A759366B36DC5C2458D

Linux (ca-certificates follows Mozilla: Not 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 "Visa TLS Root CA"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "Visa TLS 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 "E6:43:2F:CE:6B:48:F4:E8:89:B2:FE:18:3F:8B:48:0F:72:EC:F8:0F:57:38:9B:0E:9C:6E:89:CF:04:AD:69:D1"

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 VISA → Visa TLS 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.

Download PEM

# 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 visa-tls-root-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=E6:43:2F:CE:6B:48:F4:E8:89:B2:FE:18:3F:8B:48:0F:72:EC:F8:0F:57:38:9B:0E:9C:6E:89:CF:04:AD:69:D1

FAQ

Is Visa TLS Root CA trusted by Chrome, Firefox, Safari and Windows?

As of 2026-11-10, Microsoft trust it for TLS server authentication; Chrome, Mozilla, Apple do not.

When does Visa TLS Root CA expire?

On 2034-03-06, about 7.3 years after the 2026-11-10 data snapshot.

How many intermediate certificates has Visa TLS Root CA issued?

The CCADB lists 2: 2 valid, 0 expired and 0 revoked. The newest valid one is Visa TLS Issuing CA, valid until 2034-03-04.

Is Visa TLS Root CA cross-signed?

No. The CCADB has no certificate with the same subject and public key signed by another CA.

Other roots from Visa

Visa Public ECC Root CA ECDSA P-384 · 2041-03-15

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