autobild.es

Readiness by lane

Green: autobild.es. Thin bar: Cars & Automotive peer median.

Priority fixes for autobild.es

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

1. Priority 1 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   83% of Cars & Automotive peers do this. Limit: Only the standard location was requested, once, at the time of the check.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

2. Priority 2 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.

   41% of Cars & Automotive peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

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

   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.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · 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

What autobild.es already does well

Practices fewer than half of Cars & Automotive peers use.

• Referrer-Policy setReferrer-Policy present.26% of peers
• HTTP/3 advertisedHTTP/3 advertised.30% of peers
• Reachable over IPv6IPv6 address published.42% of peers

What we saw

Homepage checked

https://www.autobild.es/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-01-19

CDN or edge

Amazon CloudFront

DNS operators

Cloudflare

DMARC policy

p=none

Homepage HTML

204 KB, gzip

Images on homepage

80 (jpg 92, webp 34, svg 10, png 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

• auteco.com.co72
• autoscout24.it72
• chileautos.cl72
• togg.com.tr73
• toyota.mx73

Cars & Automotive readiness benchmark