Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
CN=goalplan.com
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
November 24, 2025
Valid Until
February 22, 2026
78 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
79:E0:66:8E:CD:3D:67:4F:D5:40:03:77:3C:AA:6E:D7:26:85:FD:F5:EC:3D:B3:CF:41:C2:0E:21:8D:11:4B:FF
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
Present
max-age=31556926
Content-Security-Policy
Basic
default-src; script-src; connect-src; +6 more
default-src 'none'; script-src 'self' *.firebaseio.com *.gstatic.com *.googleapis.com *.google-analytics.com *.googletagmanager.com unpkg.com 'unsafe-eval' 'unsafe-inline'; connect-src 'self' blob: wss://*.firebaseio.com *.sentry.io *.sentry-cdn.com *.googleapis.com unpkg.com *.google-analytics.com *.googletagmanager.com *.goalplan.com *.gstatic.com wss://*.sd-rtn.com:* goalplan-spine-brazil.s3.amazonaws.com goalplan-spine-prod.s3.amazonaws.com goalplan-spine-stage.s3.amazonaws.com; img-src 'self' blob: data: *.googleapis.com *.gstatic.com *.googletagmanager.com *.goalplan.com goalplan-spine-brazil.s3.amazonaws.com goalplan-spine-prod.s3.amazonaws.com goalplan-spine-stage.s3.amazonaws.com; font-src 'self' fonts.gstatic.com; style-src 'self' 'unsafe-inline' *.googleapis.com; manifest-src 'self'; frame-src *.firebaseio.com *.goalplan.com; media-src blob: *.goalplan.com goalplan-spine-brazil.s3.amazonaws.com goalplan-spine-stage.s3.amazonaws.com goalplan-spine-prod.s3.amazonaws.com
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