Skip to main content

Security report for viennasightseeing.at

VIENNA SIGHTSEEING TOURS · Transportation · Austria

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

Security score

55/100

Risk levelMedium

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

Viennasightseeing.at is a medium-sized tourism and transportation business specializing in guided sightseeing tours, hop-on-hop-off bus services, day trips, and sightseeing passes in Vienna, Austria. The company positions itself as a market leader in Vienna's sightseeing tour sector, targeting tourists seeking convenient and flexible travel experiences. The website is built on TYPO3 CMS and integrates modern marketing and tracking tools such as Google Tag Manager, Trustpilot, and Usercentrics for consent management. However, the site suffers from critical security issues including an invalid SSL certificate, lack of HTTPS enforcement, and a subdomain takeover vulnerability on its shop subdomain. These issues significantly impact the site's security posture and trustworthiness. Privacy compliance is well addressed with clear privacy and cookie policies and GDPR consent mechanisms. Overall, the site offers good content quality and user experience but requires urgent security improvements to protect user data and maintain business credibility.

Scanned

NIS2 and GDPR posture

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

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

    • 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 viennasightseeing.at

This scan found 24 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
75
Security headers
25
Email security
70
DNS health
55
Network security
85
GDPR outside view
18
Average
55

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 company operates in the transportation and hospitality sectors, offering a variety of sightseeing and shuttle services including hop-on-hop-off bus tours, day trips to regional attractions, and flexible city passes. Its business model relies on online ticket sales and partnerships with local and national tourism organizations. The presence of multiple language options and extensive tour offerings indicates a broad target audience of international tourists. The integration of Trustpilot and newsletter services suggests a focus on customer engagement and retention. The company leverages partnerships with viennapass.de and national tourism sites to enhance its market reach. Despite good market positioning, the lack of visible direct contact information on the homepage may limit immediate customer support accessibility.

Security posture

The website's security posture is weak due to the absence of a valid SSL certificate and HTTPS support, exposing users to potential data interception risks. The lack of security headers and DMARC records further weakens email and web security. The identified subdomain takeover vulnerability on shop.viennasightseeing.at poses a significant risk of malicious content injection or phishing attacks. While no critical vulnerabilities like Heartbleed or POODLE were detected, the overall security configuration is insufficient for a site handling online payments and personal data. Incident response and security policy information are not publicly available, indicating potential gaps in security governance and transparency.

Recommendations

  1. Immediately install and maintain a valid SSL/TLS certificate to enable HTTPS across all domains and subdomains.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and disable all insecure protocols to protect data in transit.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives to enforce HTTPS usage.
  4. Add and configure DMARC, SPF, and DKIM DNS records to improve email authentication and reduce phishing risks.
  5. Mitigate the subdomain takeover vulnerability by properly configuring or removing the cloudfront.net alias for shop.viennasightseeing.at.
  6. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to harden the website against common attacks.
  7. Publish a clear security policy and incident response contact information to improve transparency and trust.
  8. Consider adding visible and verified contact information including phone numbers and emails for customer and security support.
  9. Regularly audit third-party scripts and libraries to ensure no vulnerable components are used.
  10. Enhance accessibility features and continue improving mobile optimization for better user experience.
Technical notes

Notes

The website is powered by TYPO3 CMS, a robust open-source content management system, and uses modern frontend assets with deferred JavaScript loading for performance. It integrates Google Tag Manager for analytics and Usercentrics for GDPR-compliant consent management. Hosting appears to be managed via a1.net DNS servers. Despite a relatively large page size (~270KB) and 50 resources, the load time is slow (~8.5 seconds), indicating potential optimization opportunities. The site supports multiple languages with hreflang tags and uses structured Open Graph metadata for social media sharing. However, the lack of a valid SSL certificate and disabled TLS protocols severely impact security and user trust. The subdomain takeover risk on the shop subdomain is a critical technical vulnerability. Overall, the technical infrastructure is solid but requires urgent security and performance improvements.
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 viennasightseeing.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 viennasightseeing.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.