Skip to main content

Security report for moalach.at

Moalach · Hospitality · Austria

High risk. 9 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

36/100

Risk levelHigh

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

Moalach is a small consultancy firm specializing in online marketing and data protection services tailored for the tourism sector in Austria, particularly the Tirol region. Founded in 2016 by Dominik Neuner, the company leverages deep industry experience and academic involvement to provide practical and strategic digital marketing solutions to small and medium-sized tourism businesses. The website presents a professional image with clear service offerings and client references, targeting tourism operators and destinations seeking digital transformation and compliance support. Technically, the website employs standard web technologies including Matomo analytics for user tracking, but lacks modern security implementations such as HTTPS and security headers. The site suffers from slow load times and does not implement cookie consent mechanisms, which may impact user trust and regulatory compliance. Hosting is provided by kasserver.com, and the domain registration aligns well with the business profile. From a security perspective, the absence of a valid SSL certificate and HTTPS support is a critical vulnerability, exposing users to potential data interception. The lack of security headers and session management features further weakens the site's security posture. Privacy compliance is partially addressed with a privacy policy present, but cookie consent and detailed data retention disclosures are missing. Overall, while the business model and content quality are solid and relevant to its niche, the technical and security shortcomings present risks that should be addressed promptly to enhance trust, compliance, and user experience.

Scanned

NIS2 and GDPR posture

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

9 findings rated critical or high. Fix these first.

  1. GDPR outside view

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

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: SMB

      Port 445 (SMB) is publicly accessible - SMB - Windows file sharing, high risk

      What to do: Immediately restrict access to SMB using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

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

Keep watching moalach.at

This scan found 19 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
0
Security headers
80
Email security
50
DNS health
85
Network security
0
GDPR outside view
0
Average
36

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 · found on this site
  • 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

Moalach operates in a niche market providing consultancy services focused on digital marketing and data protection for the tourism industry. Its competitive advantage lies in the founder's combined expertise in IT, tourism, and academic teaching, which supports a practical and research-informed approach. The business model centers on service-based revenue from small and medium tourism enterprises in Austria. The company has established partnerships with recognized regional tourism organizations, enhancing its market credibility. Growth potential exists through expanding digital transformation services and compliance consulting. The company maintains a lean operation with no subsidiaries or parent companies, focusing on regional market penetration and reputation building.

Security posture

The current security maturity level of the website is low due to the absence of HTTPS and valid SSL certificates, which is a critical vulnerability exposing users to man-in-the-middle attacks. No security headers are implemented, and TLS protocols are not enabled, indicating outdated or misconfigured server security. There is no evidence of incident response policies or contact channels for security issues. GDPR compliance is partially met with a privacy policy, but cookie consent mechanisms are missing, which may lead to regulatory non-compliance. The use of Matomo analytics suggests some privacy awareness, but overall data protection practices require improvement. The lack of security best practices and vulnerability disclosures indicates a need for enhanced security culture and readiness.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire website.
  2. Implement HTTP security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Add a cookie consent banner/mechanism to comply with GDPR and ePrivacy regulations.
  4. Establish and publish an incident response policy with clear contact channels for security issues.
  5. Optimize website performance to reduce load times and improve user experience.

Contact details published on the site

Addresses
Technical notes

Notes

The website is built using standard HTML5 and CSS3 with custom JavaScript and Matomo analytics for tracking. It is hosted on servers managed by kasserver.com with DNS records pointing to a single IPv4 address. The site lacks modern TLS protocols and does not support HTTPS, which is a significant technical deficiency. Performance is slow with a load time exceeding 15 seconds and a page size of approximately 93 KB. Mobile optimization is good, and SEO meta tags including Open Graph and Twitter cards are properly implemented. No CMS or major frameworks are detected, suggesting a custom or lightweight site build. Technical debt is evident in the lack of security features and slow performance, representing risks to business continuity and user trust.
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 moalach.at. 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 moalach.at.

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.