Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=grupoubique.com.br
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
July 21, 2026
Valid Until
October 19, 2026
69 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
C8:D8:81:D2:1C:CA:47:BC:23:B2:49:C0:3D:81:39:E5:75:19:1A:61:F8:AC:38:C3:CB:E2:EA:38:28:B2:15:F4
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
Missing
Not configured
X-Frame-Options
Present
ALLOW-FROM https://app.kajabi.com https://app.vibely.io https://communities.kajabi.com https://communities-widget.kajabi.com *.mykajabi.com https://communities.newkajabi-staging.com https://communities-widget.newkajabi-staging.com https://www.ubiquejunior.com.br https://www.ubiquejur.com.br https://www.ubiquedelta.com.br https://www.grupoubique.com.br
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Significantly strengthen CSP directives
- • 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