Root certificate · GoDaddy

Go Daddy Class 2 Certification Authority

Go Daddy Class 2 Certification Authority is a root CA certificate operated by GoDaddy (RSA 2048, valid until 2034-06-29, SHA-256 C3846BF2). As of the latest CCADB data it is trusted for TLS server authentication by 2 of 4 major root stores: Apple, Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeRemoved RemovedNo—No
MozillaIncluded IncludedNo—No
AppleIncluded IncludedYes—No
MicrosoftIncluded IncludedYes—Yes

The CCADB lists EV policy OID 2.23.140.1.1, 2.16.840.1.114413.1.7.23.3, 2.16.840.1.114414.1.7.23.3 for this root, but Mozilla does not mark it as EV-enabled.

Removed Chrome

Status
Removed

Included Mozilla

Status
Included
Trust bits
All Trust Bits Turned Off
EV policy OIDs
not EV-enabled
First included in
NSS 3.10 / Firefox 1
Inclusion bug
#284677

Included Apple

Status
Included
Trust bits
serverAuth, clientAuth, emailProtection

Included Microsoft

Status
Included
Trusted EKUs
Server Authentication, Client Authentication, Code Signing, Secure Email
Not-before cutoff
2026-05-19 (Code Signing, Secure Email)

"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
OU=Go Daddy Class 2 Certification Authority,O=The Go Daddy Group\, Inc.,C=US
SHA-256
C3846BF24B9E93CA64274C0EC67C1ECC5E024FFCACD2D74019350E81FE546AE4
SHA-1 (Windows thumbprint)
2796BAE63F1801E277261BA0D77770028F20EEE4
SPKI SHA-256
5632D97BFA775BF3C99DDEA52FC2553410864016729C52DD6524C8A9C3B4489F
Valid from
2004-06-29
Expires
2034-06-29
Key
RSA 2048
Signature algorithm
sha1WithRSAEncryption
Serial number
0
Country
US
Trust bits (CCADB)
Server Authentication, Client Authentication, Secure Email
EV policy OIDs (CCADB)
2.23.140.1.1, 2.16.840.1.114413.1.7.23.3, 2.16.840.1.114414.1.7.23.3 · TLS EV capable: Yes
Test websites
valid: https://valid.gdi.catest.godaddy.com/ · expired: https://expired.gdi.catest.godaddy.com/ · revoked: https://revoked.gdi.catest.godaddy.com/
CCADB record
A000152
PEM
godaddy-go-daddy-class-2-ca.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 3 intermediate CA certificates signed directly by Go Daddy Class 2 Certification Authority: 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.

IntermediateOperated byExpiresStatus
Go Daddy Root Certificate Authority - G2 → Go Daddy Root Certificate Authority - G2 GoDaddy2031-05-30Valid
Go Daddy Root Certificate Authority - G2 GoDaddy2031-05-03Valid
Go Daddy Secure Certification Authority GoDaddy2026-11-16Revoked

Cross-signed versions

No certificate in the CCADB has the same subject and public key as Go Daddy Class 2 Certification Authority with a different issuer, so a client has to carry Go Daddy Class 2 Certification Authority itself in its root store to trust it.

CRL and OCSP addresses

In the root certificate

Go Daddy Class 2 Certification Authority 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/gdroot.crl

Used by the intermediates it issued

Addresses found in the CRL Distribution Points and OCSP fields of the 2 valid intermediates signed by Go Daddy Class 2 Certification Authority; the number in brackets is how many of them use each address.

  • CRL: http://crl.godaddy.com/gdroot.crl (2)
  • OCSP: http://ocsp.godaddy.com/ (2)

What happens when it expires

Go Daddy Class 2 Certification Authority is valid until 2034-06-29, about 7.6 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 Go Daddy Class 2 Certification Authority by common name (Go Daddy Class 2 Certification Authority) 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 "Go Daddy Class 2 Certification Authority" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: C3846BF24B9E93CA64274C0EC67C1ECC5E024FFCACD2D74019350E81FE546AE4

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 2796BAE63F1801E277261BA0D77770028F20EEE4

Linux (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 "Go Daddy Class 2 Certification Authority"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
  | openssl pkcs7 -print_certs -noout | grep -iF "Go Daddy Class 2 Certification Authority"

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 "C3:84:6B:F2:4B:9E:93:CA:64:27:4C:0E:C6:7C:1E:CC:5E:02:4F:FC:AC:D2:D7:40:19:35:0E:81:FE:54:6A:E4"

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 The Go Daddy Group, Inc. → Go Daddy Class 2 Certification Authority.

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-go-daddy-class-2-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=C3:84:6B:F2:4B:9E:93:CA:64:27:4C:0E:C6:7C:1E:CC:5E:02:4F:FC:AC:D2:D7:40:19:35:0E:81:FE:54:6A:E4

FAQ

Is Go Daddy Class 2 Certification Authority 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 Go Daddy Class 2 Certification Authority expire?

On 2034-06-29, about 7.6 years after the 2026-11-10 data snapshot.

How many intermediate certificates has Go Daddy Class 2 Certification Authority issued?

The CCADB lists 3: 2 valid, 0 expired and 1 revoked. The newest valid one is Go Daddy Root Certificate Authority - G2, valid until 2031-05-30.

Is Go Daddy Class 2 Certification Authority cross-signed?

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

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