Skip to main content

Security report for dixieclerk.com

Dixie County Clerk of Court & Comptroller · Government · United States

Medium risk. 5 critical or high findings in SSL/TLS, GDPR outside view and 1 other check.

Security score

64/100

Risk levelMedium

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

Dixie County Clerk of Court & Comptroller is a local government office serving the citizens of Dixie County, Florida. The website provides comprehensive information about court and clerk services, online records, and resources for residents. The site is well-structured with clear navigation and links to relevant government and local agencies, reflecting a strong community focus and public service mission. The business model is a government public service entity with a small organizational size and a long-established presence since 2001. Technically, the website is built on WordPress with modern technologies including Vue.js and Tailwind CSS, hosted on Amazon AWS with Cloudflare DNS. It uses Google Tag Manager for analytics and tracking. The site is mobile optimized, accessible, and performs moderately well. SEO and metadata are properly implemented, including structured JSON-LD data and Open Graph tags. From a security perspective, the site enforces HTTPS and uses domain transfer protection. However, it lacks DNSSEC and explicit security headers, and there is no visible security or incident response policy. Privacy compliance is basic with a privacy policy present but no cookie consent mechanism. No vulnerabilities or suspicious content were detected. Overall, the website is trustworthy and professional, suitable for its government role. Strategic recommendations include enabling DNSSEC, adding security headers, implementing cookie consent, and publishing security and incident response policies to enhance compliance and security posture.

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

5 findings rated critical or high. Fix these first.

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

  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

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

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

Keep watching dixieclerk.com

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. The full timeline opens with your unlock code.

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
32
Security headers
60
Email security
70
DNS health
70
Network security
100
GDPR outside view
53
Average
64

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

Technical appendix

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

Business context

Business profile

The Dixie County Clerk of Court & Comptroller website positions itself as an essential government service provider for local residents. Its competitive advantage lies in its official status and comprehensive online services including court records search, payment portals, and public announcements. The business model is non-commercial, focused on public service and transparency. Revenue streams are likely government funded. The target customers are local citizens requiring court and clerk services. Growth indicators include active announcements and digital service offerings. The partnership ecosystem includes local government bodies, state agencies, and judicial circuits, enhancing service integration and community engagement.

Security posture

The security maturity level is moderate. HTTPS is enforced and domain transfer protection is enabled, indicating basic security hygiene. The absence of DNSSEC and security headers like CSP, HSTS, and X-Frame-Options reduces the defense-in-depth posture. No exposed sensitive data or vulnerable libraries were found, which is positive. The lack of visible incident response contacts or security policies suggests limited transparency in security governance. Privacy compliance is partial, with a privacy policy but no cookie consent mechanism. Overall, the site is secure for general public use but could improve in advanced security controls and compliance documentation.

Recommendations

  1. Enable DNSSEC to protect against DNS spoofing and improve domain security.
  2. Implement HTTP security headers such as Content Security Policy (CSP), HSTS, and X-Frame-Options to mitigate common web attacks.
  3. Add a cookie consent banner/mechanism to comply with privacy regulations and improve user transparency.
  4. Publish a clear security policy and incident response contact information to enhance trust and preparedness.
  5. Regularly audit third-party scripts and dependencies to ensure no vulnerable libraries are included.

Contact details published on the site

Addresses
Legal name
Dixie County Clerk of Court & Comptroller
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Dixie County Clerk of Court & Comptroller
Description
The Clerk of the Circuit Court is an elected office established according to the Florida Constitution for the purpose of serving the citizens of each county as a public trustee.
Key services
Court Services, Clerk Services, Online Services, Online Records
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Cloudflare DNS, Google Tag Manager, Typekit Fonts, Amazon S3 (for media hosting), JavaScript, CSS
Frameworks
Tailwind CSS (indicated by class names)
Platforms
AWS S3, Cloudflare
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Domain status clientTransferProhibited
  • No exposed sensitive data in HTML
  • No visible vulnerable libraries

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Official government website for Dixie County Clerk of Court & Comptroller
  2. Clear navigation with mega menus for departments, services, resources, and about sections
  3. Multiple external links to official government and local agencies
  4. Use of modern web technologies and hosting infrastructure
  5. No signs of malicious or suspicious content
  6. No visible privacy or cookie consent banners
  7. No visible security policy or incident response information
  8. WHOIS data consistent with business claims and domain age appropriate
Technical notes

Notes

The website uses a modern technology stack with WordPress CMS, Vue.js framework, and Tailwind CSS for styling. Hosting is distributed with Amazon S3 for media and Cloudflare for DNS, providing scalability and reliability. Google Tag Manager is used for analytics and marketing. The site is mobile responsive and accessible with good SEO practices including structured data and meta tags. Performance is moderate, likely due to media assets hosted on S3 and multiple external scripts. There is no indication of technical debt or outdated technologies, but security header implementation is lacking. Overall, the technical infrastructure supports a stable and user-friendly experience with room for security enhancements.
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 dixieclerk.com. 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 dixieclerk.com.

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.