DNS Gurus

SSL Verification Bypassed

The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.

Reason:

Expired Certificate - the server's certificate has expired

Cached · just now
48/100 SECURITY SCORE

Certificate Information

Subject
UNKNOWN=03379831, UNKNOWN={:asn1_OPENTYPE, <<19, 2, 71, 66>>}, UNKNOWN={:asn1_OPENTYPE, <<19, 20, 80, 114, 105, 118, 97, 116, 101, 32, 79, 114, 103, 97, 110, 105, 122, 97, 116, 105, 111, 110>>}, C=GB, UNKNOWN={:asn1_OPENTYPE, <<19, 8, 66, 83, 49, 54, 32, 49, 70, 88>>}, ST=England, L=Bristol, UNKNOWN={:asn1_OPENTYPE, <<19, 36, 83, 105, 109, 119, 111, 111, 100, 32, 72, 111, 117, 115, 101, 44, 32, 67, 117, 98, 101, 32, 77, 52, 32, 66, 117, 115, 105, 110, 101, 115, 115, 32, 80, 97, 114, 107>>}, O=Simwood eSMS Limited, OU=COMODO EV Multi-Domain SSL, CN=simwood.com
Issuer
C=GB, ST=Greater Manchester, L=Salford, O=Sectigo Limited, CN=Sectigo RSA Extended Validation Secure Server CA
Valid From
February 13, 2019
Valid Until
February 13, 2021 Expired
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
B5:D6:D4:28:1E:DA:39:25:7C:93:DC:ED:57:49:83:CA:92:84:A7:73:22:B1:3B:D3:99:99:D2:1A:39:DC:4F:75
Alternative Names
5 domains

Security Configuration

TLS Protocols
TLS 1.0 TLS 1.1 TLS 1.2
Forward Secrecy
Limited (Check cipher configuration)
Warnings
  • • TLS 1.3 is not supported (recommended)
  • • TLS 1.1 is deprecated and should be disabled
  • • TLS 1.0 is deprecated and should be disabled

HTTP Security Headers

Status
Strict-Transport-Security
Missing
Not configured
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Add Strict-Transport-Security header with max-age of at least 1 year
  • • Add Content-Security-Policy header to prevent XSS attacks
  • • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • Add X-Content-Type-Options: nosniff
  • • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
  • • Consider adding Permissions-Policy to control browser features

CAA Records (Certificate Authority Authorization)

CAA Records
Not Configured (Any CA can issue certificates)
CAA Issues
  • • No CAA records configured - any CA can issue certificates
Recommendations
  • • Implement CAA records to restrict which CAs can issue certificates for your domain
  • • This adds an extra layer of security against unauthorized certificate issuance
  • • Example: Add CAA record 'example.com. CAA 0 issue "letsencrypt.org"'
  • • Consider adding 'iodef' record to receive security incident reports