Skip to main content

Security report for allcartuning.com

Allcartuning · Transportation · Austria

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

Security score

45/100

Risk levelHigh

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

Allcartuning is a specialized automotive tuning service provider based in Austria, focusing on chiptuning and eco-tuning for passenger cars, trucks, and agricultural vehicles. With over 14 years of experience, the company offers motor control unit programming and software tuning, supported by a network of authorized dealers. The website reflects a niche market position with a clear business model centered on automotive performance enhancement and tuning tools. Technically, the site runs on TYPO3 CMS with PHP 7.4 backend and uses common frontend libraries like jQuery and Bootstrap. It is hosted behind Cloudflare CDN but lacks a valid SSL certificate, resulting in HTTP-only access, which is a significant security concern. The site includes basic privacy and cookie policies with GDPR consent mechanisms but lacks explicit security or incident response policies. Overall, the website is functional and professionally presented but requires urgent improvements in security posture, especially regarding HTTPS implementation and modern security headers.

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

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
0
Security headers
15
Email security
50
DNS health
85
Network security
100
GDPR outside view
18
Average
45

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

The company targets automotive enthusiasts and professionals seeking performance tuning solutions for various vehicle types. Its business model relies on software tuning services, dealer partnerships, and sales of tuning tools. The presence of a dealer locator and newsletter indicates active customer engagement and marketing efforts. The company maintains a moderate digital presence with social media integration and Google/Facebook domain verifications, enhancing trust. However, the lack of advanced security policies and outdated frontend libraries may pose risks to customer data and trust. The business appears stable with consistent domain registration data and a focused market niche in the transportation sector.

Security posture

The website's security posture is weak due to the absence of HTTPS, no HSTS, and no modern TLS protocols enabled. While no critical vulnerabilities like Heartbleed or POODLE were detected, the lack of encryption exposes users to potential data interception risks. Security headers are minimal, and no incident response or vulnerability disclosure policies are present. The use of an outdated jQuery version could introduce client-side vulnerabilities. The site does implement GDPR-related consent for data collection but lacks comprehensive security frameworks or certifications. Immediate remediation is recommended to secure communications and enhance trust.

Recommendations

  1. Implement a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable HSTS with includeSubDomains and preload to enforce secure connections.
  3. Upgrade TLS protocols to support TLS 1.2 or TLS 1.3 and disable legacy protocols.
  4. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  5. Update frontend libraries like jQuery to the latest secure versions to mitigate vulnerabilities.
  6. Publish a clear security policy and incident response contact information.
  7. Consider adding a vulnerability disclosure policy or security.txt file.
  8. Improve mobile optimization and accessibility features for better user experience.
  9. Regularly audit and update privacy and cookie policies to maintain GDPR compliance.
  10. Enhance website performance monitoring and optimize load times.
Technical notes

Notes

The website uses a PHP 7.4 backend with TYPO3 CMS and a frontend stack including jQuery 1.11.1, Bootstrap, Font Awesome, and Owl Carousel. It is hosted behind Cloudflare CDN, providing some protection and performance benefits. However, the lack of HTTPS and modern TLS protocols is a critical technical deficiency. The site includes multiple CSS and JS assets but lacks performance metrics data. Mobile optimization is basic, and accessibility features are minimal. The newsletter form collects personal data with GDPR consent, indicating some compliance awareness. Overall, the technical infrastructure is functional but outdated in security and performance aspects, requiring modernization to meet current web standards and security best practices.
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 allcartuning.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 allcartuning.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.