Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=paladinsoftware.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
January 19, 2026
Valid Until
April 19, 2026
85 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
FC:4A:E0:F5:2C:11:AD:16:A0:E1:C5:1F:E6:FF:8E:11:9C:87:14:95:DB:18:3F:5B:A6:88:30:77:C0:56:59:3D
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
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
Good
default-src; font-src; img-src; +5 more
default-src 'self' https:; font-src 'self' https: data:; img-src 'self' https: data:; object-src 'none'; script-src 'self' *.google-analytics.com cdn.cookielaw.org 'nonce-YfvwRexX2deYiaOjR1ekOw=='; style-src 'self' https: 'unsafe-inline'; connect-src 'self' https:; report-uri /csp_violation_report
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Strengthen CSP by removing 'unsafe-eval'
- • 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