Cached · just now
86/100 SECURITY SCORE

Certificate Information

Subject
C=SE, ST=Stockholms län, O=Assa Abloy AB, CN=www.kwikset.com
Issuer
C=US, O=Corporation Service Company, CN=Corporation Service Company RSA OV SSL CA
Valid From
February 27, 2025
Valid Until
February 27, 2026 40 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
8D:21:3F:67:8F:62:B5:25:A4:6B:85:20:1E:BC:01:29:A9:A7:AF:43:ED:78:96:3C:DA:23:4E:80:64:6E:58:08
Alternative Names

Security Configuration

TLS Protocols
TLS 1.2 TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)

HTTP Security Headers

Status
Strict-Transport-Security
Present
max-age=37889238
Content-Security-Policy
Weak
block-all-mixed-content; frame-ancestors; upgrade-insecure-requests
X-Frame-Options
Present
ALLOW-FROM https://www.menards.com/
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
accelerometer=(),camera=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=()
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Significantly strengthen CSP directives
  • Add X-Content-Type-Options: nosniff

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