Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
Gravatar
Let's Encrypt
Adobe Fonts (Typekit)
Akamai
Cloudflare CDNJS
Crazy Egg
Facebook
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Hosted Libraries
Google Tag Manager
HubSpot
HubSpot Analytics
HubSpot Forms
LinkedIn
OneTrust
Pinterest
Salesforce Cloud
Segment
Split.io
Active incidents
SurveyMonkey
Twitter
Wistia
WordPress
WordPress VIP
Certificate Information
Subject
CN=along.org
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
March 17, 2026
Valid Until
June 15, 2026
39 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
2E:B1:9E:8A:C3:CD:BD:8B:83:FE:40:7E:4B:29:C9:FD:B7:0A:8B:86:9F:DA:7E:48:C7:8E:31:53:0F:12:47:24
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=300
X-Frame-Options
Good
SAMEORIGIN
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