template.net

Readiness by lane

Green: template.net. Thin bar: Design & Content Creation peer median.

Priority fixes for template.net

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

1. Priority 1 · Harden

   HSTS kept for at least a year

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

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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.

   37% of Design & Content Creation peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website 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.

   29% of Design & Content Creation peers do this.

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

3. Priority 3 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for template.net, so any public certificate authority may issue for it.

   What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

   17% of Design & Content Creation peers do this.

   Guide: HTTPS and TLS 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 Amazon CloudFront: Enable it in a response headers policy (security headers section).

   39% of Design & Content Creation peers do this.

   Guide: A Practical Website Health Check for Owners

What template.net already does well

Practices fewer than half of Design & Content Creation peers use.

• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.41% of peers
• HTTP/3 advertisedHTTP/3 advertised.43% of peers
• Framing restrictedFraming controls present.48% of peers

What we saw

Homepage checked

https://www.template.net/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-16

CDN or edge

Amazon CloudFront, Google edge

DNS operators

Google Cloud DNS

DMARC policy

p=quarantine

Homepage HTML

145 KB, gzip

Images on homepage

75 (webp 329, png 32, jpg 5)

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 Design & Content Creation sites

• kleki.com78
• runway.com79
• slidescarnival.com79
• slidesgo.com79
• vistaprint.ca79

Design & Content Creation readiness benchmark