DNS Gurus
Cached · just now
87/100 SECURITY SCORE

Certificate Information

Subject
CN=analytics.commit.works
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
January 31, 2026
Valid Until
May 01, 2026 88 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
0A:47:1F:E6:CE:49:BD:7A:A1:02:DB:87:76:58:4D:94:CC:6C:D0:CC:49:33:7E:5A:5B:FD:C4:D7:E4:9C:49:D7
Alternative Names
16 domains

Security Configuration

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

HTTP Security Headers

Status
Strict-Transport-Security
Excellent
max-age=64072000; includeSubDomains; preload
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
no-referrer, strict-origin-when-cross-origin
Permissions-Policy
Present
clipboard-read=(self), geolocation=(self), camera=(self), microphone=(self), clipboard-write=(self), payment=(), usb=(), display-capture=(self)
Recommendations
  • • Add Content-Security-Policy header to prevent XSS attacks
  • • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking

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