Open
Cached
·
just now
90/100
SECURITY SCORE
Detected Technologies
Google Trust
YouTube
Google AdSense
Google Maps
Microsoft 365
Google Tag Manager
Bing
Google reCAPTCHA
Google Cloud Run
AppsFlyer
Tapad
Cookiebot
Plaid
Google DoubleClick
Google Analytics
Mixpanel
Greenhouse
Typeform
Google Static File Front End
TikTok Analytics
Google Fonts
Contentful
Stripe
Google Search
Facebook
Snapchat
Adobe Fonts (Typekit)
TikTok
Persona
Microsoft Clarity
Sentry
Google Cloud
Certificate Information
Subject
CN=dev.step.com
Issuer
C=US, O=Google Trust Services, CN=WR3
Valid From
February 16, 2026
Valid Until
May 17, 2026
35 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
91:8C:7B:4C:C7:65:A5:A0:90:9F:1F:89:53:BF:C9:04:34:C5:73:37:52:AC:02:C3:61:BE:6D:0E:7D:A3:55:9A
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=31536000; includeSubDomains; preload
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
origin-when-cross-origin
Permissions-Policy
Present
payment=(self "https://js.stripe.com" "https://hooks.stripe.com"), camera=(), microphone=(); +2 more
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
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