Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
Gravatar
AWS CloudFront
Auth0
Google Tag Manager
Bugsnag
Google reCAPTCHA
Amplitude
Fullstory
WordPress
Google Analytics
Pusher
Segment
Datadog
Google Static File Front End
LaunchDarkly
Calendly
Wistia
Zendesk
Stripe
Slack
Lottie Player
Google Search
Heap
AWS
jQuery
AWS Certificate Manager
Split.io
Active incidents
Vimeo
PostHog
Intercom
YouTube
Sentry
Google Cloud
Certificate Information
Subject
CN=app.nightfall.ai
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
April 09, 2026
Valid Until
October 23, 2026
169 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
25:07:48:A5:AD:4D:47:1E:0A:3D:D1:20:A1:EC:E2:D9:A3:16:26:A2:13:89:DE:1A:7E:A5:2E:38:BE:74:C7:EB
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
Present
max-age=5184000; includeSubdomains; preload
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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