Cached · just now
86/100 SECURITY SCORE

Certificate Information

Subject
CN=brand.dev
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
September 13, 2026
Valid Until
December 12, 2026 66 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
25:E5:A3:E2:0C:3F:D2:7B:3A:EB:7C:9E:59:33:74:E9:13:14:C1:0A:13:60:22:9E:10:17:B2:BE:CA:FF:4E:04
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
worker-src; object-src; base-uri; +11 more Analyze
Content-Security-Policy-Report-Only
Basic
default-src; script-src; style-src; +9 more Analyze
X-Frame-Options
Excellent
DENY
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
  • • Improve CSP by adding more specific directives and removing 'unsafe-inline'
  • • 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

Subject Alternative Names

2 domains