Cached · just now
88/100 SECURITY SCORE

Certificate Information

Subject
CN=locticians.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
December 20, 2025
Valid Until
March 20, 2026 76 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
EF:A1:9A:53:19:4C:C4:23:72:D3:76:E4:B8:F4:FA:63:AF:AD:CD:96:A7:70:F1:3A:B8:BC:7C:DF:41:BF:79:48
Alternative Names

Security Configuration

TLS Protocols
TLS 1.0 TLS 1.1 TLS 1.2 TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)
Warnings
  • 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
Present
max-age=63072000
Content-Security-Policy
Basic
script-src; object-src; base-uri; +9 more
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin
Permissions-Policy
Present
accelerometer=*,autoplay=*,camera=*,encrypted-media=*,fullscreen=*,geolocation=*,gyroscope=*,magnetometer=*,microphone=*,sync-xhr=*,usb=*,payment=*
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Improve CSP by adding more specific directives and removing 'unsafe-inline'
  • 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

Subject Alternative Names

2 domains