Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
AWS Certificate Manager
Microsoft Advertising
Cloudflare
Active incidents
Cloudflare CDN
Cloudflare CDNJS
CookieYes
Facebook
G2
Google API JS Client
Google DoubleClick
Google Tag Manager
HubSpot
HubSpot Analytics
HubSpot Forms
Intercom
Jetboost
jQuery
jsDelivr
Leadfeeder
LinkedIn
Microsoft Clarity
Spider AF
Taboola
Twitter
Visual Website Optimizer
Webflow
Yahoo
Certificate Information
Subject
CN=*.spideraf.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M02
Valid From
September 04, 2025
Valid Until
October 02, 2026
140 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
61:80:59:44:9C:80:2A:3F:5F:05:10:1A:5E:4C:EE:3D:0D:22:86:83:5D:51:C3:32:2F:36:6C:03:EF:F7:1D:0F
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=63072000; includeSubDomains; preload
X-Frame-Options
Present
SAMEORIGIN, SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
gyroscope=(), microphone=(), fullscreen=(self)
Recommendations
- • Significantly strengthen CSP directives
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