ign.es

Readiness by lane

Green: ign.es. Thin bar: Government Services peer median.

Priority fixes for ign.es

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.ign.es/ 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 Amazon CloudFront: Set the viewer protocol policy of each cache behaviour to Redirect HTTP to HTTPS.

   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 · Enable

   Mobile viewport configured

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

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

   92% of Government Services peers do this.

   Guide: Responsive Web Design Checklist for Real Devices

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.

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

   51% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Enable

   robots.txt published

   Observed: No robots.txt file was returned at the site root.

   What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

   61% of Government Services peers do this.

   Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes

What ign.es already does well

Practices fewer than half of Government Services peers use.

• DNSSEC signedDNSSEC delegation (DS record) present.19% of peers
• Reachable over IPv6IPv6 address published.27% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.39% of peers

What we saw

Homepage checked

https://www.ign.es/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Amazon CloudFront

DNS operators

1 self-run or other nameserver domain

DMARC policy

p=quarantine

Homepage HTML

0 KB, uncompressed

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

• azhar.gov.eg36
• egazette.gov.in36
• esw.et36
• keralapsc.gov.in36
• moi.gov.eg36

Government Services readiness benchmark