Open
Cached
·
just now
87/100
SECURITY SCORE
Certificate Information
Subject
CN=staging.webhostmost.com
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
November 10, 2025
Valid Until
February 08, 2026
19 days
Public Key
ECDSA
384 bit
(P-384)
Strong
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
20:5D:D0:66:75:75:F9:FD:0D:E0:46:2F:36:0C:16:9C:BA:6F:F5:1F:C2:57:1E:6C:51:88:8C:1E:F7:3F:C1:6B
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
Weak
block-all-mixed-content
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
geolocation=*, midi=*, sync-xhr=(self "https://staging.webhostmost.com" "https://www.staging.webhostmost.com"), microphone=*, camera=*, magnetometer=*, gyroscope=*, payment=*, fullscreen=*
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Significantly strengthen CSP directives
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