Go Daddy Secure Certificate Authority - G2
Fingerprint SHA256: 973a41276ffd01e027a2aad49e34c37846d3e976ff6a620b6712e33832041aa6
Pin SHA256: 8Rw90Ej3Ttt8RRkrg+WYDS9n7IS03bk5bjP/UXPtaY8=
RSA 2048 bits
(e 65537) /
SHA256withRSA
3
Sent by server
Go Daddy Root Certificate Authority - G2
Fingerprint SHA256: 3a2fbe92891e57fe05d57087f48e730f17e5a5f53ef403d618e5b74d7a7e6ecb
Pin SHA256: Ko8tivDrEjiY90yGasP6ZpBU4jwXvHqVvQI0GS3GNdA=
RSA 2048 bits
(e 65537) /
SHA256withRSA
4
In trust store
The Go Daddy Group, Inc. / Go Daddy Class 2 Certification Authority
Self-signed
Fingerprint SHA256: c3846bf24b9e93ca64274c0ec67c1ecc5e024ffcacd2d74019350e81fe546ae4
Pin SHA256: VjLZe/p3W/PJnd6lL8JVNBCGQBZynFLdZSTIqcO0SJ8=
RSA 2048 bits
(e 3) /
SHA1withRSA
Weak or insecure signature, but no impact on root certificate
Go Daddy Secure Certificate Authority - G2
Fingerprint SHA256: 973a41276ffd01e027a2aad49e34c37846d3e976ff6a620b6712e33832041aa6
Pin SHA256: 8Rw90Ej3Ttt8RRkrg+WYDS9n7IS03bk5bjP/UXPtaY8=
RSA 2048 bits
(e 65537) /
SHA256withRSA
3
Sent by server
Go Daddy Root Certificate Authority - G2
Fingerprint SHA256: 3a2fbe92891e57fe05d57087f48e730f17e5a5f53ef403d618e5b74d7a7e6ecb
Pin SHA256: Ko8tivDrEjiY90yGasP6ZpBU4jwXvHqVvQI0GS3GNdA=
RSA 2048 bits
(e 65537) /
SHA256withRSA
4
In trust store
The Go Daddy Group, Inc. / Go Daddy Class 2 Certification Authority
Self-signed
Fingerprint SHA256: c3846bf24b9e93ca64274c0ec67c1ecc5e024ffcacd2d74019350e81fe546ae4
Pin SHA256: VjLZe/p3W/PJnd6lL8JVNBCGQBZynFLdZSTIqcO0SJ8=
RSA 2048 bits
(e 3) /
SHA1withRSA
Weak or insecure signature, but no impact on root certificate
Go Daddy Secure Certificate Authority - G2
Fingerprint SHA256: 973a41276ffd01e027a2aad49e34c37846d3e976ff6a620b6712e33832041aa6
Pin SHA256: 8Rw90Ej3Ttt8RRkrg+WYDS9n7IS03bk5bjP/UXPtaY8=
RSA 2048 bits
(e 65537) /
SHA256withRSA
3
Sent by server
Go Daddy Root Certificate Authority - G2
Fingerprint SHA256: 3a2fbe92891e57fe05d57087f48e730f17e5a5f53ef403d618e5b74d7a7e6ecb
Pin SHA256: Ko8tivDrEjiY90yGasP6ZpBU4jwXvHqVvQI0GS3GNdA=
RSA 2048 bits
(e 65537) /
SHA256withRSA
4
In trust store
The Go Daddy Group, Inc. / Go Daddy Class 2 Certification Authority
Self-signed
Fingerprint SHA256: c3846bf24b9e93ca64274c0ec67c1ecc5e024ffcacd2d74019350e81fe546ae4
Pin SHA256: VjLZe/p3W/PJnd6lL8JVNBCGQBZynFLdZSTIqcO0SJ8=
RSA 2048 bits
(e 3) /
SHA1withRSA
Weak or insecure signature, but no impact on root certificate
Go Daddy Secure Certificate Authority - G2
Fingerprint SHA256: 973a41276ffd01e027a2aad49e34c37846d3e976ff6a620b6712e33832041aa6
Pin SHA256: 8Rw90Ej3Ttt8RRkrg+WYDS9n7IS03bk5bjP/UXPtaY8=
RSA 2048 bits
(e 65537) /
SHA256withRSA
3
Sent by server
Go Daddy Root Certificate Authority - G2
Fingerprint SHA256: 3a2fbe92891e57fe05d57087f48e730f17e5a5f53ef403d618e5b74d7a7e6ecb
Pin SHA256: Ko8tivDrEjiY90yGasP6ZpBU4jwXvHqVvQI0GS3GNdA=
RSA 2048 bits
(e 65537) /
SHA256withRSA
4
In trust store
The Go Daddy Group, Inc. / Go Daddy Class 2 Certification Authority
Self-signed
Fingerprint SHA256: c3846bf24b9e93ca64274c0ec67c1ecc5e024ffcacd2d74019350e81fe546ae4
Pin SHA256: VjLZe/p3W/PJnd6lL8JVNBCGQBZynFLdZSTIqcO0SJ8=
RSA 2048 bits
(e 3) /
SHA1withRSA
Weak or insecure signature, but no impact on root certificate
Go Daddy Secure Certificate Authority - G2
Fingerprint SHA256: 973a41276ffd01e027a2aad49e34c37846d3e976ff6a620b6712e33832041aa6
Pin SHA256: 8Rw90Ej3Ttt8RRkrg+WYDS9n7IS03bk5bjP/UXPtaY8=
RSA 2048 bits
(e 65537) /
SHA256withRSA
3
Sent by server
Go Daddy Root Certificate Authority - G2
Fingerprint SHA256: 3a2fbe92891e57fe05d57087f48e730f17e5a5f53ef403d618e5b74d7a7e6ecb
Pin SHA256: Ko8tivDrEjiY90yGasP6ZpBU4jwXvHqVvQI0GS3GNdA=
RSA 2048 bits
(e 65537) /
SHA256withRSA
4
In trust store
The Go Daddy Group, Inc. / Go Daddy Class 2 Certification Authority
Self-signed
Fingerprint SHA256: c3846bf24b9e93ca64274c0ec67c1ecc5e024ffcacd2d74019350e81fe546ae4
Pin SHA256: VjLZe/p3W/PJnd6lL8JVNBCGQBZynFLdZSTIqcO0SJ8=
RSA 2048 bits
(e 3) /
SHA1withRSA
Weak or insecure signature, but no impact on root certificate
Click here to expand
Certificate #2: RSA 2048 bits (SHA384withRSA)
No SNI
Microsoft Azure RSA TLS Issuing CA 07
Fingerprint SHA256: 724247794951c93f3e41711617e95ce143263e3196c345a1da78f6639749ec03
Pin SHA256: Mfmoi2wKbxJCpI54JB7B+PPNkO8dRO51Bpbp+Gu4aFg=
RSA 4096 bits
(e 65537) /
SHA384withRSA
3
In trust store
DigiCert Global Root G2
Self-signed
Fingerprint SHA256: cb3ccbb76031e5e0138f8dd39a23f9de47ffc35e43c1144cea27d46a5ab1cb5f
Pin SHA256: i7WTqTvh0OioIruIfFR4kMPnBqrS2rdiVPl/s2uC/CY=
RSA 2048 bits
(e 65537) /
SHA256withRSA
Click here to expand
Click here to expand
Why is my certificate not trusted?
There are many reasons why a certificate may not be trusted. The
exact problem is indicated on the report card in bright red.
The problems fall into three categories:
Invalid certificate
Invalid configuration
Unknown Certificate Authority
1. Invalid certificate
A certificate is invalid if:
It is used before its activation date
It is used after its expiry date
Certificate hostnames don't match the site hostname
It has been revoked
It has insecure signature
It has been blacklisted
2. Invalid configuration
In some cases, the certificate chain does not
contain all the necessary certificates to connect the web
server certificate to one of the root certificates in our trust store.
Less commonly, one of the certificates in the chain (other than the
web server certificate) will have expired, and that invalidates the
entire chain.
3. Unknown Certificate Authority
In order for trust to be established, we must have the root certificate
of the signing Certificate Authority in our trust store. SSL Labs does not
maintain its own trust store; instead we use the store maintained by Mozilla.
If we mark a web site as not trusted, that means that the average web user's
browser will not trust it either. For certain special groups of users, such
web sites can still be secure. For example, if you can securely verify that
a self-signed web site is operated by a person you trust, then you can trust
that self-signed web site too. Or, if you work for an organisation that manages
its own trust, and you have their own root certificate already embedded in
your browser. Such special cases do not work for the general public, however,
and this is what we indicate on our report card.
4. Interoperability issues
In some rare cases trust cannot be established because of interoperability
issues between our code and the code or configuration running on the server.
We manually review such cases, but if you encounter such an issue please feel
free to contact us. Such problems are very difficult to troubleshoot and you
may be able to provide us with information that might help us determine the
root cause.