SSL Report: www.electricalcompetentperson.co.uk (20.67.208.9)
Assessed on:  Mon, 09 Jun 2025 10:41:04 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: RSA 4096 bits (SHA256withRSA)
Server Key and Certificate #1
Subject *.installsure.co.uk
Fingerprint SHA256: 231c8deb6cb38039dc008caba8a08d8c5459cb390754467d43835f80d6101854
Pin SHA256: GVKgxG93C38skboF46JFYTbb30EvDgN94iJ78iqWi9Q=
Common names *.installsure.co.uk
Alternative names *.installsure.co.uk installsure.co.uk   MISMATCH
Serial Number 04ff567cf2c57bf7234ab7ab54dcdda5
Valid from Fri, 20 Sep 2024 00:00:00 UTC
Valid until Fri, 19 Sep 2025 23:59:59 UTC (expires in 3 months and 10 days)
Key RSA 4096 bits (e 65537)
Weak key (Debian) No
Issuer GeoTrust TLS RSA CA G1
AIA: http://cacerts.geotrust.com/GeoTrustTLSRSACAG1.crt
Signature algorithm SHA256withRSA
Extended Validation No
Certificate Transparency Yes (certificate)
OCSP Must Staple No
Revocation information CRL, OCSP
CRL: http://cdp.geotrust.com/GeoTrustTLSRSACAG1.crl
OCSP: http://status.geotrust.com
Revocation status Good (not revoked)
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 (3090 bytes)
Chain issues None
#2
Subject GeoTrust TLS RSA CA G1
Fingerprint SHA256: c06e307f7cfc1d32fa72a4c033c87b90019af216f0775d64978a2eca6c8a230e
Pin SHA256: SDG5orEv8iX6MNenIAxa8nQFNpROB/6+llsZdXHZNqs=
Valid until Tue, 02 Nov 2027 12:23:37 UTC (expires in 2 years and 4 months)
Key RSA 2048 bits (e 65537)
Issuer DigiCert Global Root G2
Signature algorithm SHA256withRSA


Certification Paths
Path #1: Not trusted (invalid certificate [Fingerprint SHA256: 231c8deb6cb38039dc008caba8a08d8c5459cb390754467d43835f80d6101854])
1 Sent by server *.installsure.co.uk
Fingerprint SHA256: 231c8deb6cb38039dc008caba8a08d8c5459cb390754467d43835f80d6101854
Pin SHA256: GVKgxG93C38skboF46JFYTbb30EvDgN94iJ78iqWi9Q=

RSA 4096 bits (e 65537) / SHA256withRSA
CRL ERROR: IOException occurred
2 Sent by server GeoTrust TLS RSA CA G1
Fingerprint SHA256: c06e307f7cfc1d32fa72a4c033c87b90019af216f0775d64978a2eca6c8a230e
Pin SHA256: SDG5orEv8iX6MNenIAxa8nQFNpROB/6+llsZdXHZNqs=

RSA 2048 bits (e 65537) / SHA256withRSA
CRL ERROR: IOException occurred
3 In trust store DigiCert Global Root G2   Self-signed
Fingerprint SHA256: cb3ccbb76031e5e0138f8dd39a23f9de47ffc35e43c1144cea27d46a5ab1cb5f
Pin SHA256: i7WTqTvh0OioIruIfFR4kMPnBqrS2rdiVPl/s2uC/CY=

RSA 2048 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (invalid certificate [Fingerprint SHA256: 231c8deb6cb38039dc008caba8a08d8c5459cb390754467d43835f80d6101854])
1 Sent by server *.installsure.co.uk
Fingerprint SHA256: 231c8deb6cb38039dc008caba8a08d8c5459cb390754467d43835f80d6101854
Pin SHA256: GVKgxG93C38skboF46JFYTbb30EvDgN94iJ78iqWi9Q=

RSA 4096 bits (e 65537) / SHA256withRSA
CRL ERROR: IOException occurred
2 Sent by server GeoTrust TLS RSA CA G1
Fingerprint SHA256: c06e307f7cfc1d32fa72a4c033c87b90019af216f0775d64978a2eca6c8a230e
Pin SHA256: SDG5orEv8iX6MNenIAxa8nQFNpROB/6+llsZdXHZNqs=

RSA 2048 bits (e 65537) / SHA256withRSA
CRL ERROR: IOException occurred
3 In trust store DigiCert Global Root G2   Self-signed
Fingerprint SHA256: cb3ccbb76031e5e0138f8dd39a23f9de47ffc35e43c1144cea27d46a5ab1cb5f
Pin SHA256: i7WTqTvh0OioIruIfFR4kMPnBqrS2rdiVPl/s2uC/CY=

RSA 2048 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (invalid certificate [Fingerprint SHA256: 231c8deb6cb38039dc008caba8a08d8c5459cb390754467d43835f80d6101854])
1 Sent by server *.installsure.co.uk
Fingerprint SHA256: 231c8deb6cb38039dc008caba8a08d8c5459cb390754467d43835f80d6101854
Pin SHA256: GVKgxG93C38skboF46JFYTbb30EvDgN94iJ78iqWi9Q=

RSA 4096 bits (e 65537) / SHA256withRSA
CRL ERROR: IOException occurred
2 Sent by server GeoTrust TLS RSA CA G1
Fingerprint SHA256: c06e307f7cfc1d32fa72a4c033c87b90019af216f0775d64978a2eca6c8a230e
Pin SHA256: SDG5orEv8iX6MNenIAxa8nQFNpROB/6+llsZdXHZNqs=

RSA 2048 bits (e 65537) / SHA256withRSA
CRL ERROR: IOException occurred
3 In trust store DigiCert Global Root G2   Self-signed
Fingerprint SHA256: cb3ccbb76031e5e0138f8dd39a23f9de47ffc35e43c1144cea27d46a5ab1cb5f
Pin SHA256: i7WTqTvh0OioIruIfFR4kMPnBqrS2rdiVPl/s2uC/CY=

RSA 2048 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (invalid certificate [Fingerprint SHA256: 231c8deb6cb38039dc008caba8a08d8c5459cb390754467d43835f80d6101854])
1 Sent by server *.installsure.co.uk
Fingerprint SHA256: 231c8deb6cb38039dc008caba8a08d8c5459cb390754467d43835f80d6101854
Pin SHA256: GVKgxG93C38skboF46JFYTbb30EvDgN94iJ78iqWi9Q=

RSA 4096 bits (e 65537) / SHA256withRSA
CRL ERROR: IOException occurred
2 Sent by server GeoTrust TLS RSA CA G1
Fingerprint SHA256: c06e307f7cfc1d32fa72a4c033c87b90019af216f0775d64978a2eca6c8a230e
Pin SHA256: SDG5orEv8iX6MNenIAxa8nQFNpROB/6+llsZdXHZNqs=

RSA 2048 bits (e 65537) / SHA256withRSA
CRL ERROR: IOException occurred
3 In trust store DigiCert Global Root G2   Self-signed
Fingerprint SHA256: cb3ccbb76031e5e0138f8dd39a23f9de47ffc35e43c1144cea27d46a5ab1cb5f
Pin SHA256: i7WTqTvh0OioIruIfFR4kMPnBqrS2rdiVPl/s2uC/CY=

RSA 2048 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (invalid certificate [Fingerprint SHA256: 231c8deb6cb38039dc008caba8a08d8c5459cb390754467d43835f80d6101854])
1 Sent by server *.installsure.co.uk
Fingerprint SHA256: 231c8deb6cb38039dc008caba8a08d8c5459cb390754467d43835f80d6101854
Pin SHA256: GVKgxG93C38skboF46JFYTbb30EvDgN94iJ78iqWi9Q=

RSA 4096 bits (e 65537) / SHA256withRSA
CRL ERROR: IOException occurred
2 Sent by server GeoTrust TLS RSA CA G1
Fingerprint SHA256: c06e307f7cfc1d32fa72a4c033c87b90019af216f0775d64978a2eca6c8a230e
Pin SHA256: SDG5orEv8iX6MNenIAxa8nQFNpROB/6+llsZdXHZNqs=

RSA 2048 bits (e 65537) / SHA256withRSA
CRL ERROR: IOException occurred
3 In trust store DigiCert Global Root G2   Self-signed
Fingerprint SHA256: cb3ccbb76031e5e0138f8dd39a23f9de47ffc35e43c1144cea27d46a5ab1cb5f
Pin SHA256: i7WTqTvh0OioIruIfFR4kMPnBqrS2rdiVPl/s2uC/CY=

RSA 2048 bits (e 65537) / SHA256withRSA

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_RSA_WITH_AES_256_GCM_SHA384 (0xc030)   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
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013)   ECDH secp256r1 (eq. 3072 bits RSA)   FS   WEAK 128
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)   ECDH secp256r1 (eq. 3072 bits RSA)   FS   WEAK 256
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


Handshake Simulation
Android 4.4.2 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Android 5.0.0 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Android 6.0 RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Android 7.0 RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Android 8.0 RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Android 8.1 RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Android 9.0 RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
BingPreview Jan 2015 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Chrome 49 / XP SP3 RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Chrome 69 / Win 7  R RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Chrome 70 / Win 10 RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Chrome 80 / Win 10  R RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Firefox 31.3.0 ESR / Win 7 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Firefox 47 / Win 7  R RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Firefox 49 / XP SP3 RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Firefox 62 / Win 7  R RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Firefox 73 / Win 10  R RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Googlebot Feb 2018 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
IE 11 / Win 7  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA   ECDH secp256r1  FS
IE 11 / Win 8.1  R RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA   ECDH secp256r1  FS
IE 11 / Win Phone 8.1  R RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA   ECDH secp256r1  FS
IE 11 / Win Phone 8.1 Update  R RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA   ECDH secp256r1  FS
IE 11 / Win 10  R RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Edge 15 / Win 10  R RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Edge 16 / Win 10  R RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Edge 18 / Win 10  R RSA 4096 (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 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Java 8u161 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Java 11.0.3 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Java 12.0.1 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
OpenSSL 1.0.1l  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
OpenSSL 1.0.2s  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
OpenSSL 1.1.0k  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
OpenSSL 1.1.1c  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Safari 6 / iOS 6.0.1 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA   ECDH secp256r1  FS
Safari 7 / iOS 7.1  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA   ECDH secp256r1  FS
Safari 7 / OS X 10.9  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA   ECDH secp256r1  FS
Safari 8 / iOS 8.4  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA   ECDH secp256r1  FS
Safari 8 / OS X 10.10  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA   ECDH secp256r1  FS
Safari 9 / iOS 9  R RSA 4096 (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 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Safari 10 / iOS 10  R RSA 4096 (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 4096 (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 RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Safari 12.1.1 / iOS 12.3.1  R RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Apple ATS 9 / iOS 9  R RSA 4096 (SHA256)   TLS 1.2 > http/1.1   TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
Yahoo Slurp Jan 2015 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp256r1  FS
YandexBot Jan 2015 RSA 4096 (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)   TLS 1.2 : 0xc013
GOLDENDOODLE No (more info)   TLS 1.2 : 0xc013
OpenSSL 0-Length No (more info)   TLS 1.2 : 0xc013
Sleeping POODLE No (more info)   TLS 1.2 : 0xc013
Downgrade attack prevention Unknown (requires support for at least two protocols, excl. SSL2)
SSL/TLS compression No
RC4 No
Heartbeat (extension) Yes
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 Yes   http/1.1
Session resumption (caching) No (IDs assigned but not accepted)
Session resumption (tickets) Yes
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 secp256r1, secp521r1, brainpoolP512r1, brainpoolP384r1, secp384r1, brainpoolP256r1, secp256k1, sect571r1, sect571k1, sect409k1, sect409r1, sect283k1, sect283r1 (server preferred order)
SSL 2 handshake compatibility Yes


HTTP Requests
1 https://www.electricalcompetentperson.co.uk/  (HTTP/1.1 404 Not Found)
1
Server Microsoft-Azure-Application-Gateway/v2
Date Mon, 09 Jun 2025 10:39:06 GMT
Content-Type text/html
Content-Length 179
Connection close


Miscellaneous
Test date Mon, 09 Jun 2025 10:38:56 UTC
Test duration 128.538 seconds
HTTP status code 404
HTTP server signature Microsoft-Azure-Application-Gateway/v2
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