Open Cached · just now
82/100 SECURITY SCORE

Certificate Information

Subject
UNKNOWN=03913408, 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, ST=Worcestershire, O=Team Blue Internet Services UK Limited, CN=www.names.co.uk
Issuer
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA EV R36
Valid From
October 07, 2025
Valid Until
October 07, 2026 331 days
Public Key
RSA 4096 bit Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
EC:FD:8D:21:4E:A5:BE:90:6D:55:E5:A9:2F:B9:60:F5:C3:AC:AA:E3:A8:D7:82:AC:0C:1D:D8:3B:BE:29:8F:3A
Alternative Names

Security Configuration

TLS Protocols
TLS 1.2
Forward Secrecy
Limited (Check cipher configuration)
Warnings
  • TLS 1.3 is not supported (recommended)

HTTP Security Headers

Status
Strict-Transport-Security
Present
max-age=15552000
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Add Content-Security-Policy header to prevent XSS attacks
  • 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