Skip to main content

Security report for scandlines.com

Scandlines · Transportation/trucking/railroad · Denmark

Partial score · DNS & email only

55/100

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

Scanned

4 of 7 checks could not complete. The site may be unreachable or blocking automated scans, so the results below cover only what could be checked. Try a rescan later.

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
Checks completed
3of 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

4 findings rated critical or high. Fix these first.

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

  2. GDPR outside view

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

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics

      What to do: Document all third-party data sharing in your privacy policy

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

Keep watching scandlines.com

This scan found 8 issues across 2 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

Security headers
60
GDPR outside view
50
Average
55

Not counted

  • SSL/TLS: did not complete in this scan.
  • Email security: did not complete in this scan.
  • DNS health: did not complete in this scan.
  • Network security: did not complete in this scan.
  • 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

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 scandlines.com, from OffSeq Breach.

Total records
2,775
Employees
1
Customers
2,762
Third parties
12
Weak passwords
24%

Latest record dated 2025-11-13 · 15 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for scandlines.com.

Select it in the checkout above.

Masked preview

  • –intranet.scandlines.com2025-11-13

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)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

Scandlines holds a strong market position as a leading ferry operator in Northern Europe, particularly between Germany and Denmark. Its business model focuses on transportation services with additional offerings such as combi tickets with partners like ForSea. The company targets leisure and business travelers, providing flexible ticket options and travel inspiration. The presence of freight and agency links suggests diversified revenue streams. The website's integration with multiple marketing and analytics platforms reflects an active approach to customer engagement and data-driven decision-making. Partnerships with related ferry services enhance its ecosystem and customer reach.

Security posture

The website demonstrates a solid security foundation with HTTPS and multiple security best practices, including error reporting and consent management. However, the absence of a published security policy or incident response contact reduces transparency and preparedness perception. No vulnerabilities or exposed sensitive data were detected in the HTML content. The use of third-party scripts is extensive but appears managed with consent mechanisms. To improve, the company should consider publishing a security.txt file and enhancing HTTP security headers to further harden the site against attacks.

Recommendations

  1. Publish a clear security policy and incident response contact information on the website.
  2. Implement and verify comprehensive HTTP security headers such as CSP, X-Frame-Options, and X-XSS-Protection.
  3. Regularly audit third-party scripts and dependencies for vulnerabilities and compliance.
  4. Consider adding a security.txt file to facilitate vulnerability disclosures.
  5. Enhance WHOIS transparency or provide domain registration details to improve trust.

Contact details published on the site

Addresses
Legal name
Scandlines
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Scandlines Aps
Description
Sail with Scandlines via Puttgarden-Rødby or Rostock-Gedser and travel fast and easy between Germany and Denmark. Read more and book your ticket here.
Key services
Ferry transportation, Ticket booking, Travel information, Customer service
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, New Relic monitoring, Adobe DTM, Usercentrics CMP, Exponea marketing, Google Tag Manager
Frameworks
React (likely, based on component tags), New Relic Browser Agent
Platforms
Umbraco CMS
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Error reporting via XMLHttpRequest to internal API
  • Consent management for cookies
  • No exposed sensitive data in HTML

Analytics and tracking

Services
New Relic, Adobe DTM, Google Tag Manager, Exponea
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
New Relic, Adobe DTM, Exponea, Usercentrics
Marketing tools
Exponea, Adobe DTM, Usercentrics CMP
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with rich content and interactive features.
  2. Strong use of modern web technologies and analytics tools.
  3. Comprehensive privacy and cookie policies with consent management.
  4. No visible security policy or incident response contact information.
  5. WHOIS data is missing or unavailable, which is atypical for a commercial domain.
  6. Multiple external trusted domains used for analytics, marketing, and CDN.
  7. No signs of WAF or blocking mechanisms detected.
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 scandlines.com. 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 scandlines.com.

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.