State of Utah · Government · United States
Medium risk. 6 critical or high findings in Security headers, GDPR outside view and 2 other checks.
Utah.gov is the official website of the State of Utah, serving as a comprehensive portal for government services, information, and resources targeted at residents, businesses, and visitors. The site offers key services such as vehicle renewal, hunting and fishing licenses, driver license renewal, job listings, vital records, and local government resources. It holds a strong market position as the authoritative source for Utah state government information. Technically, the website employs modern web standards including HTML5, CSS3, and JavaScript, with integrations such as Google Tag Manager for analytics and Qualtrics for user feedback. The Utah Design System Header framework is used for consistent UI/UX. The site is mobile-optimized and accessible, with good SEO practices and moderate performance. From a security perspective, the site enforces HTTPS and avoids exposing sensitive data. However, it lacks some recommended security headers and does not provide a vulnerability disclosure policy or explicit incident response contacts. Privacy compliance is partial, with a privacy policy present but no cookie consent mechanism detected. Overall, Utah.gov demonstrates a high level of professionalism, trustworthiness, and technical maturity appropriate for a government entity. The main risk lies in incomplete WHOIS data and minor privacy compliance gaps. Strategic improvements in security headers, privacy mechanisms, and incident response transparency would enhance the site's security posture and user trust.
Scanned
NIS2 Art. 21(2)
This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.
GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.
6 findings rated critical or high. Fix these first.
Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.
Prevents clickjacking attacks
What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"
Controls resources the browser is allowed to load
What to do: Implement a Content-Security-Policy appropriate for your application
These are the privacy signals visitors and data protection authorities look for under GDPR.
GDPR requires clear information about cookie usage
What to do: Add a dedicated cookie policy explaining cookie usage and purposes
GDPR requires explicit consent for non-essential cookies
What to do: Implement a cookie consent banner that appears on first visit
SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.
DKIM selector 'google' uses 296-bit key
What to do: Use at least 2048-bit RSA keys for DKIM
Need hands-on remediation? Email guard@offseq.com
This scan found 26 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.
€25per month
Email alerts on material changes and an exportable JSON history of every change.
Billed monthly to your card. Cancel anytime. See sample alerts.
€39.90one-time
Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.
Each check with its score, findings and the evidence it collected.
The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.
Counted in this score
Not counted
Findings that cap the score at 49
Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.
Partial scans
When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.
Risk levels
Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.
Leaked records that mention utah.gov, from OffSeq Breach.
See the 10 newest leaked credentials
A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for utah.gov.
Select it in the checkout above.
Breach keeps ingesting new leaks, so these numbers can grow between scans.
Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.
Automated reading of the public site. Ratings are indicative.
Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.
Retrieved 2026-10-25
Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.
Reviews of this site
Share your experience with utah.gov. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review utah.gov.