Skip to main content

Security report for easyweek.io

Awescode GmbH · Technology · Germany

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

Security score

73/100

Risk levelMedium

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

EasyWeek is a technology company operating an online booking software and CRM platform designed to support businesses in managing appointments, time, and object reservations with advanced automation and marketing capabilities. The company targets a broad range of industries including hospitality, wellness, healthcare, and retail, positioning itself as a comprehensive business management solution. Founded in 2019 and operated by Awescode GmbH in Germany, EasyWeek offers a SaaS model with multiple localized domains for regional markets, reflecting a mature and scalable business infrastructure. Technically, the website leverages modern JavaScript frameworks such as Nuxt.js, integrates Google Analytics, Google Tag Manager, and Facebook Pixel for marketing and analytics, and is hosted behind Cloudflare DNS services. The site demonstrates good performance, mobile optimization, and SEO practices, supported by structured data in JSON-LD format that enhances search engine visibility and user trust. From a security perspective, the site uses HTTPS with a clientTransferProhibited domain status, indicating protection against unauthorized domain transfers. However, DNSSEC is not enabled, and no explicit security headers or published security policies were detected. There is no visible privacy or cookie policy, which represents a compliance gap. No vulnerability disclosure or incident response information is published, which could be improved to enhance trust and security posture. Overall, EasyWeek presents a professional and trustworthy online presence with solid technical foundations and business credibility. Strategic recommendations include implementing DNSSEC, publishing comprehensive privacy and cookie policies, adding security headers, and establishing a vulnerability disclosure program to strengthen compliance and security maturity.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 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

6 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 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

    • 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

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics, Facebook

      What to do: Document all third-party data sharing in your privacy policy

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

Keep watching easyweek.io

This scan found 17 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
72
Security headers
45
Email security
100
DNS health
85
Network security
100
GDPR outside view
35
Average
73

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 easyweek.io, from OffSeq Breach.

Total records
149
Employees
0
Customers
149
Third parties
0
Weak passwords
9%

1 subdomain affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for easyweek.io.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

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

Business context

Business profile

EasyWeek operates in the competitive online booking and CRM software market, targeting businesses that require efficient appointment and resource management. Its SaaS business model with tiered pricing caters to various business sizes and needs. The presence of multiple localized domains indicates a strategic approach to international market penetration. The company benefits from strong customer ratings and reviews, which serve as trust signals. The integration of marketing and analytics tools supports data-driven growth and customer engagement. The lack of explicit privacy and security policies suggests an area for improvement to meet evolving regulatory requirements and customer expectations. Partnerships or subsidiaries are not explicitly identified, but the regional domains imply a broad operational footprint.

Security posture

The website demonstrates a moderate security posture with HTTPS enabled and domain transfer protection. However, the absence of DNSSEC, security headers, and published security or incident response policies limits its security maturity. No exposed vulnerabilities or sensitive data were detected in the content. The use of third-party analytics and tracking scripts introduces moderate user tracking, which should be balanced with privacy compliance. The lack of a vulnerability disclosure program and security.txt file reduces transparency and responsiveness to security issues. Overall, the security posture is adequate but could be significantly improved with standard best practices and compliance documentation.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Publish comprehensive privacy and cookie policies with clear GDPR compliance statements.
  3. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Establish and publicize a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Enhance transparency by publishing incident response procedures and security contact information.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Awescode GmbH
Description
Software and app for appointment booking, time or object reservation with advanced automation and marketing capabilities.
Key services
Appointment booking, Time and object reservation, Business management CRM, Automation, Marketing capabilities
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, Google Tag Manager, Google Analytics, Facebook Pixel, Cloudflare DNS
Frameworks
Nuxt.js
Platforms
Android
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Domain status clientTransferProhibited
  • No DNSSEC (not enabled)

Analytics and tracking

Services
Google Analytics, Google Tag Manager, Facebook Pixel
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Facebook Pixel
Marketing tools
Facebook Pixel
Transparency
basic

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 blocking or WAF challenge.
  2. No explicit privacy, cookie, or terms of service pages found in the provided content.
  3. Contact phone number is provided with clear labeling in JSON-LD and footer.
  4. Strong use of structured data (JSON-LD) for software application and organization.
  5. Multiple localized domains exist for regional markets.
  6. Use of modern JavaScript frameworks and CDN hosting.
  7. No visible forms in the provided HTML content for direct user data collection.
  8. No explicit security or incident response policies published on the site.
  9. No security.txt or vulnerability disclosure found.
  10. Good mobile optimization and SEO metadata present.
Technical notes

Notes

The website is built using modern web technologies including Nuxt.js, a Vue.js framework, and is hosted with Cloudflare DNS services, indicating a robust and scalable infrastructure. It integrates widely used analytics and marketing tools such as Google Analytics, Google Tag Manager, and Facebook Pixel. The site is well-optimized for mobile devices and SEO, with appropriate meta tags and structured data enhancing search visibility. Performance is fast, and the design is professional and user-friendly. However, the absence of CMS identification suggests a custom or proprietary solution. Technical debt appears low, but security-related technical improvements are recommended to align with best practices.
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 easyweek.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 easyweek.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.