Mon, 23 Sep 2030 23:59:59 UTC (expires in 5 years and 3 months)
Key
RSA 2048 bits
(e 65537)
Issuer
DigiCert Global Root CA
Signature algorithm
SHA256withRSA
#3
Subject
DigiCert Global Root CA In trust store
Fingerprint SHA256: 4348a0e9444c78cb265e058d5e8944b4d84f9662bd26db257f8934a443c70161
Pin SHA256: r/mIkG3eEpVdm+u/ko/cwxzOMo1bk4TyHIlByibiA5E=
Valid until
Mon, 10 Nov 2031 00:00:00 UTC (expires in 6 years and 5 months)
Key
RSA 2048 bits
(e 65537)
Issuer
DigiCert Global Root CA Self-signed
Signature algorithm
SHA1withRSA
Weak, but no impact on root certificate
Certification Paths
Path #1: Not trusted (validity check failed)
1
Sent by server
cloud.crm.toyota.ru
Fingerprint SHA256: 46076e78c9fb6ab2b3264ca08e98bd6d0c67d8b55e7763a588c79bc8c7cf94a4
Pin SHA256: F/MLVD820b3Q4x4WU2Uv2iTB7VLVjMDIspSUuCclTMA=
RSA 2048 bits
(e 65537) /
SHA256withRSA
Valid until: Fri, 13 Jan 2023 23:59:59 UTC
EXPIRED
DigiCert Global Root CA
Self-signed
Fingerprint SHA256: 4348a0e9444c78cb265e058d5e8944b4d84f9662bd26db257f8934a443c70161
Pin SHA256: r/mIkG3eEpVdm+u/ko/cwxzOMo1bk4TyHIlByibiA5E=
RSA 2048 bits
(e 65537) /
SHA1withRSA
Weak or insecure signature, but no impact on root certificate
Path #1: Not trusted (validity check failed)
1
Sent by server
cloud.crm.toyota.ru
Fingerprint SHA256: 46076e78c9fb6ab2b3264ca08e98bd6d0c67d8b55e7763a588c79bc8c7cf94a4
Pin SHA256: F/MLVD820b3Q4x4WU2Uv2iTB7VLVjMDIspSUuCclTMA=
RSA 2048 bits
(e 65537) /
SHA256withRSA
Valid until: Fri, 13 Jan 2023 23:59:59 UTC
EXPIRED
DigiCert Global Root CA
Self-signed
Fingerprint SHA256: 4348a0e9444c78cb265e058d5e8944b4d84f9662bd26db257f8934a443c70161
Pin SHA256: r/mIkG3eEpVdm+u/ko/cwxzOMo1bk4TyHIlByibiA5E=
RSA 2048 bits
(e 65537) /
SHA1withRSA
Weak or insecure signature, but no impact on root certificate
Path #1: Not trusted (validity check failed)
1
Sent by server
cloud.crm.toyota.ru
Fingerprint SHA256: 46076e78c9fb6ab2b3264ca08e98bd6d0c67d8b55e7763a588c79bc8c7cf94a4
Pin SHA256: F/MLVD820b3Q4x4WU2Uv2iTB7VLVjMDIspSUuCclTMA=
RSA 2048 bits
(e 65537) /
SHA256withRSA
Valid until: Fri, 13 Jan 2023 23:59:59 UTC
EXPIRED
DigiCert Global Root CA
Self-signed
Fingerprint SHA256: 4348a0e9444c78cb265e058d5e8944b4d84f9662bd26db257f8934a443c70161
Pin SHA256: r/mIkG3eEpVdm+u/ko/cwxzOMo1bk4TyHIlByibiA5E=
RSA 2048 bits
(e 65537) /
SHA1withRSA
Weak or insecure signature, but no impact on root certificate
Path #1: Not trusted (validity check failed)
1
Sent by server
cloud.crm.toyota.ru
Fingerprint SHA256: 46076e78c9fb6ab2b3264ca08e98bd6d0c67d8b55e7763a588c79bc8c7cf94a4
Pin SHA256: F/MLVD820b3Q4x4WU2Uv2iTB7VLVjMDIspSUuCclTMA=
RSA 2048 bits
(e 65537) /
SHA256withRSA
Valid until: Fri, 13 Jan 2023 23:59:59 UTC
EXPIRED
DigiCert Global Root CA
Self-signed
Fingerprint SHA256: 4348a0e9444c78cb265e058d5e8944b4d84f9662bd26db257f8934a443c70161
Pin SHA256: r/mIkG3eEpVdm+u/ko/cwxzOMo1bk4TyHIlByibiA5E=
RSA 2048 bits
(e 65537) /
SHA1withRSA
Weak or insecure signature, but no impact on root certificate
Path #1: Not trusted (validity check failed)
1
Sent by server
cloud.crm.toyota.ru
Fingerprint SHA256: 46076e78c9fb6ab2b3264ca08e98bd6d0c67d8b55e7763a588c79bc8c7cf94a4
Pin SHA256: F/MLVD820b3Q4x4WU2Uv2iTB7VLVjMDIspSUuCclTMA=
RSA 2048 bits
(e 65537) /
SHA256withRSA
Valid until: Fri, 13 Jan 2023 23:59:59 UTC
EXPIRED
DigiCert Global Root CA
Self-signed
Fingerprint SHA256: 4348a0e9444c78cb265e058d5e8944b4d84f9662bd26db257f8934a443c70161
Pin SHA256: r/mIkG3eEpVdm+u/ko/cwxzOMo1bk4TyHIlByibiA5E=
RSA 2048 bits
(e 65537) /
SHA1withRSA
Weak or insecure signature, but no impact on root certificate
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...
77% complete
Certification Paths