Open
Cached
·
just now
91/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Gravatar
ADP
AppNexus (Xandr)
AWS
Active incidents
AWS Certificate Manager
Amazon S3
Cloudflare
Active incidents
Cloudflare CDN
Cloudflare CDNJS
Formstack
Google AdSense
Google Analytics
Google API JS Client
Google Conversion Tracking
Google DoubleClick
Google Static File Front End
Google Tag Manager
HubSpot
HubSpot Analytics
HubSpot CMS
HubSpot Feedback & Surveys
HubSpot Forms
HubSpot Live Chat
HubSpot Video
jsDelivr
Microsoft 365
Vimeo
YouTube
Google Cloud
Google Cloud Storage
Certificate Information
Subject
CN=www.etr.org
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
November 15, 2025
Valid Until
December 14, 2026
207 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
8A:5B:B2:9F:78:37:97:BD:E1:D0:99:AD:D6:3F:52:E9:CB:C0:CD:36:26:76:B9:4B:DB:45:7F:A7:AC:B0:B0:85
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=31536000; includeSubdomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
geolocation=(), camera=self, microphone=self
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
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