Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
Google Trust
Algolia
AWS
Chili Piper
ClearBit
Cloudflare CDNJS
Cloudflare Pages
Cloudflare Web Analytics
Contentful
Facebook
Fullstory
Ghost
Google Analytics
Google DoubleClick
Google Search
Google Tag Manager
HubSpot
Active incidents
HubSpot Analytics
Active incidents
HubSpot Forms
Active incidents
HubSpot Live Chat
Active incidents
IP-API
jsDelivr
LinkedIn
Loom
Osano
SalesLoft
Sentry
Twitter
unpkg
Vector
YouTube
Google Cloud Storage
Certificate Information
Subject
CN=www.cypress.io
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 19, 2026
Valid Until
July 18, 2026
77 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
4C:69:35:7C:41:51:AD:1A:B2:0B:49:5A:67:29:16:1B:88:AF:1F:C9:29:AB:45:6A:BD:9A:D1:F4:38:FC:CC: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
Good
max-age=31536000; includeSubDomains
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Strengthen CSP by removing 'unsafe-eval'
- • 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