Open
Cached
·
just now
88/100
SECURITY SCORE
Certificate Information
Subject
CN=bluetokaicoffee.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
November 19, 2025
Valid Until
February 17, 2026
89 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
02:55:AB:79:88:CA:FC:38:80:9F:87:C9:B6:E6:EF:05:EE:30:4B:CF:3D:57:B8:B1:A8:D5:17:49:65:E9:DA:FC
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=7889238
Content-Security-Policy
Weak
block-all-mixed-content; 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
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
amazontrust.com
letsencrypt.org
pki.goog
; cansignhttpexchanges=yes
ssl.com
amazon.com
amazonaws.com
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • You have authorized 6 CAs - consider limiting to only the CAs you actively use
- • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
- • Consider adding 'issuewild' records to control wildcard certificate issuance