Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
CN=tinybot.cc
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
October 12, 2025
Valid Until
November 09, 2026
289 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
C3:BD:31:44:70:93:F2:B5:66:7E:71:C5:C6:AE:95:2D:D1:23:D8:D2:13:14:86:CB:E3:B5:4B:3E:2D:74:CF:D2
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
Present
max-age=2592000
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Add Content-Security-Policy header to prevent XSS attacks
- • 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
Subject Alternative Names
10 domains
tinybot.cc
*.tinybot.cc
niceshoppy.cc
*.niceshoppy.cc
senbuy.tw
*.senbuy.tw
tinybook.cc
*.tinybook.cc
tinybot.tw
*.tinybot.tw
Other domains in certificate