SSL Report: utomlansfakturering.ltblekinge.se (79.171.249.29)
Assessed on:  Tue, 09 Sep 2025 10:59:55 UTC | Clear cache
Scan Another »

Due to a recently discovered bug in Apple's code, your browser is exposed to MITM attacks. Click here for more information.

Summary
Overall Rating
T
If trust issues are ignored: B
0
20
40
60
80
100
Certificate
 
Protocol Support
 
Key Exchange
 
Cipher Strength
 

Visit our documentation page for more information, configuration guides, and books. Known issues are documented here.
This server's certificate is not trusted, see below for details.
This server's certificate is not trusted by major browsers. MORE INFO »
This server supports weak Diffie-Hellman (DH) key exchange parameters. Grade capped to B.   MORE INFO »
This server does not support Forward Secrecy with the reference browsers. Grade capped to B.  MORE INFO »
This server supports TLS 1.0 and TLS 1.1. Grade capped to B. MORE INFO »
This server does not support TLS 1.3.  MORE INFO »
This site works only in browsers with SNI support.
Certificate #1: RSA 2048 bits (SHA512withRSA)
Server Key and Certificate #1
Subject utomlansfakturering.ltblekinge.se
Fingerprint SHA256: 93bb7d0c6e081214df1ae9b876a17f799021823256b0f85a205cf699fe80137a
Pin SHA256: Lvy+ZIPqHwvJnWKA0s/cC+XSFM9YjT0yA1u+yFe6DVY=
Common names utomlansfakturering.ltblekinge.se
Alternative names utomlansfakturering.ltblekinge.se
Serial Number 479ef1d58e4be8d68dbc48ecedc3f736
Valid from Mon, 08 Sep 2025 06:12:18 UTC
Valid until Wed, 08 Sep 2027 21:50:00 UTC (expires in 1 year and 11 months)
Key RSA 2048 bits (e 65537)
Weak key (Debian) No
Issuer SITHS e-id Function CA v1
AIA: http://aia.siths.se/sithseidfunctioncav1.cer
Signature algorithm SHA512withRSA
Extended Validation No
Certificate Transparency No
OCSP Must Staple No
Revocation information CRL, OCSP
CRL: http://crl1.siths.se/sithseidfunctioncav1.crl
OCSP: http://ocsp1.siths.se
Revocation status Unchecked (only trusted certificates can be checked)
DNS CAA No (more info)
Trusted No   NOT TRUSTED (Why?)
Mozilla  Apple  Android  Java  Windows 


Additional Certificates (if supplied)
Certificates provided 2 (3228 bytes)
Chain issues None
#2
Subject SITHS e-id Function CA v1
Fingerprint SHA256: e388fc9ca3b63ea6c06f82856676f698eeaa25b7dbfc9670f2f7bb7ff100b8e4
Pin SHA256: YfKAQ76qBOr5ZR6eSU4C8IQINmqybtLBOt7r/+SRhvI=
Valid until Wed, 15 Sep 2049 20:00:00 UTC (expires in 24 years)
Key RSA 4096 bits (e 65537)
Issuer SITHS e-id Root CA v2
Signature algorithm SHA512withRSA


Certification Paths
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server utomlansfakturering.ltblekinge.se
Fingerprint SHA256: 93bb7d0c6e081214df1ae9b876a17f799021823256b0f85a205cf699fe80137a
Pin SHA256: Lvy+ZIPqHwvJnWKA0s/cC+XSFM9YjT0yA1u+yFe6DVY=
RSA 2048 bits (e 65537) / SHA512withRSA
2 Sent by server SITHS e-id Function CA v1
Fingerprint SHA256: e388fc9ca3b63ea6c06f82856676f698eeaa25b7dbfc9670f2f7bb7ff100b8e4
Pin SHA256: YfKAQ76qBOr5ZR6eSU4C8IQINmqybtLBOt7r/+SRhvI=
RSA 4096 bits (e 65537) / SHA512withRSA
3 Extra download
  Not in trust store 		SITHS e-id Root CA v2   Self-signed
Fingerprint SHA256: 8767260ac829d833c30af23857cbf8a2304bfda445303dfce5043afa73e584c1
Pin SHA256: F7dShJ6lVFM2WxBzsaooZXeHyysrTKOfH2xbGCDqk7Y=
RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server utomlansfakturering.ltblekinge.se
Fingerprint SHA256: 93bb7d0c6e081214df1ae9b876a17f799021823256b0f85a205cf699fe80137a
Pin SHA256: Lvy+ZIPqHwvJnWKA0s/cC+XSFM9YjT0yA1u+yFe6DVY=
RSA 2048 bits (e 65537) / SHA512withRSA
2 Sent by server SITHS e-id Function CA v1
Fingerprint SHA256: e388fc9ca3b63ea6c06f82856676f698eeaa25b7dbfc9670f2f7bb7ff100b8e4
Pin SHA256: YfKAQ76qBOr5ZR6eSU4C8IQINmqybtLBOt7r/+SRhvI=
RSA 4096 bits (e 65537) / SHA512withRSA
3 Extra download
  Not in trust store 		SITHS e-id Root CA v2   Self-signed
Fingerprint SHA256: 8767260ac829d833c30af23857cbf8a2304bfda445303dfce5043afa73e584c1
Pin SHA256: F7dShJ6lVFM2WxBzsaooZXeHyysrTKOfH2xbGCDqk7Y=
RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server utomlansfakturering.ltblekinge.se
Fingerprint SHA256: 93bb7d0c6e081214df1ae9b876a17f799021823256b0f85a205cf699fe80137a
Pin SHA256: Lvy+ZIPqHwvJnWKA0s/cC+XSFM9YjT0yA1u+yFe6DVY=
RSA 2048 bits (e 65537) / SHA512withRSA
2 Sent by server SITHS e-id Function CA v1
Fingerprint SHA256: e388fc9ca3b63ea6c06f82856676f698eeaa25b7dbfc9670f2f7bb7ff100b8e4
Pin SHA256: YfKAQ76qBOr5ZR6eSU4C8IQINmqybtLBOt7r/+SRhvI=
RSA 4096 bits (e 65537) / SHA512withRSA
3 Extra download
  Not in trust store 		SITHS e-id Root CA v2   Self-signed
Fingerprint SHA256: 8767260ac829d833c30af23857cbf8a2304bfda445303dfce5043afa73e584c1
Pin SHA256: F7dShJ6lVFM2WxBzsaooZXeHyysrTKOfH2xbGCDqk7Y=
RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server utomlansfakturering.ltblekinge.se
Fingerprint SHA256: 93bb7d0c6e081214df1ae9b876a17f799021823256b0f85a205cf699fe80137a
Pin SHA256: Lvy+ZIPqHwvJnWKA0s/cC+XSFM9YjT0yA1u+yFe6DVY=
RSA 2048 bits (e 65537) / SHA512withRSA
2 Sent by server SITHS e-id Function CA v1
Fingerprint SHA256: e388fc9ca3b63ea6c06f82856676f698eeaa25b7dbfc9670f2f7bb7ff100b8e4
Pin SHA256: YfKAQ76qBOr5ZR6eSU4C8IQINmqybtLBOt7r/+SRhvI=
RSA 4096 bits (e 65537) / SHA512withRSA
3 Extra download
  Not in trust store 		SITHS e-id Root CA v2   Self-signed
Fingerprint SHA256: 8767260ac829d833c30af23857cbf8a2304bfda445303dfce5043afa73e584c1
Pin SHA256: F7dShJ6lVFM2WxBzsaooZXeHyysrTKOfH2xbGCDqk7Y=
RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server utomlansfakturering.ltblekinge.se
Fingerprint SHA256: 93bb7d0c6e081214df1ae9b876a17f799021823256b0f85a205cf699fe80137a
Pin SHA256: Lvy+ZIPqHwvJnWKA0s/cC+XSFM9YjT0yA1u+yFe6DVY=
RSA 2048 bits (e 65537) / SHA512withRSA
2 Sent by server SITHS e-id Function CA v1
Fingerprint SHA256: e388fc9ca3b63ea6c06f82856676f698eeaa25b7dbfc9670f2f7bb7ff100b8e4
Pin SHA256: YfKAQ76qBOr5ZR6eSU4C8IQINmqybtLBOt7r/+SRhvI=
RSA 4096 bits (e 65537) / SHA512withRSA
3 Extra download
  Not in trust store 		SITHS e-id Root CA v2   Self-signed
Fingerprint SHA256: 8767260ac829d833c30af23857cbf8a2304bfda445303dfce5043afa73e584c1
Pin SHA256: F7dShJ6lVFM2WxBzsaooZXeHyysrTKOfH2xbGCDqk7Y=
RSA 4096 bits (e 65537) / SHA256withRSA

Click here to expand

Configuration
Protocols
TLS 1.3 No
TLS 1.2 Yes
TLS 1.1 Yes
TLS 1.0 Yes
SSL 3 No
SSL 2 No


Cipher Suites
# TLS 1.2 (suites in server-preferred order)
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x9f)   DH 1024 bits   FS   WEAK 256
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x9e)   DH 1024 bits   FS   WEAK 128
TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x39)   DH 1024 bits   FS   WEAK 256
TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x33)   DH 1024 bits   FS   WEAK 128
TLS_RSA_WITH_AES_256_GCM_SHA384 (0x9d)   WEAK 256
TLS_RSA_WITH_AES_128_GCM_SHA256 (0x9c)   WEAK 128
TLS_RSA_WITH_AES_256_CBC_SHA256 (0x3d)   WEAK 256
TLS_RSA_WITH_AES_128_CBC_SHA256 (0x3c)   WEAK 128
TLS_RSA_WITH_AES_256_CBC_SHA (0x35)   WEAK 256
TLS_RSA_WITH_AES_128_CBC_SHA (0x2f)   WEAK 128
TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa)   WEAK 112
# TLS 1.1 (suites in server-preferred order)
TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x39)   DH 1024 bits   FS   WEAK 256
TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x33)   DH 1024 bits   FS   WEAK 128
TLS_RSA_WITH_AES_256_CBC_SHA (0x35)   WEAK 256
TLS_RSA_WITH_AES_128_CBC_SHA (0x2f)   WEAK 128
TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa)   WEAK 112
# TLS 1.0 (suites in server-preferred order)
TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x39)   DH 1024 bits   FS   WEAK 256
TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x33)   DH 1024 bits   FS   WEAK 128
TLS_RSA_WITH_AES_256_CBC_SHA (0x35)   WEAK 256
TLS_RSA_WITH_AES_128_CBC_SHA (0x2f)   WEAK 128
TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa)   WEAK 112


Handshake Simulation
Android 2.3.7   No SNI 2 Server closed connection
Android 4.0.4 RSA 2048 (SHA512)   TLS 1.0 TLS_DHE_RSA_WITH_AES_256_CBC_SHA   DH 1024  FS
Android 4.1.1 RSA 2048 (SHA512)   TLS 1.0 TLS_DHE_RSA_WITH_AES_256_CBC_SHA   DH 1024  FS
Android 4.2.2 RSA 2048 (SHA512)   TLS 1.0 TLS_DHE_RSA_WITH_AES_256_CBC_SHA   DH 1024  FS
Android 4.3 RSA 2048 (SHA512)   TLS 1.0 TLS_DHE_RSA_WITH_AES_256_CBC_SHA   DH 1024  FS
Android 4.4.2 RSA 2048 (SHA512)   TLS 1.2 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384   DH 1024  FS
Android 5.0.0 RSA 2048 (SHA512)   TLS 1.2 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256   DH 1024  FS
Android 6.0 RSA 2048 (SHA512)   TLS 1.2 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256   DH 1024  FS
Android 7.0 RSA 2048 (SHA512)   TLS 1.2 TLS_RSA_WITH_AES_256_GCM_SHA384  No FS
Android 8.0 RSA 2048 (SHA512)   TLS 1.2 TLS_RSA_WITH_AES_256_GCM_SHA384  No FS
Android 8.1 RSA 2048 (SHA512)   TLS 1.2 TLS_RSA_WITH_AES_256_GCM_SHA384  No FS
Android 9.0 RSA 2048 (SHA512)   TLS 1.2 TLS_RSA_WITH_AES_256_GCM_SHA384  No FS
Baidu Jan 2015 RSA 2048 (SHA512)   TLS 1.0 TLS_DHE_RSA_WITH_AES_256_CBC_SHA   DH 1024  FS
BingPreview Jan 2015 RSA 2048 (SHA512)   TLS 1.2 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384   DH 1024  FS
Chrome 49 / XP SP3 RSA 2048 (SHA512)   TLS 1.2 TLS_RSA_WITH_AES_128_GCM_SHA256  No FS
Chrome 69 / Win 7  R RSA 2048 (SHA512)   TLS 1.2 TLS_RSA_WITH_AES_256_GCM_SHA384  No FS
Chrome 70 / Win 10 RSA 2048 (SHA512)   TLS 1.2 TLS_RSA_WITH_AES_256_GCM_SHA384  No FS
Chrome 80 / Win 10  R RSA 2048 (SHA512)   TLS 1.2 TLS_RSA_WITH_AES_256_GCM_SHA384  No FS
Firefox 31.3.0 ESR / Win 7 Server closed connection
Firefox 47 / Win 7  R RSA 2048 (SHA512)   TLS 1.2 TLS_DHE_RSA_WITH_AES_256_CBC_SHA   DH 1024  FS
Firefox 49 / XP SP3 RSA 2048 (SHA512)   TLS 1.2 TLS_DHE_RSA_WITH_AES_256_CBC_SHA   DH 1024  FS
Firefox 62 / Win 7  R RSA 2048 (SHA512)   TLS 1.2 TLS_RSA_WITH_AES_256_CBC_SHA  No FS
Firefox 73 / Win 10  R RSA 2048 (SHA512)   TLS 1.2 TLS_DHE_RSA_WITH_AES_256_CBC_SHA   DH 1024  FS
Googlebot Feb 2018 RSA 2048 (SHA512)   TLS 1.2 TLS_RSA_WITH_AES_256_GCM_SHA384  No FS
IE 7 / Vista RSA 2048 (SHA512)   TLS 1.0 TLS_RSA_WITH_AES_256_CBC_SHA  No FS
IE 8 / XP   No FS 1   No SNI 2 Server closed connection
IE 8-10 / Win 7  R RSA 2048 (SHA512)   TLS 1.0 TLS_RSA_WITH_AES_256_CBC_SHA  No FS
IE 11 / Win 7  R RSA 2048 (SHA512)   TLS 1.2 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384   DH 1024  FS
IE 11 / Win 8.1  R RSA 2048 (SHA512)   TLS 1.2 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384   DH 1024  FS
IE 10 / Win Phone 8.0 RSA 2048 (SHA512)   TLS 1.0 TLS_RSA_WITH_AES_256_CBC_SHA  No FS
IE 11 / Win Phone 8.1  R Server closed connection
IE 11 / Win Phone 8.1 Update  R Server closed connection
IE 11 / Win 10  R RSA 2048 (SHA512)   TLS 1.2 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384   DH 1024  FS
Edge 15 / Win 10  R RSA 2048 (SHA512)   TLS 1.2 TLS_RSA_WITH_AES_256_GCM_SHA384  No FS
Edge 16 / Win 10  R RSA 2048 (SHA512)   TLS 1.2 TLS_RSA_WITH_AES_256_GCM_SHA384  No FS
Edge 18 / Win 10  R RSA 2048 (SHA512)   TLS 1.2 TLS_RSA_WITH_AES_256_GCM_SHA384  No FS
Edge 13 / Win Phone 10  R RSA 2048 (SHA512)   TLS 1.2 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384   DH 1024  FS
Java 6u45   No SNI 2 Server closed connection
Java 7u25 RSA 2048 (SHA512)   TLS 1.0 TLS_DHE_RSA_WITH_AES_128_CBC_SHA   DH 1024  FS
Java 8u161 RSA 2048 (SHA512)   TLS 1.2 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384   DH 1024  FS
Java 11.0.3 RSA 2048 (SHA512)   TLS 1.2 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384   DH 1024  FS
Java 12.0.1 RSA 2048 (SHA512)   TLS 1.2 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384   DH 1024  FS
OpenSSL 0.9.8y RSA 2048 (SHA512)   TLS 1.0 TLS_DHE_RSA_WITH_AES_256_CBC_SHA   DH 1024  FS
OpenSSL 1.0.1l  R RSA 2048 (SHA512)   TLS 1.2 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384   DH 1024  FS
OpenSSL 1.0.2s  R RSA 2048 (SHA512)   TLS 1.2 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384   DH 1024  FS
OpenSSL 1.1.0k  R RSA 2048 (SHA512)   TLS 1.2 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384   DH 1024  FS
OpenSSL 1.1.1c  R RSA 2048 (SHA512)   TLS 1.2 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384   DH 1024  FS
Safari 5.1.9 / OS X 10.6.8 RSA 2048 (SHA512)   TLS 1.0 TLS_DHE_RSA_WITH_AES_256_CBC_SHA   DH 1024  FS
Safari 6 / iOS 6.0.1 Server closed connection
Safari 6.0.4 / OS X 10.8.4  R RSA 2048 (SHA512)   TLS 1.0 TLS_DHE_RSA_WITH_AES_256_CBC_SHA   DH 1024  FS
Safari 7 / iOS 7.1  R Server closed connection
Safari 7 / OS X 10.9  R Server closed connection
Safari 8 / iOS 8.4  R Server closed connection
Safari 8 / OS X 10.10  R Server closed connection
Safari 9 / iOS 9  R Server closed connection
Safari 9 / OS X 10.11  R Server closed connection
Safari 10 / iOS 10  R RSA 2048 (SHA512)   TLS 1.2 TLS_RSA_WITH_AES_256_GCM_SHA384  No FS
Safari 10 / OS X 10.12  R RSA 2048 (SHA512)   TLS 1.2 TLS_RSA_WITH_AES_256_GCM_SHA384  No FS
Safari 12.1.2 / MacOS 10.14.6 Beta  R RSA 2048 (SHA512)   TLS 1.2 TLS_RSA_WITH_AES_256_GCM_SHA384  No FS
Safari 12.1.1 / iOS 12.3.1  R RSA 2048 (SHA512)   TLS 1.2 TLS_RSA_WITH_AES_256_GCM_SHA384  No FS
Apple ATS 9 / iOS 9  R Server closed connection
Yahoo Slurp Jan 2015 RSA 2048 (SHA512)   TLS 1.2 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384   DH 1024  FS
YandexBot Jan 2015 RSA 2048 (SHA512)   TLS 1.2 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384   DH 1024  FS
# Not simulated clients (Protocol mismatch)
IE 6 / XP   No FS 1   No SNI 2 Protocol mismatch (not simulated)

Click here to expand

(1) Clients that do not support Forward Secrecy (FS) are excluded when determining support for it.
(2) No support for virtual SSL hosting (SNI). Connects to the default site if the server uses SNI.
(3) Only first connection attempt simulated. Browsers sometimes retry with a lower protocol version.
(R) Denotes a reference browser or client, with which we expect better effective security.
(All) We use defaults, but some platforms do not use their best protocols and features (e.g., Java 6 & 7, older IE).
(All) Certificate trust is not checked in handshake simulation, we only perform TLS handshake.


Protocol Details
Secure Renegotiation Supported
Secure Client-Initiated Renegotiation No
Insecure Client-Initiated Renegotiation No
BEAST attack Not mitigated server-side (more info)   TLS 1.0: 0x39
POODLE (SSLv3) No, SSL 3 not supported (more info)
POODLE (TLS) No (more info)
Zombie POODLE No (more info)   TLS 1.2 : 0x003c
GOLDENDOODLE No (more info)   TLS 1.2 : 0x003c
OpenSSL 0-Length No (more info)   TLS 1.2 : 0x003c
Sleeping POODLE No (more info)   TLS 1.2 : 0x003c
Downgrade attack prevention No, TLS_FALLBACK_SCSV not supported (more info)
SSL/TLS compression No
RC4 No
Heartbeat (extension) No
Heartbleed (vulnerability) No (more info)
Ticketbleed (vulnerability) No (more info)
OpenSSL CCS vuln. (CVE-2014-0224) Unknown (more info)
OpenSSL Padding Oracle vuln.
(CVE-2016-2107)		 No (more info)
ROBOT (vulnerability) No (more info)
Forward Secrecy Weak key exchange   WEAK
ALPN No
NPN No
Session resumption (caching) No (IDs assigned but not accepted)
Session resumption (tickets) No
OCSP stapling No
Strict Transport Security (HSTS) No
HSTS Preloading Not in: Chrome  Edge  Firefox  IE 
Public Key Pinning (HPKP) No (more info)
Public Key Pinning Report-Only No
Public Key Pinning (Static) No (more info)
Long handshake intolerance No
TLS extension intolerance No
TLS version intolerance No
Incorrect SNI alerts No
Uses common DH primes Yes   Replace with custom DH parameters if possible (more info)
DH public server param (Ys) reuse No
ECDH public server param reuse No, ECDHE suites not supported
Supported Named Groups -
SSL 2 handshake compatibility No


HTTP Requests
1 https://utomlansfakturering.ltblekinge.se/  (HTTP/1.1 403 Forbidden)
1
Content-Type text/html
Server Microsoft-IIS/8.5
X-Powered-By ASP.NET
Date Tue, 09 Sep 2025 10:57:38 GMT
Connection close
Content-Length 1233


Miscellaneous
Test date Tue, 09 Sep 2025 10:57:24 UTC
Test duration 151.78 seconds
HTTP status code 403
HTTP server signature Microsoft-IIS/8.5
Server hostname services.ltblekinge.se


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