Open
Cached
·
just now
90/100
SECURITY SCORE
Certificate Information
Subject
CN=tigerconnect.com
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
January 22, 2026
Valid Until
April 22, 2026
82 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
63:63:63:AF:BC:1E:F7:93:01:B5:5D:77:D0:E7:F6:AC:D9:0A:6F:19:CF:C1:FA:A6:98:BD:E5:62:B5:9E:B8:F5
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
Excellent
max-age=31536000; includeSubDomains; preload
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin
Permissions-Policy
Present
midi=(),microphone=(),camera=(),magnetometer=(),gyroscope=(),payment=(),battery=()
Recommendations
- • Add Content-Security-Policy header to prevent XSS attacks
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