Open
Cached
·
just now
95/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Auth0
Cloudflare Turnstile
Cloudflare Web Analytics
Cloudflare Workers
Facebook
Firebase
Google AdSense
Google Analytics
Google API JS Client
Google Conversion Tracking
Google DoubleClick
Google Search
Google Static File Front End
Google Sign-In
Google Tag Manager
Intercom
Mixpanel
Sentry
Square
Stripe
TikTok
TikTok Analytics
Twitter
unpkg
Vimeo
YouTube
Google Cloud
Google Cloud Storage
Certificate Information
Subject
CN=upsideonly.com
Issuer
C=US, O=Let's Encrypt, CN=YE2
Valid From
July 21, 2026
Valid Until
October 19, 2026
61 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
95:1D:EA:04:1F:03:4B:C0:9F:F2:C0:52:54:A5:37:18:9C:BA:61:E3:E9:16:F3:74:87:2C:CF:F7:26:F8:2E:1B
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
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