nelf.gov.ng

Readiness by lane

Green: nelf.gov.ng. Thin bar: Government Services peer median.

Priority fixes for nelf.gov.ng

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 Next.js: Add the header in the headers() option of next.config.js for all routes.

   51% of Government Services 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

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for nelf.gov.ng 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

   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

4. Priority 4 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Next.js: Add it in next.config.js headers().

   68% of Government Services peers do this.

   Guide: A Practical Website Health Check for Owners

What nelf.gov.ng already does well

Practices fewer than half of Government Services peers use.

• Static files cached for 30 days or moreLong-lived caching on static files.30% of peers
• Offscreen images lazy-loadedNative lazy loading in use.36% of peers

What we saw

Homepage checked

https://nelf.gov.ng/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Amazon, 197-day validity, expiring 2027-03-12

Platform or framework

Next.js

DNS operators

Azure DNS

DMARC policy

p=none

Homepage HTML

32 KB, gzip

Images on homepage

8 (svg 4)

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

• gesetze-im-internet.de46
• jucerja.rj.gov.br46
• nas.gov.qa46
• njportal.com46
• ossc.gov.in46

Government Services readiness benchmark