Skip to main content

Security report for wake.tech

Wake · Technology · Brazil

Medium risk. 8 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

60/100

Risk levelMedium

0–100, higher is better. How it is calculated

Wake is a Brazilian technology company offering an integrated ecosystem of digital solutions focused on retail and industry sectors. Their core offerings include Wake Commerce, a high-performance e-commerce platform; Wake Experience, a digital experience platform with behavioral intelligence; and Wake Creators, a leading influencer marketing platform in Latin America. The company targets medium to large enterprises seeking scalable, omnichannel digital solutions to enhance customer journeys and business growth. Their market position is strengthened by partnerships, client testimonials, and certifications such as AWS Partner and SOC 2 compliance badges. Technically, the website is built on WordPress with modern frameworks and tools but lacks a valid SSL certificate and modern TLS support, which poses significant security risks. Security headers are minimal, and no formal security or incident response policies are published on the site. The company uses Google Tag Manager and Visual Website Optimizer for analytics and marketing, with moderate user tracking and basic privacy compliance. Overall, Wake demonstrates strong business maturity and branding but requires urgent improvements in security posture and compliance transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

8 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

Need hands-on remediation? Email guard@offseq.com

Keep watching wake.tech

This scan found 18 issues across 5 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
100
Security headers
15
Email security
50
DNS health
70
Network security
100
GDPR outside view
25
Average
60

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Wake operates in the technology and e-commerce sectors, providing SaaS platforms that integrate commerce, digital experiences, and influencer marketing. Their business model focuses on B2B services for retail and industrial clients, emphasizing scalability, flexibility, and omnichannel capabilities. The company leverages strategic partnerships with LWSA and digital agencies, and integrates with influencer platforms like Squidit. Revenue streams likely include platform subscriptions, service fees, and marketing campaign management. The presence of extensive case studies and client testimonials indicates a strong market presence and customer satisfaction. Their content strategy includes a well-maintained blog and rich materials targeting technology, marketing, and commerce professionals. The company’s ecosystem approach positions it competitively in Latin America’s digital transformation market.

Security posture

The current security posture of Wake’s website is weak due to the absence of a valid SSL certificate and lack of support for modern TLS protocols, exposing users to potential data interception and man-in-the-middle attacks. While DNS records show proper SPF and DMARC configurations with a quarantine policy, the website does not implement HSTS or OCSP stapling, which are important for HTTPS security. No explicit security policies, incident response plans, or vulnerability disclosure mechanisms are published, indicating limited transparency and preparedness. The use of Cloudflare as a server and CDN provides some protection, but the missing SSL undermines this benefit. The site uses standard security best practices in email authentication but needs to improve transport layer security and publish formal security documentation to meet compliance standards such as GDPR or NIS2.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate supporting TLS 1.2 and TLS 1.3 to secure all web traffic.
  2. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives to enforce HTTPS.
  3. Implement OCSP stapling and session resumption to improve TLS performance and security.
  4. Publish comprehensive security policies, including incident response and vulnerability disclosure procedures.
  5. Introduce a cookie consent mechanism to comply with privacy regulations and enhance user trust.
Technical notes

Notes

The website is built on WordPress CMS with Bootstrap 5 and jQuery frameworks, hosted behind Cloudflare CDN. It uses multiple plugins for SEO (Rank Math), analytics (Google Tag Manager, VWO), performance optimization (WP Rocket), and marketing (AdRotate, Contact Form 7). The site employs modern web fonts with lazy loading and prefetching for performance but currently reports zero load time and resource count, indicating possible measurement issues or caching effects. Mobile optimization is good, with responsive design and accessible navigation. However, the lack of SSL and outdated TLS support represent critical technical debt and security risks. The site integrates with external services including Squidit for influencer management and LWSA for institutional content. Overall, the technical infrastructure is modern but requires urgent security upgrades and performance validation.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with wake.tech. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review wake.tech.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.