Open
Cached
·
just now
94/100
SECURITY SCORE
Certificate Information
Subject
CN=siomotto.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
November 22, 2025
Valid Until
February 20, 2026
49 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
74:62:A8:67:64:31:3C:DB:C6:E5:B2:06:55:BD:7D:88:C5:CC:FE:DE:B4:2B:50:9E:6D:7D:99:D4:EB:DD:63:3D
Alternative Names
Security Configuration
TLS Protocols
TLS 1.0
TLS 1.1
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
Warnings
- • TLS 1.1 is deprecated and should be disabled
- • TLS 1.0 is deprecated and should be disabled
HTTP Security Headers
Status
Strict-Transport-Security
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
Strong
default-src; script-src; style-src; +8 more
default-src 'self';script-src 'self';style-src 'self';img-src 'self' data: https:;font-src 'self' https: data:;object-src 'none';base-uri 'self';frame-ancestors 'self';upgrade-insecure-requests;form-action 'self';script-src-attr 'none'
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • 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