Sat, 09 Aug 2031 16:44:41 UTC (expires in 5 years and 9 months)
Key
RSA 2048 bits
(e 65537)
Issuer
Ferrari S.p.A. Certification Authority G3
Signature algorithm
SHA256withRSA
#3
Subject
Ferrari S.p.A. Certification Authority G3 Not in trust store
Fingerprint SHA256: a29c7084abac2a33512cd73ad2ed38003bc4762366951cbd21bb06131cd3e7ea
Pin SHA256: paxaka1jH1TPM8xSy5K0dpG38d/eYXpyl4EkyJuznB8=
Valid until
Fri, 09 Aug 2041 14:51:15 UTC (expires in 15 years and 9 months)
Key
RSA 4096 bits
(e 65537)
Issuer
Ferrari S.p.A. Certification Authority G3 Self-signed
Signature algorithm
SHA256withRSA
Certification Paths
Path #1: Not trusted (path does not chain to a trusted anchor)
Ferrari S.p.A. External Certification Authority G3
Fingerprint SHA256: 828c07764a81d000499b8c9cda62bbf9051004d0ac3230d237e0148a03c9f492
Pin SHA256: sUjL5hQH9QpIQ/cD5cUpk+/JR/imemxnW2OF40CqmU8=
RSA 2048 bits
(e 65537) /
SHA256withRSA
3
Sent by server
Not in trust store
Ferrari S.p.A. Certification Authority G3
Self-signed
Fingerprint SHA256: a29c7084abac2a33512cd73ad2ed38003bc4762366951cbd21bb06131cd3e7ea
Pin SHA256: paxaka1jH1TPM8xSy5K0dpG38d/eYXpyl4EkyJuznB8=
RSA 4096 bits
(e 65537) /
SHA256withRSA
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.
Please wait...
5% complete
Certification Paths