Skip to main content

Security report for briese.de

BRIESE SCHIFFAHRT · Transportation · Germany

Medium risk. 7 critical or high findings in GDPR outside view, Security headers and 1 other check.

Security score

59/100

Risk levelMedium

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

BRIESE SCHIFFAHRT is a medium-sized German maritime shipping company managing a fleet of over 130 multipurpose heavylift vessels. The company operates several divisions including chartering, research vessel management, and crew management, serving clients in the shipping and logistics sectors. The website presents a professional and consistent brand image with clear navigation and relevant content targeting maritime industry professionals and potential crew members. Technically, the site uses NeoCMS with jQuery and related libraries, delivering moderate performance and basic mobile optimization. Security posture is moderate with HTTPS implied but lacking explicit security headers and advanced protections on login forms. Privacy compliance is limited, with no cookie consent mechanism detected and only a basic privacy policy present. WHOIS data is consistent and supports the legitimacy of the domain and business. Overall, the website is functional and professional but could improve in security and privacy compliance to enhance trust and regulatory adherence.

Scanned

NIS2 and GDPR posture

GDPR outside view
28/ 100 · High
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. 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 briese.de

This scan found 26 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
67
Security headers
20
Email security
70
DNS health
70
Network security
100
GDPR outside view
28
Average
59

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 holds a strong market position in the maritime transportation sector with diversified services including fleet management, chartering, research, and crew employment. Its business model focuses on providing comprehensive shipping and logistical solutions with a dedicated workforce and specialized departments. The presence of multiple linked subsidiary domains indicates a structured corporate ecosystem. The target audience includes shipping clients, logistics planners, maritime researchers, and seafarers. The company’s website content and structure reflect a stable and established business with moderate digital maturity and limited marketing or tracking tools, suggesting a focus on direct client engagement rather than broad digital marketing.

Security posture

The website demonstrates a basic security posture with HTTPS usage but lacks critical security headers such as Content-Security-Policy and Strict-Transport-Security. The login form is present but does not show visible protections like CSRF tokens. No incident response or security policy pages are available, and no vulnerability disclosure mechanisms are found. Privacy compliance is weak due to the absence of cookie consent mechanisms and limited GDPR indicators. These gaps present moderate risks related to data protection and regulatory compliance. However, no exposed sensitive data or obvious vulnerabilities are detected in the HTML content. Enhancing security headers, privacy compliance, and incident response readiness would significantly improve the security posture.

Recommendations

  1. Implement comprehensive security headers including CSP, HSTS, X-Frame-Options, and X-Content-Type-Options.
  2. Add a cookie consent banner and detailed cookie policy to comply with GDPR requirements.
  3. Enhance login form security with CSRF tokens and input validation to prevent common web attacks.
  4. Publish an incident response plan and security policy page to improve transparency and readiness.
  5. Consider adding a vulnerability disclosure policy or security.txt file to encourage responsible reporting.

Contact details published on the site

Addresses
Legal name
BRIESE SCHIFFAHRT
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
BRIESE SCHIFFAHRT
Description
BRIESE SCHIFFAHRT manages a fleet of more than 130 multipurpose heavylift vessels. 150 dedicated staff members at the head office in Leer take care of the fleet. The company also operates Briese Chartering, Briese Research Department, and Briese Crew Management, offering transport solutions, research vessel management, and crew employment services.
Key services
Fleet management, Chartering transport solutions, Research vessel management, Crew employment and management
Content quality
good
Branding
consistent

Technology

Stack
jQuery, jQuery UI, JavaScript, CSS, HTML5
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
55/100
Good practices seen
  • HTTPS usage implied by base href (https://briese.de//themes/briese/)
  • No exposed sensitive data in HTML

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is focused on maritime shipping and related services.
  3. No privacy or cookie consent banners detected, indicating potential GDPR compliance gaps.
  4. Login form present but no advanced security features visible.
  5. No visible analytics or tracking scripts detected.
  6. Multiple service divisions clearly presented with navigation links.
  7. WHOIS data supports domain legitimacy and consistency.
Technical notes

Notes

The website is built on NeoCMS with a technology stack including jQuery and jQuery UI libraries. The HTML structure is valid and includes meta tags for viewport and favicon. The site uses relative and absolute URLs with a base href set to HTTPS, indicating secure transport. Performance is moderate with multiple CSS and JS files loaded, some from local sources and one external CDN for Font Awesome icons. Mobile optimization is basic with viewport meta tag and responsive CSS but no advanced accessibility features detected. SEO optimization is basic with minimal meta description and keywords. No analytics or tracking scripts are present, indicating limited data collection. The site includes a login form with AJAX-based submission but lacks visible advanced security controls. Overall, the technical implementation is functional but could benefit from modernization and enhanced security and privacy features.
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 briese.de. 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 briese.de.

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.