Open
Cached
·
just now
96/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Let's Encrypt
Bugcrowd
HubSpot Video
Google Tag Manager
Sanity
Heroku
Reddit
HubSpot Forms
HubSpot Feedback & Surveys
Google DoubleClick
Google Analytics
Pusher
Firebase
Google Cloud Storage
Google Fonts
Twitter
Cloudflare Web Analytics
LinkedIn
HubSpot CMS
Cloudflare Turnstile
Stripe
HubSpot Analytics
Slack
Google Search
Amazon S3
bunny.net
Active incidents
GitHub
CookieYes
AWS
Vercel
HubSpot
YouTube
HubSpot Live Chat
Sentry
jsDelivr
Certificate Information
Subject
CN=dev.fireworks.ai
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
April 17, 2026
Valid Until
July 16, 2026
74 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
76:A4:7C:BA:8C:DD:A5:68:2E:1A:E0:A6:7F:4D:C1:A2:DC:DE:46:EB:20:32:77:46:55:60:48:BF:2F:7E:8A:1D
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=63072000; includeSubDomains; preload
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Present
camera=(), microphone=(self), geolocation=(); +3 more
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
CAA Records (Certificate Authority Authorization)
CAA Records
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • You have authorized 4 CAs - consider limiting to only the CAs you actively use
- • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
- • Consider adding 'issuewild' records to control wildcard certificate issuance