ncdot.gov

Readiness by lane

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

Priority fixes for ncdot.gov

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   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. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   HTTP/2 negotiated

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

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

   55% of Government Services peers do this.

   Guide: CDN Guide for Website Owners

3. Priority 3 · Harden

   CAA records limit who can issue certificates

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

4. Priority 4 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from DigiCert Inc had a 198-day validity period, longer than the 100-day maximum that applies from March 2027.

   What to do: Move to automated issuance and renewal now, while you still have time to test it.

   34% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What ncdot.gov 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
• Social preview image setog:image present.36% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.39% of peers

What we saw

Homepage checked

https://www.ncdot.gov/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.2, http/1.1

Certificate

DigiCert, 198-day validity, expiring 2027-04-16

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

50 KB, gzip

Images on homepage

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

• fda.gov71
• fonasa.gob.cl71
• gswshelper.com71
• teluguschemes.co.in71
• tjdft.jus.br71

Government Services readiness benchmark