Skip to main content

Security report for mobile.de

Zugriff verweigert / Access denied · Other · N/a

Medium risk. 6 critical or high findings in GDPR outside view and Security headers.

Security score

67/100

Risk levelMedium

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

The website mobile.de currently presents an Access Denied error page, providing no accessible content or metadata for analysis. The business overview, market position, and key services cannot be determined from the provided HTML content. The technical infrastructure is hosted on Amazon AWS with multiple IP addresses and DNS records configured properly, including SPF and DMARC records indicating a strong email security posture. However, the SSL configuration lacks detailed protocol and cipher suite information, and HSTS is not enabled, which are areas for security enhancement. The security posture is limited by the absence of security headers and published security policies. Overall, the website's current state limits visibility into its business and security maturity, representing a moderate risk due to lack of transparency and security best practices implementation.

Scanned

This is an earlier scan of mobile.de. View the latest report

NIS2 and GDPR posture

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

6 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 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. 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 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 mobile.de

This scan found 19 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
92
Security headers
35
Email security
70
DNS health
90
Network security
100
GDPR outside view
15
Average
67

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

Due to the Access Denied response, no business intelligence data such as company name, legal information, or market positioning is available. The DNS and email security configurations suggest a professional organization with attention to email security. The hosting on AWS indicates scalable infrastructure. No partnerships or subsidiaries are identifiable from the data. The lack of accessible content and metadata limits insights into revenue streams, customer segments, or growth indicators.

Security posture

The domain demonstrates good email security practices with valid SPF and strict DMARC policies set to reject unauthorized emails. The SSL certificate is valid and issued by a reputable CA but lacks detailed protocol and cipher suite support information. The absence of HSTS and security headers reduces the overall security posture. No incident response or vulnerability disclosure information is published. DNSSEC is disabled, and CAA records are improperly configured with undefined values. No subdomain takeover vulnerabilities detected. Overall, the security maturity is moderate but can be significantly improved by implementing recommended security headers, enabling DNSSEC, and publishing security policies.

Recommendations

  1. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload to enforce HTTPS.
  2. Implement security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web attacks.
  3. Configure SSL/TLS protocols and cipher suites to support only strong and secure options.
  4. Publish a security.txt file and vulnerability disclosure policy to improve transparency and incident handling.
  5. Enable DNSSEC to protect DNS integrity and prevent spoofing attacks.
Technical notes

Notes

The website is hosted on Amazon AWS infrastructure with multiple IPv4 and IPv6 addresses and uses Amazon-issued SSL certificates. DNS records are well configured with multiple authoritative nameservers and a valid SPF and DMARC setup. However, DNSSEC is not enabled, and CAA records are improperly set. The SSL configuration lacks detailed protocol and cipher suite information, and no security headers are present. The website performance is moderate with minimal resources loaded, but the user experience is poor due to the Access Denied page. No CMS or frameworks are detectable from the HTML content. The lack of metadata and structured data indicates technical debt or misconfiguration preventing content delivery.
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. 64/100Medium29 findingsView report
Reviews of this site

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