Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Gravatar
Let's Encrypt
Albacross
Cloudflare
Cloudflare CDN
Facebook
Google AdSense
Google Analytics
Google API JS Client
Google Conversion Tracking
Google DoubleClick
Google Search
Google Static File Front End
Google Tag Manager
Hotjar
jsDelivr
LinkedIn
New Relic
WordPress
Google Cloud
Certificate Information
Subject
CN=gocache.com.br
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
March 05, 2026
Valid Until
June 03, 2026
32 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
35:5B:DA:EF:2B:F0:6F:62:7F:2B:43:CB:42:4D:84:EA:50:8A:AD:41:A1:36:86:4D:F5:98:63:15:DF:10:58:4E
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
X-Frame-Options
Good
sameorigin
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
midi=(), sync-xhr=(self), microphone=(); +4 more
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
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