Skip to main content

Security report for campaigngermany.de

Johann Oberauer GmbH · Media · Germany

High risk. 8 critical or high findings in GDPR outside view, Network security and 1 other check.

Security score

49/100

Risk levelHigh

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

Campaign Germany is a well-established German media service focused on delivering daily industry news and insights for the advertising, marketing, and media sectors. The website offers subscription services, newsletters, job listings, and advertising opportunities, targeting professionals within the German media industry. The company operates under Johann Oberauer GmbH and maintains a consistent brand presence with a good quality content offering. Technically, the site is built on the Newsroom CMS and uses technologies such as nginx, Google Tag Manager, and Google Publisher Tags for advertising. However, the site lacks a valid SSL certificate and modern TLS support, which significantly impacts its security posture. While privacy policies and terms of service are present and GDPR compliant, there is no cookie consent mechanism implemented. The site uses standard security headers but misses advanced protections like HSTS and DNSSEC. Overall, the website demonstrates moderate trustworthiness and professionalism but requires urgent security improvements to protect user data and enhance compliance.

Scanned

NIS2 and GDPR posture

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

8 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

  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 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 campaigngermany.de

This scan found 21 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
100
Security headers
15
Email security
50
DNS health
75
Network security
50
GDPR outside view
18
Average
51
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

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Campaign Germany holds a solid position in the German media landscape, leveraging a subscription and advertising-based business model. Its key competitive advantage lies in its long-standing history and focused content for media professionals. The company targets a niche audience of advertising and marketing professionals, providing timely news and industry insights. The partnership with Oberauer.com and presence on LinkedIn indicate a professional network and ecosystem. Revenue streams likely include subscriptions, advertising, and job listing services. The website's technical infrastructure is moderately mature but shows signs of technical debt, especially in security. Growth potential exists through enhanced digital security, expanded analytics, and improved user engagement via newsletters and subscriptions.

Security posture

The current security posture of Campaign Germany is weak due to the absence of a valid SSL certificate and lack of modern TLS protocols, exposing users to potential data interception risks. The site does implement some cookie security flags and has a GDPR-compliant privacy policy, but lacks a cookie consent mechanism and advanced HTTP security headers like HSTS. DNSSEC and CAA records are not configured, increasing DNS-related risks. No incident response or vulnerability disclosure policies are publicly available, which may hinder timely handling of security incidents. The use of Google Tag Manager and advertising scripts introduces moderate tracking and privacy considerations. Overall, the site requires significant improvements in encryption, security headers, and transparency to meet modern security standards and regulatory requirements.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS and protect user data in transit.
  2. Enable modern TLS protocols (TLS 1.2 or TLS 1.3) and disable all insecure protocols to strengthen encryption.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload to enforce secure connections.
  4. Add DNSSEC and CAA DNS records to improve DNS security and restrict certificate issuance.
  5. Introduce a cookie consent mechanism to comply fully with GDPR and enhance user privacy transparency.
  6. Publish a security policy and incident response plan, including a security.txt file for vulnerability disclosure.
  7. Review and minimize third-party tracking scripts to reduce privacy risks and improve user trust.
  8. Enhance accessibility features and structured data markup (e.g., Open Graph, JSON-LD) for SEO and usability.
Technical notes

Notes

The website runs on nginx web server and uses the Newsroom 2.6.5 CMS, indicating a specialized publishing platform. It integrates Google Tag Manager and Google Publisher Tags for advertising and analytics. The DNS is hosted by Timme Hosting with standard A, MX, and NS records but lacks DNSSEC and CAA. The SSL configuration is currently invalid with no TLS protocols enabled, representing a critical technical risk. Performance metrics are not available, but the site shows signs of moderate speed and good mobile optimization. The frontend uses Bootstrap classes and JavaScript for responsive navigation and user interaction. The site could benefit from modernization of its security infrastructure and enhanced SEO through structured data and metadata improvements.
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 campaigngermany.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 campaigngermany.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.