中文

Root certificate · GoDaddy

GoDaddy TLS Root CA - R1

GoDaddy TLS Root CA - R1 is a root CA certificate operated by GoDaddy (RSA 4096, valid until 2040-08-24, SHA-256 25CF3DA8). As of the latest CCADB data it is trusted for TLS server authentication by 1 of 4 major root stores: Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeNot included Not includedNo—No
MozillaNot included Not includedNo—No
AppleNot included Not includedNo—No
MicrosoftIncluded IncludedYes—No

The CCADB lists no EV policy OID for GoDaddy TLS Root CA - R1.

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
GoDaddy
Subject
CN=GoDaddy TLS Root CA - R1,O=GoDaddy.com,C=US
SHA-256
25CF3DA8E9B97ADDBF92543C2B82527C8A4E2CFF2062A6483040D4B64ACE719F
SHA-1 (Windows thumbprint)
C6FC6A49610C09CB640E250CCB05CDE834660517
SPKI SHA-256
80A8C921A7194AE63A6DB0E7BB5DD617FAEE7E9B3F14AC0621AAB145BE672990
Valid from
2025-08-28
Expires
2040-08-24
Key
RSA 4096
Signature algorithm
sha256WithRSAEncryption
Serial number
DA62FF9E2619B1257A4809368EE8E3F7
Country
US
Trust bits (CCADB)
Server Authentication
EV policy OIDs (CCADB)
not EV-enabled · TLS EV capable: No
Test websites
valid: https://valid.gd-tls-issuing-dv-r1v1.catest.godaddy.com · expired: https://expired.gd-tls-issuing-dv-r1v1.catest.godaddy.com · revoked: https://revoked.gd-tls-issuing-dv-r1v1.catest.godaddy.com
CCADB record
A012665
PEM
godaddy-tls-root-ca-r1.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 3 intermediate CA certificates signed directly by GoDaddy TLS Root CA - R1: 3 currently valid, 0 expired and 0 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.

IntermediateOperated byExpiresStatus
GoDaddy TLS Intermediate CA EV - R1v1 GoDaddy2040-08-24Valid
GoDaddy TLS Intermediate CA DV - R1v1 GoDaddy2040-08-24Valid
GoDaddy TLS Intermediate CA OV - R1v1 GoDaddy2040-08-24Valid

Cross-signed versions

1 certificate(s) in the CCADB have the same subject and public key as GoDaddy TLS Root CA - R1 but a different issuer. A server can send one of them so that clients which trust the issuing root, but not GoDaddy TLS Root CA - R1, can still build a chain.

Signed byCA ownerExpiresStatus
Go Daddy Root Certificate Authority - G2 crt.sh GoDaddy2037-12-31Valid

CRL and OCSP addresses

In the root certificate

GoDaddy TLS Root CA - R1 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.godaddy.com/gd_tls_root-r1.crl

Used by the intermediates it issued

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

  • CRL: http://crl.godaddy.com/gd_tls_root-r1.crl (3)

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

What happens when it expires

GoDaddy TLS Root CA - R1 is valid until 2040-08-24, about 13.8 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 GoDaddy TLS Root CA - R1 by common name (GoDaddy TLS Root CA - R1) 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 "GoDaddy TLS Root CA - R1" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 25CF3DA8E9B97ADDBF92543C2B82527C8A4E2CFF2062A6483040D4B64ACE719F

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 C6FC6A49610C09CB640E250CCB05CDE834660517

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 "GoDaddy TLS Root CA - R1"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "GoDaddy TLS Root CA - R1"

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 "25:CF:3D:A8:E9:B9:7A:DD:BF:92:54:3C:2B:82:52:7C:8A:4E:2C:FF:20:62:A6:48:30:40:D4:B6:4A:CE:71:9F"

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 GoDaddy.com → GoDaddy TLS Root CA - R1.

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 godaddy-tls-root-ca-r1.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=25:CF:3D:A8:E9:B9:7A:DD:BF:92:54:3C:2B:82:52:7C:8A:4E:2C:FF:20:62:A6:48:30:40:D4:B6:4A:CE:71:9F

FAQ

Is GoDaddy TLS Root CA - R1 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 GoDaddy TLS Root CA - R1 expire?

On 2040-08-24, about 13.8 years after the 2026-11-10 data snapshot.

How many intermediate certificates has GoDaddy TLS Root CA - R1 issued?

The CCADB lists 3: 3 valid, 0 expired and 0 revoked. The newest valid one is GoDaddy TLS Intermediate CA EV - R1v1, valid until 2040-08-24.

Is GoDaddy TLS Root CA - R1 cross-signed?

Yes. The CCADB has 1 cross-certificate(s) with its subject and key, signed by Go Daddy Root Certificate Authority - G2; 1 of them are still valid.

Other roots from GoDaddy

Sources

  1. CCADB — Resources (TLS Server Authentication report, All Included Root Certificate Trust Bit Settings)
  2. CCADB — All Certificate Information (root and intermediate), CSV V5
  3. CCADB — Mozilla Included CA Certificate Report
  4. CCADB — Chrome / Mozilla / Apple / Microsoft TLS Server Authentication CSV