Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
HTML Load
AWS CloudFront
Let's Encrypt
Google AdSense
Miro
Google Tag Manager
Amplitude
AppNexus (Xandr)
Fullstory
Google DoubleClick
Cloudflare RocketLoader
Google Analytics
Google Conversion Tracking
ClearBit
Pusher
6sense
Mixpanel
Sprig
Segment
Datadog
Metadata.io
LaunchDarkly
Wistia
Twitter
Hotjar
Loom
LinkedIn
Zendesk
Stripe
unpkg
Google Search
BootstrapCDN
Didomi
Figma
Adobe Marketo
Facebook
OneTrust
Adobe Fonts (Typekit)
CookieYes
Heap
Cloudflare CDNJS
jQuery
Salesforce Pardot
Google Optimize
Akamai
Intercom
YouTube
Sentry
Certificate Information
Subject
CN=roadmap.codefresh.io
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
March 17, 2026
Valid Until
June 15, 2026
41 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
BC:FE:EB:67:11:58:9A:46:94:88:32:D9:F6:A9:A4:E2:04:6D:9B:97:84:87:97:BF:D6:38:8E:DD:A7:D9:2D:7D
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
Present
ALLOWALL
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
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