Skip to main content

Security report for ham.aero

Hamburg Airport · Transportation · Germany

Medium risk. 3 critical or high findings in SSL/TLS.

Security score

74/100

Risk levelMedium

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

Hamburg Airport operates as a major transportation hub in Germany, providing comprehensive flight information, parking, shopping, and passenger services. The website targets travelers and visitors, offering detailed and localized content primarily in German with English alternatives. Technically, the site employs modern web technologies including Cookiebot for GDPR-compliant consent management, etracker and Meta Pixel for analytics and advertising, and is hosted on Microsoft Azure infrastructure. The security posture is strong with HTTPS enforced and consent-based loading of tracking scripts, though explicit security policies and incident response contacts are not publicly detailed. Overall, the site is professional, trustworthy, and compliant with privacy regulations, though improvements could be made in publishing terms of service and security disclosures.

Scanned

NIS2 and GDPR posture

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

3 findings rated critical or high. Fix these first.

  1. 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.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1
    • High

      SSL Certificate Expires Soon

      SSL certificate expires in 10 days

      What to do: Renew SSL certificate before expiration

      • NIS2 21(2)(h)
      • IR 2024/2690 9.2(c): Implementing Regulation (EU) 2024/2690, Annex point 9.2(c): Cryptography
      • NIST SC-17: NIST SP 800-53 Rev. 5 SC-17: Public Key Infrastructure Certificates
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching ham.aero

This scan found 20 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
32
Security headers
75
Email security
70
DNS health
65
Network security
100
GDPR outside view
100
Average
74

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

Hamburg Airport holds a significant market position as a regional airport serving Hamburg and surrounding regions. Its business model focuses on airport operations, passenger facilitation, and ancillary services such as parking and retail. The website reflects a mature digital presence with integration of multiple third-party services for analytics and marketing, indicating a well-established partnership ecosystem. The absence of explicit contact details and terms of service suggests room for enhanced transparency. The airport likely generates revenue from airline fees, passenger services, parking, and retail concessions. The site’s content and structure support a broad audience of travelers, emphasizing service convenience and up-to-date flight information.

Security posture

The website demonstrates a solid security foundation with HTTPS enforced and use of a reputable consent management platform (Cookiebot) to comply with GDPR. Tracking and analytics scripts are loaded conditionally based on user consent, reflecting good privacy practices. However, the lack of a published security policy, incident response contacts, or vulnerability disclosure mechanisms limits transparency and preparedness visibility. No critical vulnerabilities or exposed sensitive data were detected in the analyzed content. Security headers are minimal but adequate for the site’s scope. Recommendations include publishing a security.txt file, explicit security policies, and contact channels for incident reporting to enhance security posture and trust.

Recommendations

  1. Publish a dedicated terms of service page to clarify user agreements and legal conditions.
  2. Add explicit security and incident response policies, including contact information for security issues.
  3. Implement and publish a security.txt file to facilitate vulnerability disclosures.
  4. Enhance contact information visibility with official emails and phone numbers for customer and security inquiries.
  5. Regularly review and update third-party tracking and advertising scripts to ensure compliance and minimize privacy risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Hamburg Airport
Description
Offizielle Website des Hamburg Airport - Informationen zu Abflug, Ankunft & Flugplan - Parken & Anreise - Shops, Gastro & Services. Entdecken Sie den Hamburger Flughafen!
Key services
Flight information, Parking and transportation, Shopping and gastronomy, Passenger services
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, Cookiebot CMP, etracker analytics, Meta Pixel (Facebook), The Trade Desk, TTDUniversalPixelApi, Duet Date Picker
Frameworks
Cookiebot Consent Framework (TCFv2.2)
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent with blocking mode
  • No exposed sensitive data in HTML
  • Use of consent-based analytics scripts

Analytics and tracking

Services
etracker, Google Analytics (implied by _ga cookies), Posthog (bookingkit), Meta Pixel
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Meta Platforms, Inc., The Trade Desk
Tracking pixels
Meta Pixel, etracker, TTDUniversalPixelApi
Marketing tools
Cookiebot, etracker
Transparency
good

Site quality

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

Key observations

  1. Website uses Cookiebot for GDPR-compliant cookie consent management.
  2. Multiple analytics and advertising trackers are used with user consent.
  3. No explicit contact emails or phone numbers found in the provided HTML snippet.
  4. No terms of service page detected in the analyzed content.
  5. Website content is professional, well-structured, and targeted at travelers and airport visitors.
  6. No security.txt or explicit security policy pages found.
  7. WHOIS data shows professional DNS setup with Azure nameservers.
Technical notes

Notes

The website leverages a modern technology stack including JavaScript frameworks, Cookiebot for consent management, and multiple analytics and advertising platforms such as etracker, Meta Pixel, and The Trade Desk. Hosting is managed via Microsoft Azure DNS infrastructure, indicating reliable and scalable backend support. Performance is moderate with good mobile optimization and accessibility features. SEO is supported by proper meta tags and Open Graph data. The site uses localized content with language toggles and date-picker components for user convenience. Technical risks are low, but the site could benefit from enhanced security headers and formalized security documentation.
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 ham.aero. 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 ham.aero.

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.