Root certificate · GoDaddy
Starfield Class 2 Certification Authority
Starfield Class 2 Certification Authority is a root CA certificate operated by GoDaddy (RSA 2048, valid until 2034-06-29, SHA-256 1465FA20). As of the latest CCADB data it is trusted for TLS server authentication by 2 of 4 major root stores: Apple, Microsoft.
Root store status
| Root store | Status | Trusted for TLS | Distrust for TLS after | Constrained |
|---|---|---|---|---|
| Chrome | Removed Removed | No | — | No |
| Mozilla | Included Included | No | — | No |
| Apple | Included Included | Yes | — | No |
| Microsoft | Included Included | Yes | — | Yes |
The CCADB lists EV policy OID 2.23.140.1.1, 2.16.840.1.114414.1.7.23.3, 2.16.840.1.114413.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=Starfield Class 2 Certification Authority,O=Starfield Technologies\, Inc.,C=US
- SHA-256
1465FA205397B876FAA6F0A9958E5590E40FCC7FAA4FB7C2C8677521FB5FB658- SHA-1 (Windows thumbprint)
AD7E1C28B064EF8F6003402014C3D0E3370EB58A- SPKI SHA-256
15F14AC45C9C7DA233D3479164E8137FE35EE0F38AE858183F08410EA82AC4B4- 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.114414.1.7.23.3, 2.16.840.1.114413.1.7.23.3 · TLS EV capable: Yes
- Test websites
- valid:
https://valid.sfi.catest.starfieldtech.com/· expired:https://expired.sfi.catest.starfieldtech.com/· revoked:https://revoked.sfi.catest.starfieldtech.com/ - CCADB record
- A000193
- PEM
- godaddy-starfield-class-2-ca.pem
Intermediate CAs issued by this root
The CCADB lists 5 intermediate CA certificates signed directly by Starfield Class 2 Certification Authority: 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 |
|---|---|---|---|
| Starfield Root Certificate Authority - G2 → Starfield Root Certificate Authority - G2 | GoDaddy | 2031-05-30 | Valid |
| Starfield Root Certificate Authority - G2 | GoDaddy | 2031-05-03 | Valid |
| Starfield Services Root Certificate Authority - G2 → Starfield Services Root Certificate Authority - G2 | Amazon Trust Services | 2034-06-28 | Valid |
| Starfield Services Root Certificate Authority - G2 → Starfield Services Root Certificate Authority - G2 | Amazon Trust Services | 2034-06-28 | Valid |
| Starfield Secure Certification Authority | GoDaddy | 2026-11-16 | Revoked |
Cross-signed versions
No certificate in the CCADB has the same subject and public key as Starfield Class 2 Certification Authority with a different issuer, so a client has to carry Starfield Class 2 Certification Authority itself in its root store to trust it.
CRL and OCSP addresses
In the root certificate
Starfield 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://certificates.godaddy.com/sfroot.crl
Used by the intermediates it issued
Addresses found in the CRL Distribution Points and OCSP fields of the 4 valid intermediates signed by Starfield Class 2 Certification Authority; the number in brackets is how many of them use each address.
- CRL:
http://crl.starfieldtech.com/sfroot.crl(2) - CRL:
http://s.ss2.us/r.crl(2) - OCSP:
http://o.ss2.us/(2) - OCSP:
http://ocsp.starfieldtech.com/(2)
What happens when it expires
Starfield 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 Starfield Class 2 Certification Authority by common name (Starfield 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 "Starfield Class 2 Certification Authority" -Z \
/System/Library/Keychains/SystemRootCertificates.keychain | grep "SHA-256"
# SHA-256 hash: 1465FA205397B876FAA6F0A9958E5590E40FCC7FAA4FB7C2C8677521FB5FB658Windows (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 AD7E1C28B064EF8F6003402014C3D0E3370EB58ALinux (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 "Starfield 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 "Starfield 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 "14:65:FA:20:53:97:B8:76:FA:A6:F0:A9:95:8E:55:90:E4:0F:CC:7F:AA:4F:B7:C2:C8:67:75:21:FB:5F:B6:58"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 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.
# 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-class-2-ca.pem -noout -subject -fingerprint -sha256
# sha256 Fingerprint=14:65:FA:20:53:97:B8:76:FA:A6:F0:A9:95:8E:55:90:E4:0F:CC:7F:AA:4F:B7:C2:C8:67:75:21:FB:5F:B6:58FAQ
Is Starfield 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 Starfield 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 Starfield Class 2 Certification Authority issued?
The CCADB lists 5: 4 valid, 0 expired and 1 revoked. The newest valid one is Starfield Root Certificate Authority - G2, valid until 2031-05-30.
Is Starfield 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
- Go Daddy Class 2 Certification Authority RSA 2048 · 2034-06-29
- Go Daddy Root Certificate Authority - G2 RSA 2048 · 2037-12-31
- GoDaddy TLS Root CA - R1 RSA 4096 · 2040-08-24
- 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