Skip to main content

Security report for guamcourts.org

Judiciary of Guam · Government · United States

Medium risk. 9 critical or high findings in Email security, Security headers and 2 other checks.

Security score

59/100

Risk levelMedium

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

The Judiciary of Guam website serves as the official online presence for Guam's judicial system, providing comprehensive information and services related to the Supreme and Superior Courts, judicial council, probation services, and public notices. The site targets a broad audience including legal professionals, residents, probationers, jurors, media, and students. It offers key services such as eCourt filing, court calendars, legal resources, and access to court opinions. Technically, the site uses standard web technologies including HTML5, CSS3, JavaScript, Google Fonts, and integrates third-party services like Tawk.to live chat and Facebook SDK for social media. The site appears to be custom-built without a common CMS and is hosted with DNS managed by UberNS and registered via Network Solutions. Security posture shows room for improvement with no DNSSEC, no visible security headers, and absence of privacy and cookie policies, which are critical for compliance and user trust. The domain WHOIS data is consistent with a legitimate government entity, with a long registration history and appropriate domain status settings. Overall, the website is functional, professional, and trustworthy but would benefit from enhanced security and privacy compliance measures.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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

9 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.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. 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';…

  3. GDPR outside view

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

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

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

Keep watching guamcourts.org

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.

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
72
Security headers
15
Email security
60
DNS health
70
Network security
100
GDPR outside view
35
Average
59

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 guamcourts.org, from OffSeq Breach.

Total records
2
Employees
0
Customers
0
Third parties
2
Weak passwords
0%

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 guamcourts.org.

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

The Judiciary of Guam holds a central position as the official judicial authority for the territory of Guam, operating under government funding. Its business model is service-oriented, focusing on providing judicial and legal services to the public and legal community. The website supports transparency and accessibility through extensive resources, calendars, and public notices. The presence of official social media channels and live chat indicates engagement efforts. The domain's longevity and consistent registration details reinforce credibility. However, the lack of explicit privacy and cookie policies may expose the entity to compliance risks, especially under evolving data protection regulations. The Judiciary's partnerships with local legal bodies and educational institutions are evident through linked domains and resources. Growth indicators include recent updates to court decisions and news releases, reflecting active maintenance and communication.

Security posture

The current security posture of the Judiciary of Guam website is moderate but has notable gaps. The absence of DNSSEC and security headers such as Content-Security-Policy and X-Frame-Options reduces protection against DNS spoofing and clickjacking attacks. No visible HTTPS enforcement or HSTS headers were detected in the provided data, which could impact secure communications. The site uses third-party scripts (Tawk.to and Facebook SDK) which require monitoring for vulnerabilities. No incident response or security policy information is publicly available, limiting transparency in handling security events. The domain status clientTransferProhibited is a positive control to prevent unauthorized domain transfers. Overall, while no critical vulnerabilities were detected, the site should implement stronger security controls and privacy compliance to enhance trust and resilience.

Recommendations

  1. Enable DNSSEC on the domain to protect against DNS spoofing and improve domain security.
  2. Implement and prominently display a comprehensive privacy policy and cookie policy with consent mechanisms to comply with GDPR and other regulations.
  3. Add essential security headers such as Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, and Strict-Transport-Security to harden the website against common web attacks.
  4. Ensure HTTPS is enforced site-wide with valid SSL certificates and configure HSTS headers to prevent protocol downgrade attacks.
  5. Publish incident response contact information and security policies to improve transparency and user trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Judiciary of Guam
Description
Official website for the Judiciary of Guam providing information about courts, judicial services, calendars, court opinions, and public notices.
Key services
Court calendars and schedules, eCourt services including eFiling and payments, Access to court opinions and decisions, Probation and marshal services, Public notices and judicial council information, Legal resources and forms
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, Google Fonts (Cabin), Tawk.to live chat, Facebook SDK
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
50/100
Good practices seen
  • Domain status clientTransferProhibited to prevent unauthorized transfers

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Tawk.to, Facebook SDK
Marketing tools
Tawk.to live chat, Facebook SDK
Transparency
basic

Site quality

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

Key observations

  1. Official government judiciary website for Guam
  2. Comprehensive navigation with many subpages and resources
  3. No visible privacy or cookie policies which is a compliance gap
  4. Use of third-party live chat and social media integrations
  5. No visible security headers or DNSSEC enabled
  6. Domain WHOIS data consistent with legitimacy
  7. No WAF or blocking detected
Technical notes

Notes

The website is built using standard web technologies including HTML5, CSS3, and JavaScript, with external dependencies on Google Fonts, Tawk.to live chat, and Facebook SDK. The site appears custom-developed without a known CMS, which may reduce exposure to common CMS vulnerabilities but could increase maintenance overhead. Performance is moderate with basic mobile optimization and accessibility features. Navigation is clear with multi-level menus and structured content. Hosting details are limited but DNS is managed by UberNS and domain registered via Network Solutions. The site lacks modern security enhancements such as DNSSEC and security headers. There is an opportunity to improve SEO and accessibility compliance. Overall, the technical infrastructure supports the business needs but would benefit from modernization and security hardening.
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 guamcourts.org. 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 guamcourts.org.

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.