Open
Cached
·
just now
88/100
SECURITY SCORE
Certificate Information
Subject
CN=*.eventscloud.com
Issuer
C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., OU=http://certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2
Valid From
June 26, 2025
Valid Until
July 28, 2026
194 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
F7:41:9A:9B:63:D9:0F:DC:19:F9:79:B5:28:4A:4E:B9:03:67:ED:BB:61:14:3B:F8:7A:B9:B2:5F:79:96:74:A8
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=2592000
Content-Security-Policy
Basic
default-src; script-src; style-src; +3 more
default-src 'self';script-src 'self' 'unsafe-inline' 'unsafe-eval' kit.fontawesome.com kendo.cdn.telerik.com ka-p.fontawesome.com ka-f.fontawesome.com ajax.aspnetcdn.com cdn.datatables.net cdnjs.cloudflare.com cdn.jsdelivr.net code.jquery.com;style-src 'self' 'unsafe-inline' kit.fontawesome.com kendo.cdn.telerik.com stackpath.bootstrapcdn.com cdn.datatables.net ka-p.fontawesome.com ka-f.fontawesome.com kit-uploads.fontawesome.com;img-src 'self' blob: data: *.blob.core.windows.net kendo.cdn.telerik.com;font-src 'self' kit.fontawesome.com ka-p.fontawesome.com ka-f.fontawesome.com kendo.cdn.telerik.com;connect-src 'self' ka-p.fontawesome.com ka-f.fontawesome.com kit.fontawesome.com ws: http://localhost:*
X-Frame-Options
Good
SameOrigin
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=()
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
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