Root certificate · Visa

Visa Public ECC Root CA

Visa Public ECC Root CA is a root CA certificate operated by Visa (ECDSA P-384, valid until 2041-03-15, SHA-256 E6BE68CE). 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 Public ECC 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, 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: Visa
Subject: CN=Visa Public ECC Root CA,OU=Visa International Service Association,O=VISA,C=US
SHA-256: E6BE68CE06FE0DA0C140F1AEB00B67B636C5EEA9422088929362375CE086DB39
SHA-1 (Windows thumbprint): 9CB1E6FBC21AAF3D68973CB516E932C44CB9D560
SPKI SHA-256: D6EC6348A7C4D42AC48D9C43145A8CD71971362363267C6673A77B8A8573A66B
Valid from: 2021-03-16
Expires: 2041-03-15
Key: ECDSA P-384
Signature algorithm: ecdsa-with-SHA384
Serial number: 513E96000000DCD306988C729CFA65
Country: US
Trust bits (CCADB): Server Authentication, Client 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: A007891
PEM: visa-public-ecc-root-ca.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

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

Showing 1 of 1: 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 ECC 3DS Issuing CA - G2	Visa	2041-03-11	Valid

Cross-signed versions

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

CRL and OCSP addresses

In the root certificate

Visa Public ECC 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/VisaPublicECCRoot.crl

Used by the intermediates it issued

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

CRL: http://enroll.visaca.com/VisaPublicECCRoot.crl (1)

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

What happens when it expires

Visa Public ECC Root CA is valid until 2041-03-15, about 14.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 Public ECC Root CA by common name (Visa Public ECC 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 Public ECC Root CA" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: E6BE68CE06FE0DA0C140F1AEB00B67B636C5EEA9422088929362375CE086DB39

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 9CB1E6FBC21AAF3D68973CB516E932C44CB9D560

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 Public ECC Root CA"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "Visa Public ECC 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:BE:68:CE:06:FE:0D:A0:C1:40:F1:AE:B0:0B:67:B6:36:C5:EE:A9:42:20:88:92:93:62:37:5C:E0:86:DB:39"

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 Public ECC 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-public-ecc-root-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=E6:BE:68:CE:06:FE:0D:A0:C1:40:F1:AE:B0:0B:67:B6:36:C5:EE:A9:42:20:88:92:93:62:37:5C:E0:86:DB:39

FAQ

Is Visa Public ECC 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 Public ECC Root CA expire?

On 2041-03-15, about 14.3 years after the 2026-11-10 data snapshot.

How many intermediate certificates has Visa Public ECC Root CA issued?

The CCADB lists 1: 1 valid, 0 expired and 0 revoked. The newest valid one is Visa ECC 3DS Issuing CA - G2, valid until 2041-03-11.

Is Visa Public ECC 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 TLS Root CA RSA 4096 · 2034-03-06

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