Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
CN=nikkei.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M04
Valid From
October 25, 2025
Valid Until
November 22, 2026
312 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
06:B5:5A:D3:D9:65:F4:97:FA:72:C5:56:C3:2E:D8:85:E3:0E:03:5E:2C:59:FF:7F:30:5E:FB:6B:6E:3A:18:8B
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=63072000
Content-Security-Policy
Weak
frame-ancestors
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
ch-ua-platform-version=(self "https://*.nikkei.com"), ch-ua-model=(self "https://*.nikkei.com"), ch-ua-full-version-list=(self "https://*.nikkei.com"), ch-ua-arch=(self "https://*.nikkei.com"), join-ad-interest-group=("https://td.doubleclick.net")
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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