Open
Cached
·
just now
85/100
SECURITY SCORE
Certificate Information
Subject
CN=www.mobiry.jp
Issuer
C=JP, O=CloudSecure Corporation, CN=CloudSecure RSA Domain Validation Secure Server CA 2
Valid From
December 13, 2024
Valid Until
January 13, 2026
18 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
B9:EF:35:51:49:D8:E4:66:BF:15:D7:07:A2:96:DD:73:06:C6:30:9D:DA:3E:47:86:70:DC:7D:FC:69:0D:DE:C6
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
Excellent
max-age=31556926; includeSubDomains; preload
Content-Security-Policy
Basic
base-uri; font-src; form-action; +8 more
base-uri 'self';font-src 'self' https:;form-action 'self';frame-ancestors 'none';img-src 'self' https: data:;object-src 'none';script-src 'self' 'unsafe-inline' 'unsafe-eval' https:;script-src-attr 'unsafe-inline';style-src 'self' 'unsafe-inline' https:;worker-src blob:;upgrade-insecure-requests;
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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