automoto.it

Readiness by lane

Green: automoto.it. Thin bar: Cars & Automotive peer median.

Priority fixes for automoto.it

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for automoto.it was p=none, which asks receivers to take no action on failing mail.

   Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   41% of Cars & Automotive peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.

   Guide: A Practical Website Health Check for Owners

2. Priority 2 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   31% of Cars & Automotive peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

3. Priority 3 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   On Cloudflare: Enable HTTP/3 (with QUIC) under Speed > Optimization > Protocol Optimization.

   30% of Cars & Automotive peers do this.

   Guide: CDN Guide for Website Owners

4. Priority 4 · Harden

   X-Content-Type-Options: nosniff

   Observed: The homepage response did not include X-Content-Type-Options: nosniff.

   What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.

   On Cloudflare: Add the header with a response header transform rule.

   52% of Cars & Automotive peers do this.

   Guide: A Practical Website Health Check for Owners

What automoto.it already does well

Practices fewer than half of Cars & Automotive peers use.

• CAA records limit who can issue certificatesCAA limits issuance to comodoca.com, digicert.com, letsencrypt.org and others.7.8% of peers
• HSTS kept for at least a yearHSTS with a 730-day max-age covering subdomains.41% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.45% of peers

What we saw

Homepage checked

https://www.automoto.it/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

ZeroSSL, 90-day validity, expiring 2026-12-11

DNS operators

Cloudflare

HSTS

max-age 730 days, includeSubDomains, preload

DMARC policy

p=none

Homepage HTML

640 KB, gzip

Images on homepage

130 (jpg 121, webp 7, png 6, svg 1)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Cars & Automotive sites

• auto-data.net79
• autovit.ro79
• carsales.com.au79
• gsfcarparts.com80
• zigwheels.com81

Cars & Automotive readiness benchmark