Skip to main content

Security report for oopen.de

o.open · Technology · Germany

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

Security score

60/100

Risk levelMedium

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

o.open is a small German IT service provider specializing in network design, system integration, hosting, and administration of internet and office networks. The company focuses on supporting social and left-wing projects, providing technical expertise and infrastructure services. The website content is professional and targeted at a niche audience within Germany, with references to partner organizations and detailed contact information. The business appears to have been founded in the early 2000s, with a strong community and social orientation. Technically, the website uses standard modern web technologies such as HTML5, CSS3, and vanilla JavaScript with some security-conscious practices like nonce usage in scripts. However, there is no evidence of advanced frameworks or CMS platforms. The site is moderately optimized for performance and mobile use but lacks comprehensive accessibility and SEO features. Security posture is moderate, with no visible security headers or HTTPS confirmation in the provided data, and no cookie or privacy consent mechanisms detected. From a security perspective, the site does not show signs of blocking or WAF interference, and no vulnerabilities or exposed sensitive data were found in the content. The WHOIS data is limited due to DENIC privacy policies but shows consistent nameservers under the domain's control. The domain legitimacy is high, though some WHOIS details like creation and expiry dates are not disclosed. Privacy compliance is basic, with GDPR-related documents available but no cookie consent. Overall, the website is trustworthy and professional but could improve its security posture and privacy compliance. Strategic recommendations include implementing HTTPS verification, adding security headers, introducing cookie consent mechanisms, and enhancing mobile and accessibility features to improve user experience and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 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

5 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. 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 SSL Key Length

      SSL certificate uses 384-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048
  3. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • High

      High-Risk Service Exposed: FTP

      Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer

      What to do: Consider restricting access to FTP or implementing strong authentication

      • 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

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

Keep watching oopen.de

This scan found 19 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. 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
75
Security headers
100
Email security
55
DNS health
70
Network security
20
GDPR outside view
40
Average
60

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

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 oopen.de, from OffSeq Breach.

Total records
4
Employees
0
Customers
4
Third parties
0
Weak passwords
0%

3 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 oopen.de.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

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

Business context

Business profile

o.open operates in a niche market segment providing IT infrastructure and network services to social and left-wing projects in Germany. Its competitive advantage lies in its specialized knowledge and long-standing relationships within this community. The business model is service-oriented, focusing on technical support rather than product sales. Revenue streams likely come from service contracts and hosting fees. The target customers are small organizations and initiatives requiring reliable IT support. Growth indicators are modest, with a focus on quality and trust rather than scale. The partnership ecosystem includes local organizations such as warenform gbr, MBR Berlin, and Aktionsbündnis Brandenburg, indicating a strong community network. The company maintains a low profile with limited digital marketing or analytics, emphasizing privacy and trust.

Security posture

The current security maturity level is moderate. The website employs some security best practices such as nonce usage in inline scripts to support Content-Security-Policy, but lacks explicit security headers and cookie consent mechanisms. There is no visible HTTPS confirmation in the provided data, which is a critical gap. Data protection documents are available, indicating awareness of GDPR requirements, but incident response contacts and vulnerability disclosure policies are absent. The absence of analytics and tracking reduces privacy risks but also limits monitoring capabilities. Overall, the security culture appears cautious but could benefit from formalizing policies and improving technical controls to reduce risk and enhance compliance.

Recommendations

  1. Implement and verify HTTPS with a strong TLS configuration to ensure secure communications.
  2. Add comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Introduce a cookie policy and consent mechanism to comply with GDPR and enhance user trust.
  4. Enhance mobile responsiveness and accessibility to improve user experience and inclusivity.
  5. Establish clear incident response contact channels and publish a vulnerability disclosure policy.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
o.open
Description
o.open is a technology service provider focused on technical support for social and left-wing projects, offering network design, system integration, hosting, and administration of internet and office networks.
Key services
Network Design, System Integration, Hosting, Internet Services Administration, Office Network Administration
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript (vanilla), Fetch API
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
55/100
Good practices seen
  • Use of nonce attribute in inline script for CSP
  • No exposed sensitive data in HTML

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is accessible and not blocked by WAF.
  2. Content is in German and targeted at local German audience.
  3. Contact information is provided but email is dynamically loaded via script with token.
  4. No privacy or cookie banners detected despite GDPR relevance.
  5. No social media links found.
  6. No analytics or tracking scripts detected.
  7. Website uses basic modern web technologies but lacks advanced frameworks or CMS.
  8. Security headers and HTTPS status unknown from provided data; recommend verification.
  9. WHOIS data limited due to DENIC privacy policy but domain appears controlled by owner.
Technical notes

Notes

The website is built with basic modern web technologies including HTML5, CSS3, and vanilla JavaScript. It uses a simple static structure without advanced frameworks or CMS platforms. Performance is moderate with no evident heavy scripts or resources. Mobile optimization is basic but functional. Accessibility features are minimal, and SEO optimization is basic with standard meta tags but no structured data or Open Graph tags. The site dynamically loads email contact via a JavaScript fetch call with a token, indicating some security awareness. Hosting provider and SSL configuration details are not available from the provided data. Technical debt appears low but modernization opportunities exist in adopting security headers, improving accessibility, and implementing privacy compliance 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

Earlier scans of this domain

  1. 63/100Medium25 findingsView report
Reviews of this site

Share your experience with oopen.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 oopen.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.