oregon.gov

Readiness by lane

Green: oregon.gov. Thin bar: Government Services peer median.

Priority fixes for oregon.gov

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

1. Priority 1 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.

   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. Limit: Only the standard location was requested, once, at the time of the check.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

2. Priority 2 · Accelerate

   No render-blocking scripts in <head>

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

   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.

   39% of Government Services peers do this.

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

3. Priority 3 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   41% of Government Services peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

4. Priority 4 · Harden

   CAA records limit who can issue certificates

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

   17% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What oregon.gov already does well

Practices fewer than half of Government Services peers use.

• Reachable over IPv6IPv6 address published.27% of peers
• Social preview image setog:image present.36% of peers
• Content Security Policy presentContent-Security-Policy present.41% of peers

What we saw

Homepage checked

https://www.oregon.gov/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-02-07

CDN or edge

Amazon CloudFront

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=quarantine

Homepage HTML

92 KB, gzip

Images on homepage

1 (svg 1)

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

• fao.org70
• myscheme.gov.in70
• sarkaricsc.com70
• service-public.gouv.fr70
• tjsc.jus.br71

Government Services readiness benchmark