Skip to main content

Security report for wati.io

Wati.io · Technology · N/a

Medium risk. 5 critical or high findings in Security headers and SSL/TLS.

Security score

70/100

Risk levelMedium

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

Wati.io is a technology company specializing in providing an end-to-end WhatsApp Business API platform tailored for small and medium businesses globally. Their platform enables personalized communication and automates marketing, sales, and customer support processes. The company positions itself as a leading SaaS provider in the business messaging space, trusted by fast-growing brands in over 78 countries. Technically, the website is built on WordPress and integrates multiple modern analytics and marketing tools, demonstrating a mature digital infrastructure. Security posture is good with HTTPS enforced and cookie consent mechanisms in place, though explicit security headers and incident response policies are not publicly documented. WHOIS data is privacy protected, which is typical for SaaS businesses, but limits transparency. Overall, the website is professional, well-structured, and compliant with GDPR, supporting a strong business credibility profile.

Scanned

NIS2 and GDPR posture

GDPR outside view
95/ 100 · Low
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

5 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. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching wati.io

This scan found 23 issues across 6 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. See sample alerts.

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
52
Security headers
15
Email security
80
DNS health
80
Network security
100
GDPR outside view
95
Average
70

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

Wati.io targets SMBs, marketing agencies, sales teams, ecommerce, and education sectors with a SaaS model offering WhatsApp API integration and automation tools. Their competitive advantage lies in comprehensive WhatsApp messaging features including chatbots, bulk messaging, and CRM integrations. The company leverages partnerships with platforms like HubSpot, Shopify, and Zapier to enhance ecosystem reach. Marketing efforts are supported by extensive analytics and tracking, and trust is reinforced by positive customer case studies and high G2 ratings. The multilingual website supports global market penetration. Lack of public WHOIS data is mitigated by strong brand presence and content quality.

Security posture

The website enforces HTTPS and implements cookie consent compliant with GDPR, indicating a baseline security and privacy posture. Multiple tracking and analytics scripts are used, which require careful management to avoid privacy risks. No exposed sensitive data or vulnerable libraries were detected in the HTML content. However, security headers such as Content-Security-Policy and X-Frame-Options are not explicitly found, representing an area for improvement. No public incident response or vulnerability disclosure policies were identified, which could enhance transparency and trust. Overall, the security posture is solid but could benefit from enhanced header policies and published security practices.

Recommendations

  1. Implement and verify comprehensive security headers including CSP, X-Frame-Options, and X-Content-Type-Options to mitigate common web attacks.
  2. Publish a dedicated security policy and incident response page to improve transparency and customer trust.
  3. Add a security.txt file to facilitate responsible vulnerability disclosure and improve security communication.
  4. Regularly audit third-party scripts and tracking pixels to ensure privacy compliance and minimize data leakage risks.
  5. Enhance accessibility features and provide more explicit contact information including verified company emails and phone numbers.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Wati.io
Description
Wati is the #1 end-to-end WhatsApp API solution for SMBs across the globe, trusted by fastest growing brands in over 78 countries. It personalizes communication and automates marketing, sales, service, and support.
Key services
WhatsApp Business API platform, Marketing automation, Sales automation, Customer support automation, Chatbots, Broadcast & bulk messaging, Custom notifications, Integrations with CRM and ecommerce platforms
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Google Tag Manager, Facebook Pixel, HubSpot, Dreamdata Analytics, Klenty tracking, Owl Carousel, Swiper.js, CryptoJS
Frameworks
WordPress
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Cookie consent banner implemented
  • No exposed sensitive data found in HTML

Analytics and tracking

Services
Google Analytics (via GTM), HubSpot Analytics, Dreamdata Analytics, Microsoft Clarity, LinkedIn Insight Tag
Tracking level
extensive
Privacy practices
good

Advertising

Ad networks
Google Ads, Facebook Ads
Tracking pixels
Facebook Pixel, HubSpot Analytics, Dreamdata Analytics, LinkedIn Insight Tag, Microsoft Clarity
Marketing tools
HubSpot, Klenty, Zapier, Pabbly Connect, Make (Integromat)
Transparency
good

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is fully accessible with no WAF or blocking detected
  2. Comprehensive cookie consent and privacy policy present
  3. No explicit terms of service or security policy pages found
  4. Multiple language support for global audience
  5. Strong marketing and analytics integration
  6. No exposed sensitive data or obvious vulnerabilities in HTML
  7. WHOIS data unavailable publicly, indicating privacy protection
Technical notes

Notes

The website uses WordPress CMS with modern front-end libraries such as Owl Carousel and Swiper.js for UI components. It integrates multiple marketing and analytics tools including Google Tag Manager, Facebook Pixel, HubSpot, Dreamdata, and Microsoft Clarity, indicating a sophisticated tracking and marketing infrastructure. Performance is moderate with some lazy loading optimizations. Mobile responsiveness is good with adaptive layouts and language-specific content. The site lacks explicit security headers and some accessibility features, which are opportunities for technical improvement. Hosting provider details are not evident from the HTML content. Overall, the technical implementation supports a professional and scalable SaaS platform.
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 wati.io. 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 wati.io.

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.