Skip to main content

Security report for berliner-feuerwehr.de

Berliner Feuerwehr · Government · Germany

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

Berliner Feuerwehr is the official fire department of Berlin, Germany, providing comprehensive fire fighting, rescue, and emergency medical services since 1851. The organization serves the residents and visitors of Berlin with a broad range of services including emergency response, prevention, education, and volunteer fire services. The website reflects a well-established government entity with a strong market position as the primary emergency service provider in the capital city. Technically, the website is built on TYPO3 CMS, leveraging modern web technologies such as jQuery and FontAwesome. It is hosted on Strato servers with HTTPS enforced and demonstrates good mobile optimization and accessibility features, including dedicated accessibility overlays and compliance with digital accessibility standards. The site is well-structured, professionally designed, and provides clear navigation and relevant content. From a security perspective, the site uses HTTPS with a privacy-friendly YouTube embed and cookie consent mechanisms. However, it lacks explicit security headers and a published incident response or vulnerability disclosure policy. No vulnerabilities or exposed sensitive data were detected. The WHOIS data confirms the domain's legitimacy and consistency with the organization's identity. Overall, the website presents a low-risk profile with strong business credibility and privacy compliance. Strategic improvements could include implementing security headers, publishing a security policy, and adding a security.txt file to enhance transparency and incident response readiness.

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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  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"

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

Keep watching berliner-feuerwehr.de

This scan found 22 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
57
Security headers
70
Email security
77
DNS health
70
Network security
0
GDPR outside view
28
Average
50
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 berliner-feuerwehr.de, from OffSeq Breach.

Total records
72
Employees
6
Customers
39
Third parties
27
Weak passwords
15%

Latest record dated 2025-08-22 · 9 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 berliner-feuerwehr.de.

Select it in the checkout above.

Masked preview

  • –mitarbeiterportal.berliner-feuerwehr.de2025-08-22
  • –mitarbeiterportal.berliner-feuerwehr.de2025-08-01
  • –gast.berliner-feuerwehr.de2025-07-24
  • –mitarbeiterportal.berliner-feuerwehr.de2025-07-19
  • –webaccess.berliner-feuerwehr.de2025-06-29

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

Berliner Feuerwehr operates as a government entity providing essential public safety services in Berlin. Its competitive advantage lies in its long history, comprehensive service offerings, and integration with city infrastructure. The business model is publicly funded, focusing on emergency response, prevention, and community engagement. The website targets residents, potential recruits, and the general public, supporting recruitment and public education. Growth indicators include strategic projects like 'Strategie 2030' and community campaigns. The organization maintains partnerships with Berlin city services and has a strong social media presence to engage the community.

Security posture

The website demonstrates a mature security posture with HTTPS enforcement and privacy-conscious embedded content. The presence of cookie consent and accessibility features indicates compliance with GDPR and accessibility laws. However, the absence of security headers and a formal incident response policy suggests room for improvement. No vulnerabilities or sensitive data exposures were found. The WHOIS data is transparent and consistent, supporting trustworthiness. Overall, the security posture is good but could be enhanced by adopting additional best practices and formal policies.

Recommendations

  1. Implement HTTP security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to strengthen defense against common web attacks.
  2. Publish a dedicated security policy and incident response plan on the website to improve transparency and preparedness.
  3. Add a security.txt file to facilitate responsible vulnerability disclosure and communication with security researchers.
  4. Regularly review and update third-party scripts and dependencies to mitigate potential vulnerabilities.
  5. Enhance monitoring and logging capabilities to detect and respond to security incidents promptly.

Contact details published on the site

Addresses
Legal name
Berliner Feuerwehr
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Berliner Feuerwehr
Description
Berliner Feuerwehr is the fire department of Berlin, providing fire fighting, rescue, and emergency services since 1851.
Key services
Firefighting, Emergency medical services, Technical rescue, Public safety information, Training and education, Volunteer fire services
Content quality
excellent
Branding
consistent

Technology

Stack
TYPO3 CMS, jQuery, FontAwesome
Frameworks
TYPO3 CMS
Performance
moderate
Mobile
good
Accessibility
excellent
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced (base href uses https)
  • No exposed sensitive data in HTML
  • Use of privacy-friendly YouTube embed (youtube-nocookie.com)
  • Cookie consent mechanism implemented

Analytics and tracking

Tracking level
minimal
Privacy practices
good

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is comprehensive, well-structured, and professionally presented.
  3. Strong focus on accessibility and user experience.
  4. No signs of advertising or tracking beyond essential functionality.
  5. Social media presence is official and consistent with the organization.
  6. No security.txt or explicit incident response policy found.
  7. WHOIS data confirms domain legitimacy and consistency.
Technical notes

Notes

The website is powered by TYPO3 CMS, a robust and widely used content management system, ensuring scalability and maintainability. The use of jQuery and FontAwesome supports interactive and visually appealing UI elements. Hosting on Strato servers provides reliable infrastructure. The site is mobile-optimized and accessible, with a clear navigation structure and SEO-friendly metadata. Performance is moderate, with potential for optimization in asset delivery and caching. The technical stack is modern but could benefit from enhanced security configurations and performance tuning.
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 berliner-feuerwehr.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 berliner-feuerwehr.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.