Open Cached · just now
87/100 SECURITY SCORE

Certificate Information

Subject
UNKNOWN=04058690, 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=Manchester, O=Sectigo Limited, CN=www.sslcertificaten.nl
Issuer
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA EV R36
Valid From
August 26, 2025
Valid Until
August 26, 2026 292 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
D5:D0:7F:EB:AE:E5:FA:76:70:06:EF:4C:06:78:B1:E1:BC:5F:DC:02:73:9D:4F:2E:A6:8F:36:3E:7B:62:8C:22
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=31536000; includeSubdomains; preload
Content-Security-Policy
Basic
default-src; font-src; img-src; +4 more
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Improve CSP by adding more specific directives and removing 'unsafe-inline'
  • 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