Open
Cached
·
just now
95/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Let's Encrypt
YouTube
Ashby
AWS
Chili Piper
Contentsquare
Dark Visitors
Dreamdata
Facebook
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Static File Front End
Google Tag Manager
Heap
HubSpot
HubSpot Analytics
HubSpot Forms
jsDelivr
LinkedIn
Outgrow
Raster
Sanity
Twitter
unpkg
Vercel
Vimeo
Google Cloud
Certificate Information
Subject
CN=withorb.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
May 07, 2026
Valid Until
August 05, 2026
89 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
DE:10:AB:F7:A4:A7:C5:DB:CF:56:5F:73:C6:0F:B4:29:29:35:3E:AB:1D:7A:40:6C:E1:6B:20:AA:38:2A:6B:9E
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
Excellent
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
camera=(), microphone=(), geolocation=(); +1 more
Recommendations
- • Strengthen CSP by removing 'unsafe-eval'
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