Skip to main content

Security report for utah.gov

State of Utah · Government · United States

Medium risk. 8 critical or high findings in Email security, SSL/TLS and 2 other checks.

Security score

61/100

Risk levelMedium

0–100, higher is better. How it is calculated

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

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.

Priority findings

8 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

  3. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

Need hands-on remediation? Email guard@offseq.com

Keep watching utah.gov

This scan found 25 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.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. See sample alerts.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

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

SSL/TLS
37
Security headers
15
Email security
75
DNS health
85
Network security
100
GDPR outside view
53
Average
61

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

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.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

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

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention utah.gov, from OffSeq Breach.

Total records
18,456
Employees
102
Customers
18,018
Third parties
336
Weak passwords
15%

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.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

DTS operates as a critical government IT service provider, supporting executive branch agencies in Utah. Its market position is strong as the primary technology services entity for the state government. The business model is service-oriented, focusing on internal government customers and employees. Key services include IT infrastructure, employee support portals, and strategic technology initiatives such as AI and data privacy. The organization benefits from strong branding consistency and trust signals typical of official government websites. Partnerships with other Utah government domains reinforce its ecosystem. The site’s content and navigation cater to government employees and agencies, emphasizing transparency and accessibility.

Security posture

The website demonstrates a good security posture with enforced HTTPS, use of Google reCAPTCHA to protect forms, and integration with a government identity provider (UtahID). However, the absence of explicit security headers like X-Frame-Options and X-Content-Type-Options is a minor gap. No vulnerabilities or exposed sensitive data were detected in the HTML content. The lack of a published security policy or incident response contact limits transparency in security governance. The site would benefit from adding a security.txt file and more visible security documentation to enhance trust and readiness for vulnerability disclosures.

Recommendations

  1. Implement and enforce security headers such as X-Frame-Options and X-Content-Type-Options to mitigate clickjacking and MIME sniffing risks.
  2. Add a visible cookie consent banner to comply with privacy regulations and improve user transparency.
  3. Publish a dedicated security policy and incident response contact information to enhance security governance and user trust.
  4. Regularly audit and update third-party scripts and plugins to minimize vulnerabilities.
  5. Consider adding a security.txt file to facilitate responsible vulnerability disclosure and improve security posture.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Division of Technology Services
Description
The Division of Technology Services (DTS) is the IT service provider for the executive branch of the state of Utah, offering innovative solutions and exceptional services to state agencies. They provide a wide variety of IT services, employee resources, and strategic initiatives including Artificial Intelligence, Data Privacy, Security and Access Management, and more.
Key services
IT service provision for executive branch agencies, Employee IT resources and support, Strategic IT initiatives and innovation
Content quality
excellent
Branding
consistent

Technology

Stack
WordPress, jQuery, Google Tag Manager, Google reCAPTCHA, Utah Design System, FontAwesome
Frameworks
WordPress theme: Pro, Utah Design System
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of Google reCAPTCHA for forms
  • No exposed sensitive data in HTML
  • Use of official UtahID sign-in system

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Qualtrics
Marketing tools
Qualtrics
Transparency
basic

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Official Utah government website for Division of Technology Services
  2. Comprehensive navigation with clear menu structure
  3. Use of Utah Design System for consistent branding
  4. Integration with UtahID for authentication
  5. Presence of Google Tag Manager and Qualtrics for analytics and feedback
  6. No signs of malicious or suspicious content
  7. WHOIS data incomplete but domain under utah.gov domain space
  8. No cookie consent banner detected
  9. No explicit security.txt or vulnerability disclosure found
Standards and sources

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

Earlier scans of this domain

  1. 66/100Medium35 findingsView report
Reviews of this site

Share your experience with utah.gov. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review utah.gov.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.