Open
Cached
·
just now
89/100
SECURITY SCORE
Certificate Information
Subject
CN=webtreinamento.flitapp.com.br
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
November 30, 2025
Valid Until
February 28, 2026
79 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
56:E6:B1:D4:F1:78:1D:DD:DF:32:B9:00:E8:59:C1:75:16:5E:A8:5B:E1:85:76:35:14:73:75:0E:67:61:CC:3A
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
Present
max-age=31556926
Content-Security-Policy
Basic
script-src; object-src; form-action; +3 more
script-src 'self' https://*.firebaseio.com https://*.googleapis.com;object-src 'none';form-action 'self';base-uri 'self';style-src 'self' 'unsafe-inline' https://*.gstatic.com https://*.googleapis.com;frame-ancestors 'self';
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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