Open
Cached
·
just now
98/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Let's Encrypt
Active incidents
YouTube
Ashby
AWS
Active incidents
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=links.withorb.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
April 19, 2026
Valid Until
July 18, 2026
68 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F9:1B:4D:4D:6C:8D:1C:97:D0:44:E1:1F:9E:64:0A:64:54:3B:C4:F9:30:62:FA:AC:26:21:43:C2:6C:A2:F7:96
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
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
letsencrypt.org
; validationmethods=http-01;accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/23216805
awstrust.com
digicert.com
Incident Reporting
mailto:[email protected]
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • Consider adding 'issuewild' records to control wildcard certificate issuance