iana.org

Readiness by lane

Green: iana.org. Thin bar: Government Services peer median.

Priority fixes for iana.org

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

1. Priority 1 · Harden

   HTTP requests move to HTTPS

   Observed: A request to http://www.iana.org/ was not redirected to HTTPS.

   Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.

   What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.

   On Cloudflare: Turn on Always Use HTTPS under SSL/TLS > Edge Certificates.

   88% of Government Services peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for iana.org 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.

   52% of Government Services peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Enable

   XML sitemap discoverable

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

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

   42% of Government Services peers do this.

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

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   39% of Government Services peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

What iana.org already does well

Practices fewer than half of Government Services peers use.

• HTTP/3 advertisedHTTP/3 advertised.11% of peers
• CAA records limit who can issue certificatesCAA limits issuance to digicert.com, letsencrypt.org, pki.goog and others.17% of peers
• DNSSEC signedDNSSEC delegation (DS record) present.19% of peers

What we saw

Homepage checked

https://www.iana.org/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2027-01-17

CDN or edge

Cloudflare

DNS operators

2 self-run or other nameserver domains

HSTS

max-age 558 days, preload

DMARC policy

p=none

Homepage HTML

6 KB, br

Images on homepage

0

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 Government Services sites

• belastingdienst.nl68
• imserso.es68
• inps.it68
• transportstyrelsen.se69
• www.gov.br69

Government Services readiness benchmark