STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

nfse.gov.br

nfse.gov.br's public homepage, certificate and DNS checked against 31 practices and compared with 954 Government Services sites.

Readiness index
54/100

Government Services median 53

Ahead of
51%

of measured Government Services sites

Practices observed
15/30

1 of 31 could not be measured

Popularity band
Top 1K

Chrome UX Report top-sites list

Measured 2026-10-23 11:25:47 UTC from one location. How we measure

Readiness by lane

Green: nfse.gov.br. Thin bar: Government Services peer median.

Enable

51/100

Peers 59

Harden

74/100

Peers 59

Accelerate

24/100

Peers 41

Recover

0/100

Peers 25

Priority fixes for nfse.gov.br

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

  1. Priority 1 · Accelerate

    HTTP/2 negotiated

    Observed: The TLS handshake selected HTTP/1.1 instead of HTTP/2.

    Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

    What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

    55% of Government Services peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

  2. Priority 2 · Harden

    DMARC policy enforces quarantine or reject

    Observed: No DMARC record was found at _dmarc.nfse.gov.br.

    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.

  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.

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

What nfse.gov.br already does well

Practices fewer than half of Government Services peers use.

  • Structured data presentJSON-LD structured data found.15% of peers
  • Certificate lifetime of 100 days or lessShort-lived 89-day certificate from Let's Encrypt, already inside the 2027 limit.34% of peers
  • Social preview image setog:image present.36% of peers

What we saw

Homepage checked
https://www.nfse.gov.br/
Homepage response
HTTP 200, after 2 redirects
TLS
TLSv1.3
Certificate
Let's Encrypt, 89-day validity, expiring 2026-12-24
DNS operators
1 self-run or other nameserver domain
HSTS
max-age 365 days, includeSubDomains
Homepage HTML
114 KB, gzip
Images on homepage
9 (png 5, jpg 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

Observed 15

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Content Security Policy present
  • Referrer-Policy set
  • HTML compressed
  • Canonical URL declared
  • Mobile viewport configured
  • Structured data present
  • Social preview image set
  • Page language declared

Not measured 1

  • Static files cached for 30 days or more

Own nfse.gov.br?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

Live status for this site: Status Is Down: nfse.gov.br. This profile covers configuration only.

Compare with other Government Services sites