Open
Cached
·
just now
90/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Let's Encrypt
PayPal
Adyen
Akamai
Active incidents
Algolia
Apple Music
Braintree
Cloudflare Access
GIPHY
Google API JS Client
Google Cloud Storage
Google Fonts
Google reCAPTCHA
Google Search
Google Static File Front End
hCaptcha
Mux
Reddit
Sentry
SoundCloud
Spotify
Square
Stripe
Tenor
TikTok
Twitch
Twitter
Vimeo
YouTube
Google Cloud
Certificate Information
Subject
CN=*.authjs.dev
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
March 09, 2026
Valid Until
June 07, 2026
60 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
C4:DF:73:9E:78:2F:CC:58:62:09:4A:09:42:68:1F:F4:B8:D8:45:99:AA:B9:9C:72:78:98:95:11:E6:67:8A:47
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
Missing
Not configured
Permissions-Policy
Present
interest-cohort=()
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
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