Skip to main content

Security report for linauer.at

Ankerbrot Holding GmbH · Retail · Austria

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

Security score

42/100

Risk levelHigh

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

Linauer.at is a transitional website for the Linauer bakery brand, which is being integrated into the Ankerbrot Holding GmbH group, a well-established bakery company in Austria. The site primarily serves as a redirect landing page to the main Ankerbrot website, indicating a brand consolidation. The business operates in the retail bakery sector targeting consumers in Austria. The website content is minimal, focusing on brand transition with a video and countdown redirect. Technical infrastructure includes JavaScript libraries such as jQuery and RequireJS, hosted on ip.co.at nameservers. However, the site lacks HTTPS, which is a critical security deficiency. No security headers or cookie consent mechanisms are implemented, and performance is slow with a large page size and long load time. The WHOIS data confirms domain legitimacy and consistency with the business claims. Overall, the site demonstrates basic digital maturity but requires significant security and privacy improvements.

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

8 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. 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"

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

Keep watching linauer.at

This scan found 20 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
0
Security headers
15
Email security
50
DNS health
85
Network security
100
GDPR outside view
0
Average
42

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

The website reflects a strategic brand transition from Linauer to Ankerbrot, indicating consolidation within the bakery retail sector. Ankerbrot Holding GmbH is the parent company, suggesting a medium-sized enterprise with regional market presence in Austria. The business model focuses on retail bakery products with a target audience of local consumers. The partnership with ip::systems for hosting and technology indicates a professional IT infrastructure provider. The lack of direct contact information on this domain and reliance on the parent site for policies and contacts suggests centralized corporate governance. The use of Facebook SDK indicates engagement with social media marketing. The site’s slow performance and minimal content suggest it is a temporary or placeholder page during brand migration.

Security posture

The security posture of linauer.at is weak due to the absence of HTTPS, invalid SSL certificate, and lack of security headers such as HSTS, Content-Security-Policy, and X-Frame-Options. No cookie consent or privacy compliance mechanisms are present on the site. The site does not expose sensitive data or forms, which reduces immediate risk, but the lack of encryption exposes users to potential interception and undermines trust. DNS configuration is standard but lacks DNSSEC and CAA records, which could enhance domain security. No vulnerability disclosure or incident response contacts are provided. Overall, the site requires urgent implementation of HTTPS and security best practices to meet modern security standards and GDPR compliance.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the site.
  2. Implement security headers including HSTS, Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Add a cookie consent banner and privacy disclosures to comply with GDPR.
  4. Create and publish a vulnerability disclosure policy or security.txt file to improve transparency.
  5. Optimize site performance by reducing page size and improving load times.
  6. Centralize contact information and ensure clear access to privacy and terms policies.
  7. Regularly audit DNS settings to consider enabling DNSSEC and CAA records for enhanced security.
Technical notes

Notes

The website uses JavaScript libraries such as jQuery and Slick Carousel, with RequireJS for module loading. The site is hosted on servers indicated by ip.co.at nameservers. The HTML content is valid but minimal, serving primarily as a redirect landing page with embedded video. Performance is poor with a load time exceeding 10 seconds and a large page size (~210 KB). Mobile optimization is basic with viewport meta tags but no advanced responsive design detected. SEO is minimal with basic meta tags and Open Graph tags for social sharing. Accessibility features are limited. The lack of HTTPS and security headers represents a significant technical risk. The site’s technical debt includes outdated or missing security configurations and slow performance, which could impact user trust and search ranking.
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 linauer.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 linauer.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.