iditena.org

Readiness by lane

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

Priority fixes for iditena.org

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

1. Priority 1 · Accelerate

   No render-blocking scripts in <head>

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

   Why it matters: A plain <script src> in the head stops the browser from showing anything until that file has downloaded and run.

   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.

   On Next.js: Use the next/script component with an appropriate loading strategy.

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

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

2. Priority 2 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for iditena.org, 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.

   On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.

   17% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

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.

   11% of Government Services peers do this.

   Guide: CDN Guide for Website Owners

4. Priority 4 · Harden

   security.txt published

   Observed: No valid /.well-known/security.txt with a Contact field was returned.

   What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

   On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.

   8% of Government Services peers do this.

   Guide: A Practical Website Health Check for Owners

What iditena.org already does well

Practices fewer than half of Government Services peers use.

• Structured data presentJSON-LD structured data found.15% of peers
• Reachable over IPv6IPv6 address published.27% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.30% of peers

What we saw

Homepage checked

https://iditena.org/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Cloudflare

Platform or framework

Next.js

DNS operators

Cloudflare

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

398 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

• form.gov.sg85
• nsw.gov.au86
• polisen.se84
• politie.nl86
• suomi.fi84

Government Services readiness benchmark