Skip to main content

Security report for daheim-bremen.de

Hospitality · Germany

Partial score · DNS & email only

47/100

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

The website 'Das Viertel liefert' serves as a local food delivery platform targeting residents in Bremen, Germany. It aggregates various local restaurants offering diverse cuisines such as burgers, pasta, sushi, Italian pizza, and Syrian specialties. The business model focuses on online food ordering and delivery, leveraging third-party ordering platforms. The site content is basic but relevant, with a clear focus on local hospitality services. Technically, the website is minimalistic, using nginx as the server and Google Fonts for typography. There is no evidence of a CMS or advanced frameworks. The site lacks HTTPS, which is a critical security flaw, and no modern security headers or mechanisms are implemented. Performance metrics are unavailable, but the site appears to have basic mobile optimization and accessibility. From a security perspective, the absence of SSL/TLS encryption, security headers, and DNS security features exposes users to potential risks. No privacy or cookie policies are present, indicating non-compliance with GDPR. No contact or incident response information is provided, limiting trust and transparency. Overall, the website presents a low security posture and limited privacy compliance, which negatively impacts its trustworthiness and professional appearance. Strategic improvements in security, privacy policies, and contact transparency are recommended to enhance user trust and regulatory compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
0/ 100 · Critical
Checks completed
6of 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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

  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

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

Keep watching daheim-bremen.de

This scan found 12 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
0
Email security
50
DNS health
85
Network security
100
GDPR outside view
0
Average
47

Not counted

  • Security headers: did not complete in this scan.
  • 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

The business operates as a small local food delivery aggregator in Bremen, focusing on promoting local restaurants and facilitating online orders through external platforms. Its competitive advantage lies in its niche focus on the Viertel district and diverse cuisine offerings. Revenue likely derives from partnerships or commissions with listed restaurants. The target customers are local residents seeking convenient food delivery. The absence of direct ordering on the site suggests reliance on third-party services. Growth potential depends on expanding restaurant partnerships and improving digital presence. No parent or subsidiary companies are identified, indicating an independent operation.

Security posture

The current security maturity level is low due to the lack of HTTPS, absence of security headers, and missing DNS security features. These gaps expose the site and its users to interception, spoofing, and other attacks. The lack of privacy and cookie policies indicates non-compliance with GDPR, increasing legal risk. No incident response or vulnerability disclosure mechanisms are present, limiting the ability to handle security events effectively. The site does not collect user data directly, reducing some risk, but the overall security culture appears immature. Immediate remediation of SSL and privacy compliance is critical.

Recommendations

  1. Implement a valid SSL/TLS certificate to enable HTTPS and protect user data.
  2. Develop and publish comprehensive privacy and cookie policies to comply with GDPR.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-XSS-Protection to harden the site against common attacks.
  4. Provide clear contact information including email and phone to improve transparency and trust.
  5. Establish an incident response process and publish vulnerability disclosure guidelines to enhance security readiness.
Technical notes

Notes

The website is hosted on nginx with DNS and mail services provided by Ionos. It uses Google Fonts for typography and links to external image and ordering resources. No CMS or JavaScript frameworks are detected, and no analytics or tracking scripts are present. The site lacks HTTPS and modern security configurations. Performance data is missing, but the site appears to have basic mobile responsiveness. Technical debt is evident in the lack of security and privacy features. Modernization opportunities include adopting HTTPS, improving SEO metadata, and implementing accessibility standards.
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 daheim-bremen.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 daheim-bremen.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.