Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Let's Encrypt
Amazon S3
Bing
Clickagy
Cloudflare CDNJS
Datadog
Google Analytics
Google API JS Client
Google Conversion Tracking
Google DoubleClick
Google Maps
Google Search
Google Static File Front End
Google Tag Manager
Heroku
Hotjar
HubSpot
HubSpot Analytics
HubSpot Forms
HubSpot Live Chat
jsDelivr
LinkedIn
Microsoft Clarity
unpkg
ZoomInfo
Google Cloud
Certificate Information
Subject
CN=beta.upstack.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
March 13, 2026
Valid Until
June 11, 2026
34 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
BF:A2:4C:5E:52:74:2B:EA:D2:85:0C:33:75:70:FD:7C:8D:BF:52:3F:D9:28:D9:F4:98:E3:E4:63:81:6E:0C:F6
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=604800
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
origin-when-cross-origin, strict-origin-when-cross-origin
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'
- • 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