DNS Gurus

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 mktru.tw, animalsmeta.tw, bcydm.org, bettermilk.cc, erica-design.com, fantinohome.com, fb2.cc, forest.tw, gaoboss999.com, not for hosetee.com

Open Cached · just now
81/100 SECURITY SCORE

Certificate Information

Subject
CN=mktru.tw
Issuer
C=AT, O=ZeroSSL, CN=ZeroSSL RSA Domain Secure Site CA
Valid From
October 30, 2025
Valid Until
January 28, 2026 53 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
1E:E4:28:25:80:3D:02:3B:5D:3A:74:23:D3:B5:6A:95:3B:2D:8C:9A:D2:B8:08:AA:8B:F0:EF:96:16:1B:EC:13
Alternative Names
40 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
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
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 X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • 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