SSL Report: demo.efaktura.bg (193.41.190.23)
Assessed on:  Wed, 18 Jun 2025 06:28:38 UTC | Clear cache

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: A
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 TLS 1.3.  MORE INFO »
HTTP Strict Transport Security (HSTS) with long duration deployed on this server.  MORE INFO »
DNS Certification Authority Authorization (CAA) Policy found for this domain.  MORE INFO »
Certificate #1: RSA 2048 bits (SHA256withRSA)
Server Key and Certificate #1
Subject *.efaktura.bg
Fingerprint SHA256: f44064e2c14688d6266f643da1995310f7a1050e6366786e50e9985c35bfaa3b
Pin SHA256: tbzgJq6VFf48RbFGHpxjaIvjyoY5I4X1ANgOwwq3/08=
Common names *.efaktura.bg
Alternative names *.efaktura.bg
Serial Number 724d1e65d3d83b83
Valid from Mon, 26 Jun 2023 12:35:43 UTC
Valid until Sun, 28 Sep 2025 12:35:43 UTC (expires in 3 months and 9 days)
Key RSA 2048 bits (e 65537)
Weak key (Debian) No
Issuer B-Trust Operational Advanced CA
AIA: http://ca.b-trust.org/repository/B-TrustOperationalACA.cer
Signature algorithm SHA256withRSA
Extended Validation No
Certificate Transparency No
OCSP Must Staple No
Revocation information CRL, OCSP
CRL: http://crl.b-trust.org/repository/B-TrustOperationalACA.crl
OCSP: http://ocsp.b-trust.org
Revocation status Unchecked (only trusted certificates can be checked)
DNS CAA Yes
policy host: efaktura.bg
issue: b-trust.org flags:0
issue: sectigo.com flags:0
iodef: mailto:admin@borica.bg flags:0
Trusted No   NOT TRUSTED (Why?)
Mozilla  Apple  Android  Java  Windows 


Additional Certificates (if supplied)
Certificates provided 3 (5368 bytes)
Chain issues Incorrect order, Contains anchor
#2
Subject B-Trust Root Advanced CA   Not in trust store
Fingerprint SHA256: fb2c736f3cf1ad7c89ec36e860c90cd6be87f70d66098e0accd54a49eafa2ca9
Pin SHA256: SnjKI1jpp7cGgIK6ObkdmfCRTlMj+CECZK8lpd3OdrY=
Valid until Fri, 24 Apr 2037 15:55:40 UTC (expires in 11 years and 10 months)
Key RSA 4096 bits (e 48249)
Issuer B-Trust Root Advanced CA   Self-signed
Signature algorithm SHA256withRSA
#3
Subject B-Trust Operational Advanced CA
Fingerprint SHA256: 5b3ba3dbfffa39a2d622c29df7af436406a761785d240b48be7ac2f267b6dac8
Pin SHA256: c1DZhvys/879RRMyAMuWVxZu0UEZ+hDk32FzvmQu8Ok=
Valid until Fri, 23 Apr 2032 16:07:09 UTC (expires in 6 years and 10 months)
Key RSA 4096 bits (e 34999)
Issuer B-Trust Root Advanced CA
Signature algorithm SHA256withRSA


Certification Paths
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server *.efaktura.bg
Fingerprint SHA256: f44064e2c14688d6266f643da1995310f7a1050e6366786e50e9985c35bfaa3b
Pin SHA256: tbzgJq6VFf48RbFGHpxjaIvjyoY5I4X1ANgOwwq3/08=

RSA 2048 bits (e 65537) / SHA256withRSA
2 Sent by server B-Trust Operational Advanced CA
Fingerprint SHA256: 5b3ba3dbfffa39a2d622c29df7af436406a761785d240b48be7ac2f267b6dac8
Pin SHA256: c1DZhvys/879RRMyAMuWVxZu0UEZ+hDk32FzvmQu8Ok=

RSA 4096 bits (e 34999) / SHA256withRSA
3 Sent by server
  Not in trust store
B-Trust Root Advanced CA   Self-signed
Fingerprint SHA256: fb2c736f3cf1ad7c89ec36e860c90cd6be87f70d66098e0accd54a49eafa2ca9
Pin SHA256: SnjKI1jpp7cGgIK6ObkdmfCRTlMj+CECZK8lpd3OdrY=

RSA 4096 bits (e 48249) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server *.efaktura.bg
Fingerprint SHA256: f44064e2c14688d6266f643da1995310f7a1050e6366786e50e9985c35bfaa3b
Pin SHA256: tbzgJq6VFf48RbFGHpxjaIvjyoY5I4X1ANgOwwq3/08=

RSA 2048 bits (e 65537) / SHA256withRSA
2 Sent by server B-Trust Operational Advanced CA
Fingerprint SHA256: 5b3ba3dbfffa39a2d622c29df7af436406a761785d240b48be7ac2f267b6dac8
Pin SHA256: c1DZhvys/879RRMyAMuWVxZu0UEZ+hDk32FzvmQu8Ok=

RSA 4096 bits (e 34999) / SHA256withRSA
3 Sent by server
  Not in trust store
B-Trust Root Advanced CA   Self-signed
Fingerprint SHA256: fb2c736f3cf1ad7c89ec36e860c90cd6be87f70d66098e0accd54a49eafa2ca9
Pin SHA256: SnjKI1jpp7cGgIK6ObkdmfCRTlMj+CECZK8lpd3OdrY=

RSA 4096 bits (e 48249) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server *.efaktura.bg
Fingerprint SHA256: f44064e2c14688d6266f643da1995310f7a1050e6366786e50e9985c35bfaa3b
Pin SHA256: tbzgJq6VFf48RbFGHpxjaIvjyoY5I4X1ANgOwwq3/08=

RSA 2048 bits (e 65537) / SHA256withRSA
2 Sent by server B-Trust Operational Advanced CA
Fingerprint SHA256: 5b3ba3dbfffa39a2d622c29df7af436406a761785d240b48be7ac2f267b6dac8
Pin SHA256: c1DZhvys/879RRMyAMuWVxZu0UEZ+hDk32FzvmQu8Ok=

RSA 4096 bits (e 34999) / SHA256withRSA
3 Sent by server
  Not in trust store
B-Trust Root Advanced CA   Self-signed
Fingerprint SHA256: fb2c736f3cf1ad7c89ec36e860c90cd6be87f70d66098e0accd54a49eafa2ca9
Pin SHA256: SnjKI1jpp7cGgIK6ObkdmfCRTlMj+CECZK8lpd3OdrY=

RSA 4096 bits (e 48249) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server *.efaktura.bg
Fingerprint SHA256: f44064e2c14688d6266f643da1995310f7a1050e6366786e50e9985c35bfaa3b
Pin SHA256: tbzgJq6VFf48RbFGHpxjaIvjyoY5I4X1ANgOwwq3/08=

RSA 2048 bits (e 65537) / SHA256withRSA
2 Sent by server B-Trust Operational Advanced CA
Fingerprint SHA256: 5b3ba3dbfffa39a2d622c29df7af436406a761785d240b48be7ac2f267b6dac8
Pin SHA256: c1DZhvys/879RRMyAMuWVxZu0UEZ+hDk32FzvmQu8Ok=

RSA 4096 bits (e 34999) / SHA256withRSA
3 Sent by server
  Not in trust store
B-Trust Root Advanced CA   Self-signed
Fingerprint SHA256: fb2c736f3cf1ad7c89ec36e860c90cd6be87f70d66098e0accd54a49eafa2ca9
Pin SHA256: SnjKI1jpp7cGgIK6ObkdmfCRTlMj+CECZK8lpd3OdrY=

RSA 4096 bits (e 48249) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server *.efaktura.bg
Fingerprint SHA256: f44064e2c14688d6266f643da1995310f7a1050e6366786e50e9985c35bfaa3b
Pin SHA256: tbzgJq6VFf48RbFGHpxjaIvjyoY5I4X1ANgOwwq3/08=

RSA 2048 bits (e 65537) / SHA256withRSA
2 Sent by server B-Trust Operational Advanced CA
Fingerprint SHA256: 5b3ba3dbfffa39a2d622c29df7af436406a761785d240b48be7ac2f267b6dac8
Pin SHA256: c1DZhvys/879RRMyAMuWVxZu0UEZ+hDk32FzvmQu8Ok=

RSA 4096 bits (e 34999) / SHA256withRSA
3 Sent by server
  Not in trust store
B-Trust Root Advanced CA   Self-signed
Fingerprint SHA256: fb2c736f3cf1ad7c89ec36e860c90cd6be87f70d66098e0accd54a49eafa2ca9
Pin SHA256: SnjKI1jpp7cGgIK6ObkdmfCRTlMj+CECZK8lpd3OdrY=

RSA 4096 bits (e 48249) / SHA256withRSA

Click here to expand

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


Cipher Suites
# TLS 1.3 (suites in server-preferred order)
TLS_AES_256_GCM_SHA384 (0x1302)   ECDH x25519 (eq. 3072 bits RSA)   FS 256
TLS_CHACHA20_POLY1305_SHA256 (0x1303)   ECDH x25519 (eq. 3072 bits RSA)   FS 256
TLS_AES_128_GCM_SHA256 (0x1301)   ECDH x25519 (eq. 3072 bits RSA)   FS 128
# TLS 1.2 (suites in server-preferred order)
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)   ECDH secp256r1 (eq. 3072 bits RSA)   FS 256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca8)   ECDH secp256r1 (eq. 3072 bits RSA)   FS 256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)   ECDH secp256r1 (eq. 3072 bits RSA)   FS 128


Handshake Simulation
Android 4.4.2 RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Android 5.0.0 RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Android 6.0 RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Android 7.0 RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Android 8.0 RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Android 8.1 -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Android 9.0 -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
BingPreview Jan 2015 RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Chrome 49 / XP SP3 RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256   ECDH secp256r1  FS
Chrome 69 / Win 7  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Chrome 70 / Win 10 -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Chrome 80 / Win 10  R -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Firefox 31.3.0 ESR / Win 7 RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Firefox 47 / Win 7  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256   ECDH secp256r1  FS
Firefox 49 / XP SP3 RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Firefox 62 / Win 7  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Firefox 73 / Win 10  R -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Googlebot Feb 2018 RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
IE 11 / Win 7  R Server sent fatal alert: handshake_failure
IE 11 / Win 8.1  R Server sent fatal alert: handshake_failure
IE 11 / Win Phone 8.1  R Server sent fatal alert: handshake_failure
IE 11 / Win Phone 8.1 Update  R Server sent fatal alert: handshake_failure
IE 11 / Win 10  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Edge 15 / Win 10  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Edge 16 / Win 10  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Edge 18 / Win 10  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Edge 13 / Win Phone 10  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Java 8u161 RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Java 11.0.3 -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH secp256r1  FS
Java 12.0.1 -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH secp256r1  FS
OpenSSL 1.0.1l  R RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
OpenSSL 1.0.2s  R RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
OpenSSL 1.1.0k  R RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
OpenSSL 1.1.1c  R -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Safari 6 / iOS 6.0.1 Server sent fatal alert: handshake_failure
Safari 7 / iOS 7.1  R Server sent fatal alert: handshake_failure
Safari 7 / OS X 10.9  R Server sent fatal alert: handshake_failure
Safari 8 / iOS 8.4  R Server sent fatal alert: handshake_failure
Safari 8 / OS X 10.10  R Server sent fatal alert: handshake_failure
Safari 9 / iOS 9  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Safari 9 / OS X 10.11  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Safari 10 / iOS 10  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Safari 10 / OS X 10.12  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Safari 12.1.2 / MacOS 10.14.6 Beta  R -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Safari 12.1.1 / iOS 12.3.1  R -   TLS 1.3 TLS_AES_256_GCM_SHA384   ECDH x25519  FS
Apple ATS 9 / iOS 9  R RSA 2048 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Yahoo Slurp Jan 2015 RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
YandexBot Jan 2015 RSA 2048 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
# Not simulated clients (Protocol mismatch)
Android 2.3.7   No SNI 2 Protocol mismatch (not simulated)
Android 4.0.4 Protocol mismatch (not simulated)
Android 4.1.1 Protocol mismatch (not simulated)
Android 4.2.2 Protocol mismatch (not simulated)
Android 4.3 Protocol mismatch (not simulated)
Baidu Jan 2015 Protocol mismatch (not simulated)
IE 6 / XP   No FS 1   No SNI 2 Protocol mismatch (not simulated)
IE 7 / Vista Protocol mismatch (not simulated)
IE 8 / XP   No FS 1   No SNI 2 Protocol mismatch (not simulated)
IE 8-10 / Win 7  R Protocol mismatch (not simulated)
IE 10 / Win Phone 8.0 Protocol mismatch (not simulated)
Java 6u45   No SNI 2 Protocol mismatch (not simulated)
Java 7u25 Protocol mismatch (not simulated)
OpenSSL 0.9.8y Protocol mismatch (not simulated)
Safari 5.1.9 / OS X 10.6.8 Protocol mismatch (not simulated)
Safari 6.0.4 / OS X 10.8.4  R 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 Mitigated server-side (more info)  
POODLE (SSLv3) No, SSL 3 not supported (more info)
POODLE (TLS) No (more info)
Zombie POODLE No (more info)  
GOLDENDOODLE No (more info)  
OpenSSL 0-Length No (more info)  
Sleeping POODLE No (more info)  
Downgrade attack prevention Yes, TLS_FALLBACK_SCSV 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) No (more info)
OpenSSL Padding Oracle vuln.
(CVE-2016-2107)
No (more info)
ROBOT (vulnerability) No (more info)
Forward Secrecy Yes (with most browsers)   ROBUST (more info)
ALPN Yes   http/1.1
NPN No
Session resumption (caching) Yes
Session resumption (tickets) Yes
OCSP stapling No
Strict Transport Security (HSTS) Yes
max-age=31536000; includeSubDomains
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 No, DHE suites not supported
DH public server param (Ys) reuse No, DHE suites not supported
ECDH public server param reuse No
Supported Named Groups secp256r1, secp384r1, secp521r1, x25519, x448 (server preferred order)
SSL 2 handshake compatibility No
0-RTT enabled No


HTTP Requests
1 https://demo.efaktura.bg/  (HTTP/1.1 200 OK)
1
Date Wed, 18 Jun 2025 06:26:54 GMT
Server Apache
X-Frame-Options SAMEORIGIN
Content-Security-Policy frame-ancestors 'self'
X-XSS-Protection 1; mode=block
X-Content-Type-Options nosniff
Referrer-Policy no-referrer-when-downgrade
X-Frame-Options SAMEORIGIN
Content-Security-Policy frame-ancestors 'self'
X-XSS-Protection 1; mode=block
Expires Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control no-store, no-cache, must-revalidate
Pragma no-cache
Content-Length 4662
Content-Type text/html; charset=win-1251
Via 1.1 demo.efaktura.bg
Strict-Transport-Security max-age=31536000; includeSubDomains
Set-Cookie PHPSESSID=2e3tjs1k2annb701utb4dd7l0js4h9dlebvrtnt8gtrvd02p75t0; path=/; domain=demo.efaktura.bg; secure; HttpOnly;HttpOnly;Secure
Connection close


Miscellaneous
Test date Wed, 18 Jun 2025 06:27:21 UTC
Test duration 77.225 seconds
HTTP status code 200
HTTP server signature Apache
Server hostname net190.bobs.bg


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.0