archive.ph

Readiness by lane

Green: archive.ph. Thin bar: Web Tools peer median.

Priority fixes for archive.ph

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

1. Priority 1 · Enable

   Mobile viewport configured

   Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.

   Why it matters: Without it, phones render the page at desktop width and shrink it, which makes text tiny and hard to use.

   What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.

   97% of Web Tools peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: Responsive Web Design Checklist for Real Devices

2. Priority 2 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   92% of Web Tools peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

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

   30% of Web Tools peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Accelerate

   Modern image formats in use

   Observed: The homepage had 3 images and none used WebP or AVIF.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   37% of Web Tools peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

What archive.ph already does well

Practices fewer than half of Web Tools peers use.

• Nameservers spread across providersNameservers spread across more than one operator.6.1% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=quarantine.23% of peers
• Framing restrictedFraming controls present.48% of peers

What we saw

Homepage checked

https://archive.ph/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-02

DNS operators

4 self-run or other nameserver domains

DMARC policy

p=quarantine

Homepage HTML

14 KB, gzip

Images on homepage

3

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 Web Tools sites

• archive.is61
• cuitonline.com61
• grabnwatch.com61
• time.ir62
• vww-y2mate.com62

Web Tools readiness benchmark