Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Let's Encrypt
Algolia
AWS
Amazon S3
Azure Blob Storage
BugHerd
Bugsnag
Calendly
Facebook
Google Analytics
Google API JS Client
Google DoubleClick
Google Fonts
Google reCAPTCHA
Google Search
Google Sign-In
hCaptcha
Hotjar
HubSpot Forms
jsDelivr
Mixpanel
New Relic
PostHog
Pusher
Sentry
Stripe
Yellow.ai
YouTube
Zendesk
Certificate Information
Subject
CN=yellow.ai
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
March 01, 2026
Valid Until
May 30, 2026
56 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
5B:E7:18:4D:83:1F:9C:DF:48:49:F6:55:66:65:CC:11:94:37:7B:CE:75:56:ED:EC:C7:3D:F4:EF:CF:AD:97:C0
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
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Missing
Not configured
Recommendations
- • 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