STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

planalto.gov.br

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

Readiness index
21/100

Government Services median 53

Ahead of
1.9%

of measured Government Services sites

Practices observed
5/28

3 of 31 could not be measured

Popularity band
Top 10K

Chrome UX Report top-sites list

Measured 2026-10-23 12:00:56 UTC from one location. How we measure

Readiness by lane

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

Enable

8/100

Peers 59

Harden

29/100

Peers 59

Accelerate

21/100

Peers 41

Recover

0/100

Peers 25

Priority fixes for planalto.gov.br

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.planalto.gov.br/ 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.

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

  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.

  3. Priority 3 · Accelerate

    HTML compressed

    Observed: The homepage HTML (2 KB) was delivered without gzip, Brotli or zstd compression.

    What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.

    74% of Government Services peers do this.

  4. Priority 4 · Harden

    TLS 1.3 negotiated

    Observed: The TLS connection negotiated TLSv1.2.

    What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

    77% of Government Services peers do this.

What planalto.gov.br already does well

Practices fewer than half of Government Services peers use.

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

What we saw

Homepage checked
https://www.planalto.gov.br/
Homepage response
HTTP 200
TLS
TLSv1.2
Certificate
Sectigo, 396-day validity, expiring 2027-01-23
DNS operators
1 self-run or other nameserver domain
HSTS
max-age 730 days, includeSubDomains, preload
Homepage HTML
2 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

Own planalto.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: planalto.gov.br. This profile covers configuration only.

Compare with other Government Services sites