Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Let's Encrypt
Google Tag Manager
Integrate
UserSnap
Google DoubleClick
Microsoft Advertising
Google Conversion Tracking
Adobe Audience Manager
6sense
Baidu Analytics
Basis Technologies
Google Fonts
Clickagy
Twitter
Qualtrics
Hotjar
LinkedIn
ZoomInfo
Contentsquare
Drift
TrustRadius
Adobe Marketo
Adobe Dynamic Tag Management
Facebook
Cloudflare CDNJS
Oracle Eloqua
Dun & Bradstreet DirectPlus
Active incidents
MNTN
TrustArc
Intercom
YouTube
Font Awesome
Sentry
Certificate Information
Subject
CN=redhatstatic.com
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
March 16, 2026
Valid Until
June 14, 2026
38 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
30:84:63:A4:2D:54:6E:45:07:54:57:86:A9:9A:84:A1:4E:58:83:3C:9D:E2:98:A8:5B:ED:25:BC:A4:A5:91:02
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=31536000, max-age=31536000
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
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'
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • Consider adding Permissions-Policy to control browser features
CAA Records (Certificate Authority Authorization)
CAA Records
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
Incident Reporting
mailto:[email protected]
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • Consider adding 'issuewild' records to control wildcard certificate issuance