Root certificate · GoDaddy

Starfield Root Certificate Authority - G2

Starfield Root Certificate Authority - G2 is a root CA certificate operated by GoDaddy (RSA 2048, valid until 2037-12-31, SHA-256 2CE1CB0B). As of the latest CCADB data it is trusted for TLS server authentication by 4 of 4 major root stores: Chrome, Mozilla, Apple, Microsoft.

Data updated

Root store status

Root storeStatusTrusted for TLSDistrust for TLS afterConstrained
ChromeIncluded IncludedYes—No
MozillaIncluded IncludedYes—No
AppleIncluded IncludedYes—Yes
MicrosoftIncluded IncludedYes—Yes

Mozilla treats it as an EV root for policy OID 2.16.840.1.114414.1.7.23.3.

Included Chrome

Status
Included

Included Mozilla

Status
Included
Trust bits
Websites
EV policy OIDs
2.16.840.1.114414.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
Allowed policies
Server Authentication, Client Authentication, Code Signing, Timestamp Signing

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=Starfield Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US
SHA-256
2CE1CB0BF9D2F9E102993FBE215152C3B2DD0CABDE1C68E5319B839154DBB7F5
SHA-1 (Windows thumbprint)
B51C067CEE2B0C3DF855AB2D92F4FE39D4E70F0E
SPKI SHA-256
808D68B3FAB4884A5F971ACE7D10550D7A95A163774F3EC36AFFFB213FBE4C74
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, Encrypting File System, Time Stamping, IP Security Tunnel Termination, IP Security User
EV policy OIDs (CCADB)
2.16.840.1.114414.1.7.23.3, 2.23.140.1.1 · TLS EV capable: Yes
Test websites
valid: https://valid.sfig2.catest.starfieldtech.com/ · expired: https://expired.sfig2.catest.starfieldtech.com/ · revoked: https://revoked.sfig2.catest.starfieldtech.com/
CCADB record
A000194
PEM
godaddy-starfield-root-ca-g2.pem

Look up this certificate on crt.sh

Intermediate CAs issued by this root

The CCADB lists 9 intermediate CA certificates signed directly by Starfield Root Certificate Authority - G2: 6 currently valid, 0 expired and 3 revoked (revoked includes those whose parent was revoked).

Showing 9 of 9: 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
Starfield TLS Root CA - R1 → Starfield TLS Root CA - R1 GoDaddy2037-12-31Valid
Certainly Intermediate R1 Certainly LLC2032-06-21Valid
Certainly Intermediate E1 Certainly LLC2032-06-21Valid
Starfield Secure Extended Validation Code Signing CA - G2 GoDaddy2035-05-01Valid
Starfield Secure Code Signing Certificate Authority - G2 GoDaddy2034-04-01Valid
Starfield Secure Certificate Authority - G2 GoDaddy2031-05-03Valid
Starfield Secure Certificate Authority - G5 GoDaddy2042-06-21Revoked
Certainly Intermediate R1 Certainly LLC2032-06-21Revoked
Certainly Intermediate E1 Certainly LLC2032-06-21Revoked

Cross-signed versions

1 certificate(s) in the CCADB have the same subject and public key as Starfield 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 Starfield Root Certificate Authority - G2, can still build a chain.

Signed byCA ownerExpiresStatus
Starfield Class 2 Certification Authority crt.sh GoDaddy2031-05-30Valid

CRL and OCSP addresses

In the root certificate

Starfield 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.starfieldtech.com/sfroot-g2.crl

Used by the intermediates it issued

Addresses found in the CRL Distribution Points and OCSP fields of the 6 valid intermediates signed by Starfield Root Certificate Authority - G2; the number in brackets is how many of them use each address.

  • CRL: http://crl.starfieldtech.com/sfroot-g2.crl (5)
  • CRL: http://crl.starfieldtech.com/repository/sfroot-g2.crl (1)
  • OCSP: http://ocsp.starfieldtech.com/ (3)

What happens when it expires

Starfield 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 Starfield Root Certificate Authority - G2 by common name (Starfield 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 "Starfield Root Certificate Authority - G2" -Z \
  /System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 2CE1CB0BF9D2F9E102993FBE215152C3B2DD0CABDE1C68E5319B839154DBB7F5

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 B51C067CEE2B0C3DF855AB2D92F4FE39D4E70F0E

Linux (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 "Starfield 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 "Starfield 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 "2C:E1:CB:0B:F9:D2:F9:E1:02:99:3F:BE:21:51:52:C3:B2:DD:0C:AB:DE:1C:68:E5:31:9B:83:91:54:DB:B7:F5"

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 Starfield Technologies, Inc. → Starfield 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.

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-starfield-root-ca-g2.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=2C:E1:CB:0B:F9:D2:F9:E1:02:99:3F:BE:21:51:52:C3:B2:DD:0C:AB:DE:1C:68:E5:31:9B:83:91:54:DB:B7:F5

FAQ

Is Starfield 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 Starfield 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 Starfield Root Certificate Authority - G2 issued?

The CCADB lists 9: 6 valid, 0 expired and 3 revoked. The newest valid one is Starfield TLS Root CA - R1, valid until 2037-12-31.

Is Starfield Root Certificate Authority - G2 cross-signed?

Yes. The CCADB has 1 cross-certificate(s) with its subject and key, signed by Starfield Class 2 Certification Authority; 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