Open
Cached
·
1h ago
89/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
C=US, ST=WA, L=Redmond, O=Microsoft Corporation, CN=word.cloud.microsoft
Issuer
C=US, O=Microsoft Corporation, CN=Microsoft TLS G2 RSA CA OCSP 04
Valid From
October 01, 2026
Valid Until
January 09, 2027
98 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
4C:D2:33:AC:AD:40:10:47:69:E7:5C:8C:1B:D8:8A:6E:2D:79:37:CB:76:20:68:CC:07:B9:CC:03:ED:28:5A:6A
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
Missing
Not configured
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Present
camera=(), microphone=(), geolocation=(); +1 more
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • 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