Skip to main content

Security report for engatta.io

Engatta · Technology · Netherlands

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

Security score

62/100

Risk levelMedium

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

Engatta is a technology company providing a SaaS content operations platform designed to help content teams plan, create, organize, and collaborate on content across multiple channels. The company targets organizations seeking to optimize their content workflows and improve team alignment with real-time performance metrics. The website is built on HubSpot CMS and integrates marketing and analytics tools such as Google Analytics and Facebook Pixel. However, the technical infrastructure shows weaknesses including an invalid SSL certificate and disabled TLS protocols, which pose significant security risks. Additionally, multiple subdomains are vulnerable to takeover due to dangling DNS records. Privacy and cookie policies are present with consent mechanisms, but GDPR compliance indicators are basic. Overall, the website presents a professional business front but requires urgent security improvements to protect user data and maintain trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
43/ 100 · High
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 X-Frame-Options header

      Prevents clickjacking attacks

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

  2. GDPR outside view

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

    • 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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  3. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • High

      Potential Subdomain Takeover

      Subdomain mail.engatta.io points to unregistered service ac30f492d56c711e9a12f02ef47fa165-2073928757.eu-west-1.elb.amazonaws.com

      What to do: Remove or fix CNAME record to prevent subdomain takeover

      • WSTG-CONF-10
      • NIS2 21(2)(i)
      • IR 2024/2690 12.4: Implementing Regulation (EU) 2024/2690, Annex point 12.4: Asset inventory
      • NIST CM-8: NIST SP 800-53 Rev. 5 CM-8: System Component Inventory
    • High

      Potential Subdomain Takeover

      Subdomain ftp.engatta.io points to unregistered service ac30f492d56c711e9a12f02ef47fa165-2073928757.eu-west-1.elb.amazonaws.com

      What to do: Remove or fix CNAME record to prevent subdomain takeover

      • WSTG-CONF-10
      • NIS2 21(2)(i)
      • IR 2024/2690 12.4: Implementing Regulation (EU) 2024/2690, Annex point 12.4: Asset inventory
      • NIST CM-8: NIST SP 800-53 Rev. 5 CM-8: System Component Inventory

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

Keep watching engatta.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. 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
97
Security headers
45
Email security
85
DNS health
0
Network security
100
GDPR outside view
43
Average
62

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention engatta.io, from OffSeq Breach.

No leaked records found

Breach holds no records for engatta.io right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

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

Business context

Business profile

Engatta operates in the technology sector with a focus on content management and collaboration SaaS solutions. The company maintains a clear market niche by offering a centralized platform for content operations, targeting content teams and enterprises. Their business model revolves around subscription-based software services. The presence of detailed blogs and release notes indicates active product development and customer engagement. Contact information and social media presence on Instagram, YouTube, and LinkedIn support brand visibility and customer outreach. The company is based in the Netherlands and appears to be a small-sized enterprise. No parent or subsidiary companies were identified. The website content and branding are consistent and professionally presented, supporting credibility in their market segment.

Security posture

The website's security posture is weak due to the absence of a valid SSL certificate and lack of enabled TLS protocols, which are critical for secure communications. The presence of HSTS is positive but insufficient without proper TLS support. SPF and DMARC records exist but DMARC policy is set to 'none', offering minimal email protection. The detection of multiple subdomains vulnerable to takeover is a serious risk that could lead to unauthorized access or phishing attacks. No explicit security policies, incident response plans, or vulnerability disclosure mechanisms are published, indicating limited transparency and preparedness. The site uses modern marketing and analytics scripts but lacks advanced security features such as OCSP stapling and session resumption. Immediate remediation of SSL/TLS issues and DNS cleanup is recommended to improve security.

Recommendations

  1. Obtain and correctly install a valid SSL certificate to enable HTTPS and modern TLS protocols (TLS 1.2 and 1.3).
  2. Audit and remove or properly configure dangling CNAME DNS records to prevent subdomain takeover vulnerabilities.
  3. Implement stricter DMARC policies to enhance email security and reduce spoofing risks.
  4. Publish a clear security policy and incident response plan to improve transparency and preparedness.
  5. Optimize website performance to reduce page load times and improve user experience.

Contact details published on the site

Addresses
Technical notes

Notes

The website is hosted on Amazon AWS infrastructure as inferred from DNS ELB records and uses HubSpot CMS for content management and marketing automation. The tech stack includes Google Tag Manager, Facebook Pixel, GSAP for animations, and Google Fonts. Despite modern technologies, the site suffers from slow load times (over 10 seconds) and a large page size (~1.3 MB). Accessibility features are basic, with some ARIA roles and skip links present. SEO is well addressed with meta tags, Open Graph, and Twitter cards. The site is mobile optimized with responsive design. However, the invalid SSL certificate and disabled TLS protocols represent critical technical debt and security risks. The DNS configuration exposes multiple subdomains to takeover, indicating a need for DNS hygiene improvements. Overall, the technical infrastructure supports business goals but requires urgent security and performance enhancements.
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 engatta.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 engatta.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.