Root certificate · GoDaddy
Go Daddy Root Certificate Authority - G2
Go Daddy Root Certificate Authority - G2 is a root CA certificate operated by GoDaddy (RSA 2048, valid until 2037-12-31, SHA-256 45140B32). As of the latest CCADB data it is trusted for TLS server authentication by 4 of 4 major root stores: Chrome, Mozilla, Apple, 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 | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | Yes |
Mozilla treats it as an EV root for policy OID 2.16.840.1.114413.1.7.23.3.
Included Chrome
- Status
- Included
Included Mozilla
- Status
- Included
- Trust bits
- Websites
- EV policy OIDs
- 2.16.840.1.114413.1.7.23.3
- First included in
- NSS 3.12.10 / Firefox 6.0
- Inclusion bug
- #527056
Included Apple
- Status
- Included
- Trust bits
- serverAuth, clientAuth, emailProtection
Included Microsoft
- Status
- Included
- Trusted EKUs
- Server Authentication, Client Authentication, Code Signing, Encrypting File System, IP Security Tunnel Termination, IP Security User, Secure Email, Time Stamping
- 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
- CN=Go Daddy Root Certificate Authority - G2,O=GoDaddy.com\, Inc.,L=Scottsdale,ST=Arizona,C=US
- SHA-256
45140B3247EB9CC8C5B4F0D7B53091F73292089E6E5A63E2749DD3ACA9198EDA- SHA-1 (Windows thumbprint)
47BEABC922EAE80E78783462A79F45C254FDE68B- SPKI SHA-256
2A8F2D8AF0EB123898F74C866AC3FA669054E23C17BC7A95BD0234192DC635D0- Valid from
- 2009-09-01
- Expires
- 2037-12-31
- Key
- RSA 2048
- Signature algorithm
- sha256WithRSAEncryption
- Serial number
0- Country
- US
- Trust bits (CCADB)
- Server Authentication, Client Authentication, Secure Email, Encrypting File System, Time Stamping, IP Security Tunnel Termination, IP Security User
- EV policy OIDs (CCADB)
- 2.16.840.1.114413.1.7.23.3, 2.23.140.1.1 · TLS EV capable: Yes
- Test websites
- valid:
https://valid.gdig2.catest.godaddy.com/· expired:https://expired.gdig2.catest.godaddy.com/· revoked:https://revoked.gdig2.catest.godaddy.com/ - CCADB record
- A000153
- PEM
- godaddy-go-daddy-root-ca-g2.pem
Intermediate CAs issued by this root
The CCADB lists 5 intermediate CA certificates signed directly by Go Daddy Root Certificate Authority - G2: 4 currently valid, 0 expired and 1 revoked (revoked includes those whose parent was revoked).
Showing 5 of 5: 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 |
|---|---|---|---|
| GoDaddy TLS Root CA - R1 → GoDaddy TLS Root CA - R1 | GoDaddy | 2037-12-31 | Valid |
| Go Daddy Secure Extended Validation Code Signing CA - G2 | GoDaddy | 2035-05-01 | Valid |
| Go Daddy Secure Code Signing Certificate Authority - G2 | GoDaddy | 2034-04-01 | Valid |
| Go Daddy Secure Certificate Authority - G2 | GoDaddy | 2031-05-03 | Valid |
| GoDaddy Secure Certificate Authority - G5 | GoDaddy | 2042-06-21 | Revoked |
Cross-signed versions
1 certificate(s) in the CCADB have the same subject and public key as Go Daddy Root Certificate Authority - G2 but a different issuer. A server can send one of them so that clients which trust the issuing root, but not Go Daddy Root Certificate Authority - G2, can still build a chain.
| Signed by | CA owner | Expires | Status |
|---|---|---|---|
| Go Daddy Class 2 Certification Authority crt.sh | GoDaddy | 2031-05-30 | Valid |
CRL and OCSP addresses
In the root certificate
Go Daddy Root Certificate Authority - G2 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-g2.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 4 valid intermediates signed by Go Daddy Root Certificate Authority - G2; the number in brackets is how many of them use each address.
- CRL:
http://crl.godaddy.com/gdroot-g2.crl(3) - CRL:
http://crl.godaddy.com/repository/gdroot-g2.crl(1) - OCSP:
http://ocsp.godaddy.com/(3)
What happens when it expires
Go Daddy Root Certificate Authority - G2 is valid until 2037-12-31, about 11.1 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 Root Certificate Authority - G2 by common name (Go Daddy Root Certificate Authority - G2) 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 Root Certificate Authority - G2" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 45140B3247EB9CC8C5B4F0D7B53091F73292089E6E5A63E2749DD3ACA9198EDAWindows (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 47BEABC922EAE80E78783462A79F45C254FDE68BLinux (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 "Go Daddy Root Certificate Authority - G2"
# Debian / Ubuntu (ca-certificates)
openssl crl2pkcs7 -nocrl -certfile /etc/ssl/certs/ca-certificates.crt \
| openssl pkcs7 -print_certs -noout | grep -iF "Go Daddy Root Certificate Authority - G2"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 "45:14:0B:32:47:EB:9C:C8:C5:B4:F0:D7:B5:30:91:F7:32:92:08:9E:6E:5A:63:E2:74:9D:D3:AC:A9:19:8E:DA"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, Inc. → Go Daddy Root Certificate Authority - G2.
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 godaddy-go-daddy-root-ca-g2.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=45:14:0B:32:47:EB:9C:C8:C5:B4:F0:D7:B5:30:91:F7:32:92:08:9E:6E:5A:63:E2:74:9D:D3:AC:A9:19:8E:DAFAQ
Is Go Daddy Root Certificate Authority - G2 trusted by Chrome, Firefox, Safari and Windows?
Yes. As of 2026-11-10, Chrome, Mozilla (Firefox), Apple (Safari) and Microsoft (Windows) all trust it for TLS server authentication.
When does Go Daddy Root Certificate Authority - G2 expire?
On 2037-12-31, about 11.1 years after the 2026-11-10 data snapshot.
How many intermediate certificates has Go Daddy Root Certificate Authority - G2 issued?
The CCADB lists 5: 4 valid, 0 expired and 1 revoked. The newest valid one is GoDaddy TLS Root CA - R1, valid until 2037-12-31.
Is Go Daddy Root Certificate Authority - G2 cross-signed?
Yes. The CCADB has 1 cross-certificate(s) with its subject and key, signed by Go Daddy Class 2 Certification Authority; 1 of them are still valid.
Other roots from GoDaddy
- Go Daddy Class 2 Certification Authority RSA 2048 · 2034-06-29
- GoDaddy TLS Root CA - R1 RSA 4096 · 2040-08-24
- Starfield Class 2 Certification Authority RSA 2048 · 2034-06-29
- Starfield Root Certificate Authority - G2 RSA 2048 · 2037-12-31
- Starfield TLS Root CA - R1 RSA 4096 · 2040-08-23
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