SSL Verification Bypassed

The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.

Reason:

Hostname Mismatch - certificate is issued for *.blog.st-hatena.com, *.hateblo.jp, *.hatena.blog, *.hatenablog-oem.com, *.hatenablog.com, *.hatenablog.jp, *.hatenadiary.com, *.hatenadiary.jp, *.hatenadiary.org, not for ec2-54-199-90-60.ap-northeast-1.compute.amazonaws.com

Certificate Information

Subject
CN=hateblo.jp
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
December 03, 2025
Valid Until
March 03, 2026 85 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
FD:E0:4F:09:52:81:D2:60:78:7C:D6:29:57:EE:19:F7:FE:EC:55:67:83:94:23:23:E6:33:F8:8A:E6:AB:A8:B0
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
Weak
frame-ancestors; upgrade-insecure-requests
X-Frame-Options
Excellent
DENY
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
  • Significantly strengthen CSP directives
  • 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