Open
Cached
·
just now
81/100
SECURITY SCORE
Certificate Information
Subject
C=JP, ST=Tokyo, L=Shinagawa-ku, O=CHIeru Co., Ltd., CN=*.chieru.net
Issuer
C=BE, O=GlobalSign nv-sa, CN=GlobalSign RSA OV SSL CA 2018
Valid From
January 15, 2025
Valid Until
February 16, 2026
94 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
0E:60:D2:6D:61:1B:50:EA:5B:14:6E:C0:0E:C3:08:40:D2:14:4A:14:D0:9D:2B:1C:3A:01:27:3D:21:8C:0C:BF
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
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • Consider adding Permissions-Policy to control browser features
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