Open
Cached
·
just now
91/100
SECURITY SCORE
Certificate Information
Subject
CN=cloudsponge.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
December 03, 2025
Valid Until
March 03, 2026
48 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
0C:63:97:D0:20:1F:62:66:3B:A8:46:FF:CD:56:8E:55:EF:18:F8:D8:C6:A8:17:6E:58:10:A7:6C:3C:68:9D:D3
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
Content-Security-Policy
Basic
default-src; font-src; img-src; +6 more
default-src 'self' https:; font-src 'self' data: https:; img-src 'self' https: data:; object-src 'none'; script-src 'self' https: 'unsafe-inline' 'unsafe-eval'; style-src 'self' https: 'unsafe-inline'; connect-src 'self' https: ws://vts.zohopublic.com ws://ws.inspectlet.com; frame-ancestors 'self'; worker-src 'self' blob: https:
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
camera=(), gyroscope=(), microphone=(), usb=(), payment=(), geolocation=(), fullscreen=(self)
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