Skip to main content

Security report for autodoc.de

Other · N/a

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

Security score

53/100

Risk levelMedium

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

The website autodoc.de is currently inaccessible due to a Cloudflare security challenge page requiring human verification via Turnstile captcha. This prevents access to any meaningful business or security content. The domain uses Cloudflare nameservers, indicating privacy protection and security measures at the DNS level. No metadata, contact information, or business details are available for analysis. The technical infrastructure relies heavily on Cloudflare services for security and performance. Due to the content block, no evaluation of privacy policies, cookie consent, or terms of service is possible. The security posture cannot be fully assessed beyond the presence of Cloudflare's WAF and challenge mechanisms. Overall, the site appears to be protected by strong security controls but lacks accessible content for further analysis.

Scanned

NIS2 and GDPR posture

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

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

      Unable to retrieve SSL certificate

      Could not establish secure connection to retrieve certificate information

      What to do: Check if the server is accessible and SSL/TLS is properly configured

  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 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 autodoc.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. 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
0
Security headers
70
Email security
70
DNS health
70
Network security
100
GDPR outside view
10
Average
53

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

No business intelligence data could be extracted due to the content block. The domain appears to be commercial but no company name, description, or sector information is available. The use of Cloudflare suggests a focus on security and performance. No partner or subsidiary domains were identified. The lack of accessible content limits insights into market positioning, business model, or customer targeting.

Security posture

The site is protected by Cloudflare's security platform, including Turnstile captcha for bot mitigation. This indicates a proactive security posture against automated threats. However, no detailed security headers or SSL configuration data were available. No vulnerabilities or incident response contacts were found. The absence of visible privacy or security policies limits compliance assessment. Overall, the security posture is strong at the perimeter but internal security practices cannot be evaluated.

Recommendations

  1. Ensure that legitimate users can access the website content without excessive friction from security challenges.
  2. Publish clear privacy, cookie, and terms of service policies accessible without security barriers.
  3. Provide visible contact information and security incident response contacts for transparency and trust.
  4. Implement and expose security headers and SSL/TLS configuration details for improved security posture.
  5. Consider reducing reliance on aggressive WAF challenges to improve user experience while maintaining security.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. Detected Cloudflare security challenge page with Turnstile captcha and browser verification. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor

Technology

Stack
Cloudflare Turnstile, Cloudflare Challenge Platform, Cloudflare Insights Beacon

Analytics and tracking

Services
Cloudflare Insights
Tracking level
minimal

Advertising

Tracking pixels
Cloudflare Insights

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is blocked by Cloudflare security challenge (Turnstile captcha).
  2. No business content or metadata is accessible for analysis.
  3. No privacy, cookie, or terms of service policies found in the accessible content.
  4. No contact information or forms are visible.
  5. No social media or external business links found except Cloudflare domains.
  6. Technical infrastructure relies on Cloudflare for security and performance.
  7. No visible security headers or SSL configuration details available from provided data.
  8. No evidence of adult or unsafe content.
  9. Analysis incomplete due to WAF/security mechanisms. For accurate analysis, please contact guard@offseq.com.
Technical notes

Notes

The website is hosted behind Cloudflare, utilizing their challenge platform and Turnstile captcha for bot mitigation. The HTML content is minimal and serves only to verify human users before granting access. No CMS or other frameworks are detectable. The site uses Cloudflare Insights for performance and security monitoring. Due to the challenge page, performance, SEO, accessibility, and mobile optimization cannot be assessed. The technical stack is modern in terms of security infrastructure but lacks visible content or metadata for further evaluation.
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. 68/100 −6Medium27 findingsView report
  2. 74/100Medium20 findingsView report
Reviews of this site

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