Security report for nlm.de
Niedersächsische Landesmedienanstalt · Media · Germany
Medium risk. 4 critical or high findings in Security headers, Email security and 1 other check.
The Niedersächsische Landesmedienanstalt (NLM) is a regional media regulatory authority in Niedersachsen, Germany, responsible for licensing private radio and television broadcasters and supervising broadcast and telemedia content. The organization also promotes media competence, supports citizen broadcasting, and facilitates the digitalization of broadcasting technology. The website reflects a professional and government-oriented presence with clear communication of its mission and services. The target audience includes broadcasters, media professionals, educators, and the general public interested in media regulation and education. Technically, the website is built on the TYPO3 CMS platform, utilizing modern web technologies such as jQuery and Cookiebot for consent management. The site is mobile-optimized and provides a good user experience with clear navigation and relevant content. Hosting appears professional with DNS servers linked to vision-connect.de and xlink.net, indicating stable infrastructure. From a security perspective, the site enforces HTTPS and employs cookie consent mechanisms with granular user controls. While no explicit security headers were detected in the provided data, no vulnerabilities or exposed sensitive data were found. The absence of a published security or incident response policy is noted as an area for improvement. Overall, the security posture is solid for a public-facing regulatory website. The website is fully accessible without any WAF or security challenge blocking content. Privacy compliance is strong, with a comprehensive privacy policy and cookie consent aligned with GDPR requirements. Contact information is clearly presented, including phone numbers and a physical address, enhancing business credibility. Social media presence on LinkedIn and YouTube further supports trust and outreach. Strategic recommendations include implementing security headers, publishing a security.txt file for vulnerability disclosure, and enhancing incident response transparency. These steps would strengthen the site's security maturity and user trust further.
Scanned
NIS2 and GDPR posture
- GDPR outside view
- 83/ 100 · Low
- Checks completed
- 7of 7
NIS2 Art. 21(2)
- (a) Risk analysis and security policies: Not visible from outside
- (b) Incident handling: One indicator
- (c) Business continuity, backups and crisis management: Not visible from outside
- (d) Supply chain security: Not visible from outside
- (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
- (f) Assessing the effectiveness of security measures: Not visible from outside
- (g) Cyber hygiene and security training: Not visible from outside
- (h) Cryptography and encryption: Partly checked
- (i) HR security, access control and asset management: One indicator
- (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.
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"
- CWE-1021
- OWASP A06:2025
- CAPEC-103
- ASVS V3.4.6
- OWASP Secure Headers: OWASP Secure Headers Project recommends X-Frame-Options: deny
- RFC 7034
- 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';…
- High
Email security
SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.
- High
Weak DKIM Key
DKIM selector 'mail' uses 264-bit key
What to do: Use at least 2048-bit RSA keys for DKIM
- High
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
- RFC 8996
- RFC 7568
- Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: tls_versions TLSv1.2, TLSv1.3
- NIS2 21(2)(h)
- IR 2024/2690 9.2(b): Implementing Regulation (EU) 2024/2690, Annex point 9.2(b): Cryptography
- NIST SC-8(1): NIST SP 800-53 Rev. 5 SC-8(1): Cryptographic Protection
- High
Need hands-on remediation? Email guard@offseq.com
Keep watching nlm.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. 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
- SSL/TLS
- 62
- Security headers
- 45
- Email security
- 75
- DNS health
- 70
- Network security
- 40
- GDPR outside view
- 83
- Average
- 63
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
Security posture
Recommendations
- Implement HTTP security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
- Publish a security.txt file to provide a clear vulnerability disclosure channel and improve incident response readiness.
- Develop and publish a dedicated security and incident response policy page to increase transparency and user trust.
- Regularly audit and update third-party scripts and libraries to mitigate potential vulnerabilities.
- Enhance accessibility features to improve compliance with WCAG standards and broaden user inclusivity.
Contact details published on the site
- Addresses
- Legal name
- Niedersächsische Landesmedienanstalt
Site observations
Automated reading of the public site. Ratings are indicative.
Business
- Company
- Niedersächsische Landesmedienanstalt
- Description
- Die NLM lizenziert private Radio- und Fernsehveranstalter und beaufsichtigt die Programme. Sie engagiert sich im Bereich Medienkompetenz, fördert den Bürgerrundfunk und unterstützt die Digitalisierung der Rundfunktechnik
- Key services
- Licensing private radio and TV broadcasters, Supervising broadcast and telemedia content, Promoting media competence, Supporting citizen broadcasting, Supporting digitalization of broadcasting technology
- Content quality
- good
- Branding
- consistent
Technology
- Stack
- TYPO3 CMS, jQuery, Cookiebot Consent Management, HTML5, CSS3
- Frameworks
- TYPO3 CMS
- Performance
- moderate
- Mobile
- good
- Accessibility
- basic
- SEO
- good
Security
- Observed score
- 85/100
- Good practices seen
- HTTPS enforced
- Cookie consent with granular controls
- No exposed sensitive data in HTML
- Use of Cloudflare cookies for bot detection
Analytics and tracking
- Tracking level
- minimal
- Privacy practices
- good
Advertising
- Tracking pixels
- Cookiebot pixel, Cloudflare bot detection cookies
- Marketing tools
- Cookiebot consent management
- Transparency
- good
Site quality
- Design
- good
- User experience
- good
- Content relevance
- good
- Navigation
- good
- Professionalism
- good
- Trustworthiness
- high
Key observations
- Website is fully accessible with no blocking or WAF challenge.
- Content is in German with professional presentation and clear navigation.
- Cookie consent is implemented with detailed categories and user control.
- No explicit security or incident response policies published.
- Contact information is clearly presented including phone and physical address.
- No email addresses explicitly found in HTML content.
- Social media presence includes LinkedIn and YouTube official channels.
- Use of reputable third-party services like Cookiebot and Cloudflare.
- No signs of suspicious or malicious content.
- Website uses modern CMS TYPO3 and standard web technologies.
Technical notes
Notes
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.
- MITRE CWE (opens in a new tab)4.20 (2026-04-30) · CWE Terms of Use (free use with attribution, © MITRE)
- OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
- MITRE CAPEC (opens in a new tab)3.9 (2023-01-24) · CAPEC Terms of Use (free use with attribution, © MITRE)
- OWASP ASVS (opens in a new tab)5.0.0 · CC BY-SA 4.0
- OWASP Web Security Testing Guide (opens in a new tab)latest (checklist.json, master) · CC BY-SA 4.0
- OWASP Secure Headers Project (opens in a new tab)2026-10-18 · Apache-2.0
- Mozilla Server Side TLS (intermediate) (opens in a new tab)6.0 · MPL-2.0
- NIST SP 800-53 Rev. 5 (OSCAL catalog) (opens in a new tab)5.2.0 · Public domain (US Government work)
- Directive (EU) 2022/2555 (NIS2) (opens in a new tab)OJ L 333, 27.12.2022 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Commission Implementing Regulation (EU) 2024/2690 (opens in a new tab)OJ L, 18.10.2024 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Regulation (EU) 2016/679 (GDPR) (opens in a new tab)OJ L 119, 4.5.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive 2002/58/EC (ePrivacy), consolidated (opens in a new tab)19.12.2009 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- RFC Editor metadata (opens in a new tab)per-RFC (obsolete RFCs rejected) · IETF Trust Legal Provisions (metadata only)
- NIST CSRC, W3C TR, IETF Datatracker, EDPB, EUR-Lex CELLAR and gesetze-bayern.de (opens in a new tab)per document · Titles and links only
- NIST NVD CVE API 2.0 (opens in a new tab)live records · Public domain (NVD); CVE® records © MITRE, free use
- W3C WCAG 2.2 (opens in a new tab)W3C Recommendation (wcag.json) · W3C Software and Document License
- ETSI EN 301 549 (opens in a new tab)V3.2.1 (2021-03), clause headings · Clause numbers and titles only (© ETSI)
- Directive (EU) 2019/882 (European Accessibility Act) (opens in a new tab)OJ L 151, 7.6.2019 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive (EU) 2016/2102 (Web Accessibility Directive) (opens in a new tab)OJ L 327, 2.12.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Retrieved 2026-10-25
Feedback on this report
Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.
Reviews of this site
Share your experience with nlm.de. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review nlm.de.