DNS Gurus
Cached · just now
81/100 SECURITY SCORE

Certificate Information

Subject
C=JP, ST=Tokyo, L=Chiyoda-ku, O=LY Corporation, CN=mscedge01.yahoo.co.jp
Issuer
C=JP, O=Cybertrust Japan Co., Ltd., CN=Cybertrust Japan SureServer CA G4
Valid From
October 02, 2025
Valid Until
November 01, 2026 215 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
A8:16:BA:F7:3E:64:FF:CB:1C:E0:5D:B7:4C:55:B7:7D:95:E3:0C:87:EB:34:9F:8E:42:65:32:29:27:D7:0B:CF
Alternative Names
7 domains

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 Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
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