Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
CN=liveactiongolf.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
November 20, 2025
Valid Until
February 18, 2026
54 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
F1:B6:4D:6B:27:41:05:03:E0:E9:39:1B:31:E4:9F:C5:92:F0:D2:1D:A6:D3:E9:ED:5B:93:0C:F5:0C:E0:AF:98
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=31536000
Content-Security-Policy
Basic
upgrade-insecure-requests; base-uri; object-src; +4 more
upgrade-insecure-requests; base-uri 'self'; object-src 'none'; script-src https://liveactiongolf.com/logs/ https://liveactiongolf.com/sidekiq/ https://liveactiongolf.com/mini-profiler-resources/ https://liveactiongolf.com/assets/ https://liveactiongolf.com/brotli_asset/ https://liveactiongolf.com/extra-locales/ https://liveactiongolf.com/highlight-js/ https://liveactiongolf.com/javascripts/ https://liveactiongolf.com/plugins/ https://liveactiongolf.com/theme-javascripts/ https://liveactiongolf.com/svg-sprite/ https://www.google-analytics.com/analytics.js https://www.googletagmanager.com/gtag/js; worker-src 'self' https://liveactiongolf.com/assets/ https://liveactiongolf.com/brotli_asset/ https://liveactiongolf.com/javascripts/ https://liveactiongolf.com/plugins/; frame-ancestors 'self'; manifest-src 'self'
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
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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