Skip to main content

Security report for pier69.at

LuSt Hospitality GmbH · Hospitality · Austria

High risk. 7 critical or high findings in GDPR outside view, Network security and 2 other checks.

Security score

49/100

Risk levelHigh

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

PIER 69 Bregenz, operated by LuSt Hospitality GmbH, is a hospitality business located at the harbor of Bregenz, Austria, offering culinary experiences including breakfast, business lunch, fine dining, bar, lounge, and boat tours. The website positions itself as a stylish and relaxed meeting point for guests who appreciate good food and atmosphere. The business targets local and visiting customers seeking quality dining and event experiences by the Bodensee lake. Technically, the website is built on WordPress with Elementor, leveraging modern web technologies and includes a cookie consent mechanism compliant with GDPR. Security posture is strong with HTTPS, security headers, and no visible vulnerabilities. However, no explicit security or incident response policies are published. Overall, the site is professional, trustworthy, and well-optimized for user experience and SEO.

Scanned

NIS2 and GDPR posture

GDPR outside view
55/ 100 · Medium
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

7 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

    • 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

  2. 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: 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
  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 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';…

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

Keep watching pier69.at

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
72
Security headers
30
Email security
85
DNS health
75
Network security
0
GDPR outside view
55
Average
53
After the cap
49

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

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 pier69.at, from OffSeq Breach.

No leaked records found

Breach holds no records for pier69.at 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

The company operates in the hospitality sector with a focus on restaurant and event services. Its market position is that of a local premium dining and event venue. The business model revolves around direct customer service in food and beverage, supplemented by event hosting and boat tours. Revenue streams likely include restaurant sales, event bookings, and possibly ticketing for boat tours. The presence of partner domains for reservations and virtual tours indicates a digital ecosystem supporting customer engagement. The company maintains active social media channels to enhance brand presence and customer interaction.

Security posture

The website demonstrates a mature security posture with enforced HTTPS, presence of key security headers, and a GDPR-compliant cookie consent mechanism. No exposed sensitive data or vulnerable libraries were detected in the HTML content. However, the absence of a publicly available security policy or incident response contact limits transparency in security governance. There is no evidence of a vulnerability disclosure program or security certifications. Overall, the security measures are adequate for the business type but could be enhanced by publishing formal security policies and incident response procedures.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and commitments.
  2. Provide clear incident response contact channels such as security@ or abuse@ email addresses.
  3. Implement and publicize a vulnerability disclosure policy to encourage responsible reporting.
  4. Enhance website accessibility features to meet higher compliance standards.
  5. Regularly review and update third-party scripts and plugins to mitigate potential vulnerabilities.

Contact details published on the site

Addresses
Legal name
LuSt Hospitality GmbH
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
LuSt Hospitality GmbH
Description
Stilvoll essen und entspannt genießen. Direkt am Bodensee: Frühstück, Business-Lunch, Casual Fine Dining, Bar & Lounge, Schifffahrt.
Key services
Restaurantbetrieb, Frühstück, Business-Lunch, Casual Fine Dining, Bar & Lounge, Schifffahrt, Events
Content quality
excellent
Branding
consistent

Technology

Stack
WordPress, Elementor, jQuery, Swiper.js, Borlabs Cookie
Frameworks
Elementor
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism implemented
  • No exposed sensitive data in HTML
  • Use of security headers

Analytics and tracking

Services
Google Analytics 4
Tracking level
moderate
Privacy practices
good

Advertising

Transparency
good

Site quality

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

Key observations

  1. Website is professionally designed with clear branding and consistent messaging.
  2. Comprehensive privacy and cookie policies with active consent mechanisms.
  3. Clear contact information including email, phone, and physical address.
  4. Use of modern web technologies and CMS (WordPress with Elementor).
  5. No signs of malicious content or security issues detected.
  6. Social media integration with Facebook and Instagram.
  7. No explicit or adult content present; suitable for general audiences.
  8. No published security or incident response policies found.
  9. Good SEO and accessibility practices, though accessibility could be improved.
Technical notes

Notes

The website uses WordPress CMS with Elementor page builder, jQuery, and Swiper.js for UI components. It integrates Borlabs Cookie for GDPR-compliant cookie management and Google Analytics 4 for visitor tracking. The site loads external resources from trusted CDNs and partner domains. Performance is moderate with room for optimization. Mobile responsiveness is good, and SEO meta tags including Open Graph and JSON-LD structured data are well implemented. Accessibility is basic but could be improved. No hosting provider details were identified from the content. Overall, the technical infrastructure supports a professional and user-friendly online presence.
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 pier69.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 pier69.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.