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

Please wait... 90% complete
Testing Heartbleed

Certificate #1: RSA 1024 bits (SHA1withRSA)
Server Key and Certificate #1
Subject web.softeca.es
Fingerprint SHA256: f3718691e81f12cd682856a3ce9063abd3874f09456432937a210b8103548617
Pin SHA256: OF05RhNvEYHA12eA5E8bXgw+5Tqq1pe8dtf+v7Hm28I=
Common names web.softeca.es
Alternative names -   INVALID
Serial Number 2a1a
Valid from Sat, 08 Sep 2012 18:38:53 UTC
Valid until Sun, 08 Sep 2013 18:38:53 UTC (expired 12 years and 1 month ago)   EXPIRED
Key RSA 1024 bits (e 65537)   WEAK
Weak key (Debian) No
Issuer web.softeca.es   Self-signed
Signature algorithm SHA1withRSA   INSECURE
Extended Validation No
Revocation information None
DNS CAA No (more info)
Trusted No   NOT TRUSTED (Why?)
Mozilla  Apple  Android  Java  Windows 


Additional Certificates (if supplied)
Certificates provided 1 (807 bytes)
Chain issues None


Certification Paths
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server
  Not in trust store 		web.softeca.es   Self-signed
Fingerprint SHA256: f3718691e81f12cd682856a3ce9063abd3874f09456432937a210b8103548617
Pin SHA256: OF05RhNvEYHA12eA5E8bXgw+5Tqq1pe8dtf+v7Hm28I=
RSA 1024 bits (e 65537) / SHA1withRSA
Valid until: Sun, 08 Sep 2013 18:38:53 UTC
EXPIRED   WEAK KEY
Weak or insecure signature, but no impact on root certificate
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server
  Not in trust store 		web.softeca.es   Self-signed
Fingerprint SHA256: f3718691e81f12cd682856a3ce9063abd3874f09456432937a210b8103548617
Pin SHA256: OF05RhNvEYHA12eA5E8bXgw+5Tqq1pe8dtf+v7Hm28I=
RSA 1024 bits (e 65537) / SHA1withRSA
Valid until: Sun, 08 Sep 2013 18:38:53 UTC
EXPIRED   WEAK KEY
Weak or insecure signature, but no impact on root certificate
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server
  Not in trust store 		web.softeca.es   Self-signed
Fingerprint SHA256: f3718691e81f12cd682856a3ce9063abd3874f09456432937a210b8103548617
Pin SHA256: OF05RhNvEYHA12eA5E8bXgw+5Tqq1pe8dtf+v7Hm28I=
RSA 1024 bits (e 65537) / SHA1withRSA
Valid until: Sun, 08 Sep 2013 18:38:53 UTC
EXPIRED   WEAK KEY
Weak or insecure signature, but no impact on root certificate
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server
  Not in trust store 		web.softeca.es   Self-signed
Fingerprint SHA256: f3718691e81f12cd682856a3ce9063abd3874f09456432937a210b8103548617
Pin SHA256: OF05RhNvEYHA12eA5E8bXgw+5Tqq1pe8dtf+v7Hm28I=
RSA 1024 bits (e 65537) / SHA1withRSA
Valid until: Sun, 08 Sep 2013 18:38:53 UTC
EXPIRED   WEAK KEY
Weak or insecure signature, but no impact on root certificate
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server
  Not in trust store 		web.softeca.es   Self-signed
Fingerprint SHA256: f3718691e81f12cd682856a3ce9063abd3874f09456432937a210b8103548617
Pin SHA256: OF05RhNvEYHA12eA5E8bXgw+5Tqq1pe8dtf+v7Hm28I=
RSA 1024 bits (e 65537) / SHA1withRSA
Valid until: Sun, 08 Sep 2013 18:38:53 UTC
EXPIRED   WEAK KEY
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:

  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