Open
Cached
·
just now
90/100
SECURITY SCORE
Certificate Information
Subject
CN=hazelcast.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
October 25, 2025
Valid Until
January 23, 2026
63 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
1A:EB:4F:A8:70:E1:3A:50:AC:3E:DE:C8:88:C7:20:FC:7B:BB:2F:3B:65:1D:FB:7D:63:36:10:61:EC:2E:FB:29
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
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Present
ALLOW-FROM https://www.linkedin.com
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
origin-when-cross-origin
Permissions-Policy
Present
accelerometer=(), autoplay=(self "https://player.vimeo.com"), camera=(), clipboard-write=(self), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=(), fullscreen=(self "https://player.vimeo.com"), clipboard-write=(self)
Recommendations
- • Add Content-Security-Policy header to prevent XSS attacks
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