Skip to main content

Security report for russmedia.com

Russmedia GmbH · Media · Austria

High risk. 7 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

44/100

Risk levelHigh

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

Russmedia GmbH is a well-established Austrian media company with a strong regional presence and diversified digital offerings including newspapers, online portals, and marketplaces. The company operates multiple subsidiaries and partner sites, serving a broad audience in Austria and Germany. The website is professionally designed, content-rich, and provides clear contact and policy information, reflecting a mature digital presence. Technically, the site is built on WordPress with modern libraries and frameworks, ensuring good user experience and SEO. However, the lack of a valid SSL certificate and HTTPS implementation is a critical security gap that undermines user trust and data protection. Privacy compliance is well addressed with comprehensive policies and consent management. Overall, Russmedia demonstrates solid business credibility but must urgently address its security posture to align with best practices and regulatory requirements.

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

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

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  2. 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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  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 russmedia.com

This scan found 20 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
0
Security headers
15
Email security
50
DNS health
80
Network security
100
GDPR outside view
18
Average
44

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

Russmedia holds a leading position in the regional media sector, leveraging a multi-niche approach with over 40 products and 19 locations. Its business model combines traditional media with digital marketplaces and service technologies, targeting consumers, advertisers, and job seekers. The company benefits from a strong brand, consistent messaging, and a broad partnership ecosystem including equity partners and event organizers. Growth indicators include active recruitment, digital product innovation, and international expansion. The website supports these efforts with clear navigation, product showcases, and career opportunities, enhancing market reach and engagement.

Security posture

The current security posture is weak due to the absence of HTTPS and valid SSL certificates, exposing users to potential data interception and undermining trust. While no immediate vulnerabilities or malware were detected, the lack of modern TLS protocols, HSTS, and security headers indicates insufficient hardening. The presence of cookie consent management and privacy policies shows awareness of compliance, but incident response and vulnerability disclosure mechanisms are missing. This gap poses risks for data protection and regulatory compliance, especially under GDPR and emerging NIS2 requirements. Immediate remediation is necessary to secure communications and protect user data.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Configure modern TLS protocols (TLS 1.2 and TLS 1.3) and disable insecure protocols.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload options.
  4. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  5. Establish a formal vulnerability disclosure policy and incident response contact channels.
  6. Regularly audit and update third-party libraries and plugins to mitigate vulnerabilities.
  7. Enhance accessibility features and mobile optimization for broader user inclusivity.
  8. Maintain transparency in advertising practices and improve advertising disclosure.
  9. Document and publish data retention policies aligned with GDPR requirements.
  10. Consider obtaining recognized security certifications to boost trust and compliance.
Technical notes

Notes

The website is powered by WordPress 6.7.2, utilizing common web technologies such as jQuery, Bootstrap, FontAwesome, and Masonry layout for responsive design and interactive elements. The hosting environment uses nginx 1.22.1 with caching enabled (FastCGI cache HIT). External resources include Google Fonts, FontAwesome CDN, and Google Analytics for tracking. The site employs Cookiebot for cookie consent management, indicating compliance with privacy regulations. Performance metrics were not available, but the site uses lazy loading for images and responsive carousels, suggesting moderate optimization. However, the lack of HTTPS and modern TLS protocols is a significant technical deficiency. The site would benefit from performance monitoring and further optimization to improve load times and accessibility.
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 russmedia.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 russmedia.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.