Open
Cached
·
just now
88/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=mail.spongepowered.org
Issuer
C=US, O=Let's Encrypt, CN=YR1
Valid From
August 09, 2026
Valid Until
November 07, 2026
80 days
Public Key
RSA
3072 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
01:90:55:68:43:2F:B0:94:9A:E3:07:0C:3D:A8:53:31:6B:DB:6B:A6:63:68:D0:B1:A1:52:92:D3:7D:62:9A:F8
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
Good
max-age=31536000; includeSubDomains;
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin
Permissions-Policy
Present
geolocation=(self "https://mail.spongepowered.org/webmail/")
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Significantly strengthen CSP directives
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
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