SSL Report: array611.prod.do.dsp.mp.microsoft.com (40.69.74.80)
Assessed on:  Mon, 09 Jun 2025 17:00:19 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 does not support TLS 1.3.  MORE INFO »
Certificate #1: EC 256 bits (SHA256withECDSA)
Server Key and Certificate #1
Subject *.prod.do.dsp.mp.microsoft.com
Fingerprint SHA256: 58f6bac3332c184f90ccaabc0a04d1d9a5fab62c097930a561fe3c25f766769b
Pin SHA256: /2F5HDBuStcpcgQUkMqBMJPtNm34qapkWpUCWipAH28=
Common names *.prod.do.dsp.mp.microsoft.com
Alternative names *.prod.do.dsp.mp.microsoft.com
Serial Number 330000005327cd597143efb877000000000053
Valid from Tue, 04 Mar 2025 20:39:31 UTC
Valid until Wed, 04 Mar 2026 20:39:31 UTC (expires in 8 months and 22 days)
Key EC 256 bits
Weak key (Debian) No
Issuer Microsoft ECC Content Distribution Secure Server CA 2.1
AIA: http://www.microsoft.com/pkiops/certs/Microsoft%20ECC%20Content%20Distribution%20Secure%20Server%20CA%202.1.crt
Signature algorithm SHA256withECDSA
Extended Validation No
Certificate Transparency No
OCSP Must Staple No
Revocation information CRL
CRL: http://www.microsoft.com/pkiops/crl/Microsoft%20ECC%20Content%20Distribution%20Secure%20Server%20CA%202.1.crl
Revocation status Good (not revoked)
DNS CAA No (more info)
Trusted No   NOT TRUSTED (Why?)
Mozilla  Apple  Android  Java  Windows 


Additional Certificates (if supplied)
Certificates provided 2 (2136 bytes)
Chain issues None
#2
Subject Microsoft ECC Content Distribution Secure Server CA 2.1
Fingerprint SHA256: e39f93f3b2b40fd3c41de7dfa7d0b0cb6c4d8f97cbab2bb81c178f4b5f3c7eed
Pin SHA256: vqzZda/5xFmPTNN3QsExaxmWVtXfDR5GHcMbx+g+p9c=
Valid until Wed, 07 Dec 2033 20:15:35 UTC (expires in 8 years and 5 months)
Key EC 384 bits
Issuer Microsoft ECC Product Root Certificate Authority 2018
Signature algorithm SHA384withECDSA


Certification Paths
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server *.prod.do.dsp.mp.microsoft.com
Fingerprint SHA256: 58f6bac3332c184f90ccaabc0a04d1d9a5fab62c097930a561fe3c25f766769b
Pin SHA256: /2F5HDBuStcpcgQUkMqBMJPtNm34qapkWpUCWipAH28=

EC 256 bits / SHA256withECDSA
2 Sent by server Microsoft ECC Content Distribution Secure Server CA 2.1
Fingerprint SHA256: e39f93f3b2b40fd3c41de7dfa7d0b0cb6c4d8f97cbab2bb81c178f4b5f3c7eed
Pin SHA256: vqzZda/5xFmPTNN3QsExaxmWVtXfDR5GHcMbx+g+p9c=

EC 384 bits / SHA384withECDSA
3 Extra download
  Not in trust store
Microsoft ECC Product Root Certificate Authority 2018   Self-signed
Fingerprint SHA256: caca93b9d23d2b6fa76e8b8471931e0df3ec6f63af3cdbb936c41954a1872326
Pin SHA256: aN7ZogP/bjZ+EqpJl3zSAPcSeoAPqm+Fnwuv7YKGpPs=

EC 384 bits / SHA384withECDSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server *.prod.do.dsp.mp.microsoft.com
Fingerprint SHA256: 58f6bac3332c184f90ccaabc0a04d1d9a5fab62c097930a561fe3c25f766769b
Pin SHA256: /2F5HDBuStcpcgQUkMqBMJPtNm34qapkWpUCWipAH28=

EC 256 bits / SHA256withECDSA
2 Sent by server Microsoft ECC Content Distribution Secure Server CA 2.1
Fingerprint SHA256: e39f93f3b2b40fd3c41de7dfa7d0b0cb6c4d8f97cbab2bb81c178f4b5f3c7eed
Pin SHA256: vqzZda/5xFmPTNN3QsExaxmWVtXfDR5GHcMbx+g+p9c=

EC 384 bits / SHA384withECDSA
3 Extra download
  Not in trust store
Microsoft ECC Product Root Certificate Authority 2018   Self-signed
Fingerprint SHA256: caca93b9d23d2b6fa76e8b8471931e0df3ec6f63af3cdbb936c41954a1872326
Pin SHA256: aN7ZogP/bjZ+EqpJl3zSAPcSeoAPqm+Fnwuv7YKGpPs=

EC 384 bits / SHA384withECDSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server *.prod.do.dsp.mp.microsoft.com
Fingerprint SHA256: 58f6bac3332c184f90ccaabc0a04d1d9a5fab62c097930a561fe3c25f766769b
Pin SHA256: /2F5HDBuStcpcgQUkMqBMJPtNm34qapkWpUCWipAH28=

EC 256 bits / SHA256withECDSA
2 Sent by server Microsoft ECC Content Distribution Secure Server CA 2.1
Fingerprint SHA256: e39f93f3b2b40fd3c41de7dfa7d0b0cb6c4d8f97cbab2bb81c178f4b5f3c7eed
Pin SHA256: vqzZda/5xFmPTNN3QsExaxmWVtXfDR5GHcMbx+g+p9c=

EC 384 bits / SHA384withECDSA
3 Extra download
  Not in trust store
Microsoft ECC Product Root Certificate Authority 2018   Self-signed
Fingerprint SHA256: caca93b9d23d2b6fa76e8b8471931e0df3ec6f63af3cdbb936c41954a1872326
Pin SHA256: aN7ZogP/bjZ+EqpJl3zSAPcSeoAPqm+Fnwuv7YKGpPs=

EC 384 bits / SHA384withECDSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server *.prod.do.dsp.mp.microsoft.com
Fingerprint SHA256: 58f6bac3332c184f90ccaabc0a04d1d9a5fab62c097930a561fe3c25f766769b
Pin SHA256: /2F5HDBuStcpcgQUkMqBMJPtNm34qapkWpUCWipAH28=

EC 256 bits / SHA256withECDSA
2 Sent by server Microsoft ECC Content Distribution Secure Server CA 2.1
Fingerprint SHA256: e39f93f3b2b40fd3c41de7dfa7d0b0cb6c4d8f97cbab2bb81c178f4b5f3c7eed
Pin SHA256: vqzZda/5xFmPTNN3QsExaxmWVtXfDR5GHcMbx+g+p9c=

EC 384 bits / SHA384withECDSA
3 Extra download
  Not in trust store
Microsoft ECC Product Root Certificate Authority 2018   Self-signed
Fingerprint SHA256: caca93b9d23d2b6fa76e8b8471931e0df3ec6f63af3cdbb936c41954a1872326
Pin SHA256: aN7ZogP/bjZ+EqpJl3zSAPcSeoAPqm+Fnwuv7YKGpPs=

EC 384 bits / SHA384withECDSA
Path #1: Trusted
1 Sent by server *.prod.do.dsp.mp.microsoft.com
Fingerprint SHA256: 58f6bac3332c184f90ccaabc0a04d1d9a5fab62c097930a561fe3c25f766769b
Pin SHA256: /2F5HDBuStcpcgQUkMqBMJPtNm34qapkWpUCWipAH28=

EC 256 bits / SHA256withECDSA
2 Sent by server Microsoft ECC Content Distribution Secure Server CA 2.1
Fingerprint SHA256: e39f93f3b2b40fd3c41de7dfa7d0b0cb6c4d8f97cbab2bb81c178f4b5f3c7eed
Pin SHA256: vqzZda/5xFmPTNN3QsExaxmWVtXfDR5GHcMbx+g+p9c=

EC 384 bits / SHA384withECDSA
3 In trust store Microsoft ECC Product Root Certificate Authority 2018   Self-signed
Fingerprint SHA256: caca93b9d23d2b6fa76e8b8471931e0df3ec6f63af3cdbb936c41954a1872326
Pin SHA256: aN7ZogP/bjZ+EqpJl3zSAPcSeoAPqm+Fnwuv7YKGpPs=

EC 384 bits / SHA384withECDSA

Click here to expand

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


Cipher Suites
# TLS 1.2 (suites in server-preferred order)
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c)   ECDH secp384r1 (eq. 7680 bits RSA)   FS 256
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b)   ECDH x25519 (eq. 3072 bits RSA)   FS 128
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (0xc024)   ECDH secp384r1 (eq. 7680 bits RSA)   FS   WEAK 256
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (0xc023)   ECDH x25519 (eq. 3072 bits RSA)   FS   WEAK 128


Handshake Simulation
Android 4.4.2 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Android 5.0.0 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Android 6.0 EC 256 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Android 7.0 EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Android 8.0 EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Android 8.1 EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Android 9.0 EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
BingPreview Jan 2015 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Chrome 49 / XP SP3 Server closed connection
Chrome 69 / Win 7  R EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Chrome 70 / Win 10 EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Chrome 80 / Win 10  R EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Firefox 31.3.0 ESR / Win 7 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Firefox 47 / Win 7  R EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Firefox 49 / XP SP3 EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Firefox 62 / Win 7  R EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Firefox 73 / Win 10  R EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Googlebot Feb 2018 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
IE 11 / Win 7  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
IE 11 / Win 8.1  R EC 256 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
IE 11 / Win Phone 8.1  R EC 256 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
IE 11 / Win Phone 8.1 Update  R EC 256 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
IE 11 / Win 10  R EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Edge 15 / Win 10  R EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Edge 16 / Win 10  R EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Edge 18 / Win 10  R EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Edge 13 / Win Phone 10  R EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Java 8u161 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Java 11.0.3 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Java 12.0.1 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
OpenSSL 1.0.1l  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
OpenSSL 1.0.2s  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
OpenSSL 1.1.0k  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
OpenSSL 1.1.1c  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Safari 6 / iOS 6.0.1 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384   ECDH secp384r1  FS
Safari 7 / iOS 7.1  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384   ECDH secp384r1  FS
Safari 7 / OS X 10.9  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384   ECDH secp384r1  FS
Safari 8 / iOS 8.4  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384   ECDH secp384r1  FS
Safari 8 / OS X 10.10  R EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384   ECDH secp384r1  FS
Safari 9 / iOS 9  R EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Safari 9 / OS X 10.11  R EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Safari 10 / iOS 10  R EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Safari 10 / OS X 10.12  R EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Safari 12.1.2 / MacOS 10.14.6 Beta  R EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Safari 12.1.1 / iOS 12.3.1  R EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Apple ATS 9 / iOS 9  R EC 256 (SHA256)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Yahoo Slurp Jan 2015 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
YandexBot Jan 2015 EC 256 (SHA256)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  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)   TLS 1.2 : 0xc023
GOLDENDOODLE No (more info)   TLS 1.2 : 0xc023
OpenSSL 0-Length No (more info)   TLS 1.2 : 0xc023
Sleeping POODLE No (more info)   TLS 1.2 : 0xc023
Downgrade attack prevention Unknown (requires support for at least two protocols, excl. SSL2)
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   h2 http/1.1
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 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 secp384r1, x25519, secp256r1 (server preferred order)
SSL 2 handshake compatibility No


HTTP Requests
1 https://array611.prod.do.dsp.mp.microsoft.com/  (HTTP/1.1 403 Forbidden)
1
Content-Type text/html
Server Microsoft-IIS/10.0
X-Powered-By ASP.NET
Date Mon, 09 Jun 2025 16:59:18 GMT
Connection close
Content-Length 1233


Miscellaneous
Test date Mon, 09 Jun 2025 16:59:06 UTC
Test duration 72.801 seconds
HTTP status code 403
HTTP server signature Microsoft-IIS/10.0
Server hostname -


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