Skip to main content

Security report for ehawaii.gov

State of Hawaiʻi · Government · United States

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

62/100

Risk levelMedium

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

The website portal.ehawaii.gov serves as the official digital gateway for the State of Hawaiʻi, providing comprehensive resources and services for government entities, residents, businesses, and visitors. It functions as a centralized platform offering access to government departments, online services such as business registration and driver records, news updates, and visitor information. The site is well-positioned as an authoritative source for state-related information and services, reflecting a large government entity with a broad target audience. From a technical perspective, the site employs modern web technologies including Google Analytics for tracking, Freshchat for user support, and Siteimprove Analytics for performance monitoring. The design is professional, mobile-optimized, and accessible, with clear navigation and consistent branding. However, no explicit CMS or hosting provider details are discernible from the source. Security-wise, the site enforces HTTPS and uses secure form submissions, but lacks visible security headers and published security policies or incident response contacts. No vulnerabilities or exposed sensitive data were detected in the HTML content. Privacy compliance is partially addressed with a privacy policy and terms of use, but no cookie consent mechanism or GDPR-specific indicators were found. WHOIS data is incomplete, lacking registrar and registrant details, which slightly reduces domain trustworthiness, though the site content and external references strongly support legitimacy. Overall, the site demonstrates a strong security posture and professional digital presence appropriate for a government portal, with recommendations to enhance security headers, privacy compliance, and incident response transparency to further strengthen trust and compliance.

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

7 findings rated critical or high. Fix these first.

  1. Security headers

    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.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…
  2. 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 ehawaii.gov

This scan found 27 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
67
Security headers
15
Email security
75
DNS health
60
Network security
100
GDPR outside view
53
Average
62

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 ehawaii.gov, from OffSeq Breach.

Total records
2,716
Employees
2
Customers
2,712
Third parties
2
Weak passwords
7%

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 ehawaii.gov.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

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

Business context

Business profile

The portal is a critical government digital asset serving multiple stakeholder groups including government officials, residents, businesses, and tourists. Its business model is informational and service-oriented, focusing on providing authoritative content and facilitating online government transactions. The site’s market position is that of the official state government portal, which inherently carries high trust and responsibility. Revenue streams are not applicable as it is a government service. The partnership ecosystem includes various state departments and agencies, as well as tourism and public safety organizations. Growth indicators include recent news updates and active service usage statistics. Strategic observations highlight the importance of maintaining high availability, security, and compliance to serve a diverse and broad user base effectively.

Security posture

The website exhibits a mature security posture with mandatory HTTPS and secure form handling. The absence of visible security headers such as Content-Security-Policy and X-Frame-Options is a gap that should be addressed to mitigate risks like clickjacking and content injection. No evidence of exposed credentials or vulnerable libraries was found. Privacy compliance is partial, lacking cookie consent mechanisms and GDPR-specific disclosures. Incident response and vulnerability disclosure information are not published, which limits transparency and user trust in security incident handling. Overall, the site is secure but could improve by adopting comprehensive security headers, publishing security policies, and implementing cookie consent to align with best practices and regulatory requirements.

Recommendations

  1. Implement comprehensive HTTP security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  2. Add a cookie consent banner/mechanism to comply with privacy regulations and improve user transparency.
  3. Publish a dedicated security policy and incident response contact information to enhance trust and preparedness.
  4. Establish and publicize a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  5. Regularly audit and update third-party scripts and analytics tools to minimize potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
State of Hawaiʻi
Description
The official website of the State of Hawaiʻi providing resources for government, residents, business, and visitors.
Key services
Government departments and agencies directory, Online services including business registration and driver records, News and alerts, Visitor information and resources
Content quality
excellent
Branding
consistent

Technology

Stack
Google Analytics, Freshchat, Siteimprove Analytics, Font Awesome, jQuery (implied by $ usage in scripts)
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Secure forms with POST method

Analytics and tracking

Services
Google Analytics, Siteimprove Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Siteimprove Analytics
Marketing tools
Freshchat
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenge.
  2. Content is rich, well-structured, and professionally presented.
  3. Strong government branding and official seals present.
  4. Multiple external government-related domains linked.
  5. No contact emails or phone numbers explicitly listed on homepage.
  6. No explicit cookie consent mechanism detected.
  7. Security headers not visible in HTML source; likely set at server level but not confirmed.
  8. Multiple Google Analytics IDs used, indicating extensive analytics tracking.
  9. No vulnerability disclosure or security.txt found.
  10. Privacy policy and terms of use pages are present and linked in footer.
Technical notes

Notes

The website uses a modern technology stack with Google Analytics, Freshchat, and Siteimprove Analytics integrated for tracking and user engagement. The front-end employs standard web technologies with responsive design and accessibility considerations. No CMS or hosting provider details are explicitly identified. Performance is moderate with preloading of fonts and asynchronous loading of scripts to optimize speed. The site structure is semantic and SEO-friendly with appropriate meta tags and Open Graph data. Technical risks are minimal but include the absence of visible security headers and lack of explicit privacy consent mechanisms. Opportunities exist to enhance technical robustness by adopting security best practices and improving privacy compliance features.
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

Reviews of this site

Share your experience with ehawaii.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 ehawaii.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.