SSL Report: mail.itbuildgroup.com (79.98.10.71)
Due to a recently discovered bug in Apple's code, your browser is exposed to MITM attacks. Click here for more information.

Please wait... 71% complete
Determining available cipher suites

Certificate #1: RSA 2048 bits (SHA256withRSA)
Server Key and Certificate #1
Subject e4-system.ru
Fingerprint SHA256: 1af2b45ad65c86836af037348c60c55b4df2ee0261637d48c7d6e0a884a7fac0
Pin SHA256: +Vt1dMUzLfvdcZDd7+edAXH675IoiAzJAwsanq3LBt8=
Common names e4-system.ru
Alternative names *.e4-system.ru e4-system.ru   MISMATCH
Serial Number 05fc28ea2ca4a933427a8149ba35046ca53b
Valid from Mon, 24 Nov 2025 05:31:01 UTC
Valid until Sun, 22 Feb 2026 05:31:00 UTC (expires in 2 months and 10 days)
Key RSA 2048 bits (e 65537)
Weak key (Debian) No
Issuer R13
AIA: http://r13.i.lencr.org/
Signature algorithm SHA256withRSA
Extended Validation No
Revocation information CRL
CRL: http://r13.c.lencr.org/60.crl
Revocation status Validation error
CRL ERROR: IOException occurred
DNS CAA No (more info)
Trusted No   NOT TRUSTED (Why?)
Mozilla  Apple  Android  Java  Windows 


Additional Certificates (if supplied)
Certificates provided 2 (2579 bytes)
Chain issues None
#2
Subject R13
Fingerprint SHA256: d3b128216a843f8ef1321501f5df52a5df52939ee2c19297712cd3de4d419354
Pin SHA256: AlSQhgtJirc8ahLyekmtX+Iw+v46yPYRLJt9Cq1GlB0=
Valid until Fri, 12 Mar 2027 23:59:59 UTC (expires in 1 year and 3 months)
Key RSA 2048 bits (e 65537)
Issuer ISRG Root X1
Signature algorithm SHA256withRSA


Certification Paths
Path #1: Not trusted (invalid certificate [Fingerprint SHA256: 1af2b45ad65c86836af037348c60c55b4df2ee0261637d48c7d6e0a884a7fac0])
1 Sent by server e4-system.ru
Fingerprint SHA256: 1af2b45ad65c86836af037348c60c55b4df2ee0261637d48c7d6e0a884a7fac0
Pin SHA256: +Vt1dMUzLfvdcZDd7+edAXH675IoiAzJAwsanq3LBt8=

RSA 2048 bits (e 65537) / SHA256withRSA
CRL ERROR: IOException occurred
2 Sent by server R13
Fingerprint SHA256: d3b128216a843f8ef1321501f5df52a5df52939ee2c19297712cd3de4d419354
Pin SHA256: AlSQhgtJirc8ahLyekmtX+Iw+v46yPYRLJt9Cq1GlB0=

RSA 2048 bits (e 65537) / SHA256withRSA
CRL ERROR: IOException occurred
3 In trust store ISRG Root X1   Self-signed
Fingerprint SHA256: 96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
Pin SHA256: C5+lpZ7tcVwmwQIMcRtPbsQtWLABXhQzejna0wHFr8M=

RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (invalid certificate [Fingerprint SHA256: 1af2b45ad65c86836af037348c60c55b4df2ee0261637d48c7d6e0a884a7fac0])
1 Sent by server e4-system.ru
Fingerprint SHA256: 1af2b45ad65c86836af037348c60c55b4df2ee0261637d48c7d6e0a884a7fac0
Pin SHA256: +Vt1dMUzLfvdcZDd7+edAXH675IoiAzJAwsanq3LBt8=

RSA 2048 bits (e 65537) / SHA256withRSA
CRL ERROR: IOException occurred
2 Sent by server R13
Fingerprint SHA256: d3b128216a843f8ef1321501f5df52a5df52939ee2c19297712cd3de4d419354
Pin SHA256: AlSQhgtJirc8ahLyekmtX+Iw+v46yPYRLJt9Cq1GlB0=

RSA 2048 bits (e 65537) / SHA256withRSA
CRL ERROR: IOException occurred
3 In trust store ISRG Root X1   Self-signed
Fingerprint SHA256: 96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
Pin SHA256: C5+lpZ7tcVwmwQIMcRtPbsQtWLABXhQzejna0wHFr8M=

RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (invalid certificate [Fingerprint SHA256: 1af2b45ad65c86836af037348c60c55b4df2ee0261637d48c7d6e0a884a7fac0])
1 Sent by server e4-system.ru
Fingerprint SHA256: 1af2b45ad65c86836af037348c60c55b4df2ee0261637d48c7d6e0a884a7fac0
Pin SHA256: +Vt1dMUzLfvdcZDd7+edAXH675IoiAzJAwsanq3LBt8=

RSA 2048 bits (e 65537) / SHA256withRSA
CRL ERROR: IOException occurred
2 Sent by server R13
Fingerprint SHA256: d3b128216a843f8ef1321501f5df52a5df52939ee2c19297712cd3de4d419354
Pin SHA256: AlSQhgtJirc8ahLyekmtX+Iw+v46yPYRLJt9Cq1GlB0=

RSA 2048 bits (e 65537) / SHA256withRSA
CRL ERROR: IOException occurred
3 In trust store ISRG Root X1   Self-signed
Fingerprint SHA256: 96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
Pin SHA256: C5+lpZ7tcVwmwQIMcRtPbsQtWLABXhQzejna0wHFr8M=

RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (invalid certificate [Fingerprint SHA256: 1af2b45ad65c86836af037348c60c55b4df2ee0261637d48c7d6e0a884a7fac0])
1 Sent by server e4-system.ru
Fingerprint SHA256: 1af2b45ad65c86836af037348c60c55b4df2ee0261637d48c7d6e0a884a7fac0
Pin SHA256: +Vt1dMUzLfvdcZDd7+edAXH675IoiAzJAwsanq3LBt8=

RSA 2048 bits (e 65537) / SHA256withRSA
CRL ERROR: IOException occurred
2 Sent by server R13
Fingerprint SHA256: d3b128216a843f8ef1321501f5df52a5df52939ee2c19297712cd3de4d419354
Pin SHA256: AlSQhgtJirc8ahLyekmtX+Iw+v46yPYRLJt9Cq1GlB0=

RSA 2048 bits (e 65537) / SHA256withRSA
CRL ERROR: IOException occurred
3 In trust store ISRG Root X1   Self-signed
Fingerprint SHA256: 96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
Pin SHA256: C5+lpZ7tcVwmwQIMcRtPbsQtWLABXhQzejna0wHFr8M=

RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (invalid certificate [Fingerprint SHA256: 1af2b45ad65c86836af037348c60c55b4df2ee0261637d48c7d6e0a884a7fac0])
1 Sent by server e4-system.ru
Fingerprint SHA256: 1af2b45ad65c86836af037348c60c55b4df2ee0261637d48c7d6e0a884a7fac0
Pin SHA256: +Vt1dMUzLfvdcZDd7+edAXH675IoiAzJAwsanq3LBt8=

RSA 2048 bits (e 65537) / SHA256withRSA
CRL ERROR: IOException occurred
2 Sent by server R13
Fingerprint SHA256: d3b128216a843f8ef1321501f5df52a5df52939ee2c19297712cd3de4d419354
Pin SHA256: AlSQhgtJirc8ahLyekmtX+Iw+v46yPYRLJt9Cq1GlB0=

RSA 2048 bits (e 65537) / SHA256withRSA
CRL ERROR: IOException occurred
3 In trust store ISRG Root X1   Self-signed
Fingerprint SHA256: 96bcec06264976f37460779acf28c5a7cfe8a3c0aae11a8ffcee05c0bddf08c6
Pin SHA256: C5+lpZ7tcVwmwQIMcRtPbsQtWLABXhQzejna0wHFr8M=

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:

  1. Invalid certificate
  2. Invalid configuration
  3. Unknown Certificate Authority

1. Invalid certificate

A certificate is invalid if:

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.

SSL Report v2.4.1