Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Let's Encrypt
Algolia
Arcade
ClearBit
Firebase
Google Analytics
Google API JS Client
Google Cloud Functions
Google Cloud Storage
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Hosted Libraries
Google Static File Front End
Google Tag Manager
HubSpot
HubSpot Analytics
HubSpot Forms
Intercom
jsDelivr
LinkedIn
Liveblocks
Mux
Pexels
PostHog
Sentry
Stripe
Vercel
Google Cloud
Certificate Information
Subject
CN=staging.arcade.software
Issuer
C=US, O=Let's Encrypt, CN=YR1
Valid From
September 25, 2026
Valid Until
December 24, 2026
78 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
84:9F:53:8F:2E:6C:FB:FA:0F:53:48:BD:72:D3:AE:CD:D6:1E:E3:11:29:C4:F0:47:A1:43:8F:82:4C:CE:A6:50
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=63072000
X-Frame-Options
Excellent
DENY
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
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • You have authorized 4 CAs - consider limiting to only the CAs you actively use
- • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
- • Consider adding 'issuewild' records to control wildcard certificate issuance