Skip to main content

Security report for fayetteville-ar.gov

City of Fayetteville · Government · United States

Medium risk. 5 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

68/100

Risk levelMedium

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

The City of Fayetteville's official website serves as a comprehensive portal for residents and visitors to access municipal services, pay utility bills, apply for permits, and stay informed about community events and government activities. The site is well-branded with consistent city imagery and provides clear navigation to key services and resources. The target audience primarily includes local residents, businesses, and community stakeholders. Technically, the website leverages modern JavaScript libraries such as jQuery and AlpineJS, integrates Google Tag Manager for analytics, and uses Azure Application Insights for telemetry, indicating a moderate level of digital maturity. Accessibility tools like Monsido and Google Translate enhance usability for diverse users. Security posture is adequate with HTTPS enforced and anti-forgery tokens implemented in forms, but lacks explicit security headers and published security policies. WHOIS data is incomplete or restricted, which slightly impacts trust but does not detract from the site's legitimacy given its official nature. Overall, the website is professional, functional, and trustworthy, though improvements in privacy compliance and security transparency are recommended.

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

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

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

Keep watching fayetteville-ar.gov

This scan found 23 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
47
Security headers
40
Email security
85
DNS health
80
Network security
100
GDPR outside view
53
Average
68

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

As a municipal government website, Fayetteville operates in the government sector providing essential public services and information dissemination. Its business model is service-oriented, focusing on community engagement, transparency, and operational efficiency. The site supports multiple revenue-neutral services such as utility payments and permit applications. The presence of job listings and public meeting information indicates active civic participation. The website's partnership ecosystem includes CivicPlus as the CMS provider and integrations with social media platforms for outreach. Growth indicators include active news updates and community involvement features. Strategic observations suggest a focus on digital accessibility and public engagement, with opportunities to enhance security and privacy compliance to meet evolving regulatory standards.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and use of anti-forgery tokens to protect form submissions. However, the absence of explicit security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options represents a gap in defense-in-depth strategies. No published security policy or incident response contact information was found, limiting transparency in security governance. The lack of a vulnerability disclosure or security.txt file reduces the site's openness to responsible vulnerability reporting. Third-party scripts from Google, Azure, and Monsido are used, which require ongoing monitoring for vulnerabilities. Overall, the site is secure for general public use but would benefit from enhanced security controls and published policies to improve trust and compliance.

Recommendations

  1. Implement and enforce security headers including CSP, X-Frame-Options, and X-Content-Type-Options to mitigate common web attacks.
  2. Publish a clear security policy and incident response contact information to improve transparency and readiness.
  3. Add a vulnerability disclosure or security.txt file to facilitate responsible security reporting.
  4. Introduce a cookie consent mechanism to comply with privacy regulations such as GDPR.
  5. Regularly audit and update third-party scripts and dependencies to minimize vulnerabilities.

Contact details published on the site

Addresses
Legal name
City of Fayetteville
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
City of Fayetteville
Description
Official website for the City of Fayetteville, Arkansas. Learn about all departments, city services and events. Pay utility bills, report concerns, apply for permits, sign up for notifications, view calendars of events and meetings, and much more.
Key services
Utility bill payment, Permit applications, Public meeting agendas and minutes, Community event calendar, Job openings, Report a concern, Public engagement portal
Content quality
good
Branding
consistent

Technology

Stack
jQuery 3.7.1, jQuery Migrate 3.5.2, AlpineJS 3.14.1, Google Tag Manager, Azure Application Insights, Monsido (accessibility and analytics), Google Translate
Frameworks
CivicPlus CMS
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enforced
  • Anti-forgery tokens in forms
  • Use of Azure Application Insights for telemetry

Analytics and tracking

Services
Google Analytics (via GTM), Azure Application Insights, Monsido analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Monsido heatmaps and page correct
Marketing tools
Azure Application Insights, Monsido
Transparency
basic

Site quality

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

Key observations

  1. Official city government website with comprehensive public service information
  2. Good use of modern web technologies and accessibility tools
  3. No signs of malicious or suspicious content
  4. WHOIS data incomplete or unavailable, possibly due to privacy or registry restrictions
  5. No explicit privacy or cookie consent banners detected
  6. Social media presence is well integrated
  7. No visible security.txt or vulnerability disclosure
Technical notes

Notes

The website is built on the CivicPlus CMS platform, utilizing modern JavaScript libraries like jQuery and AlpineJS, and integrates analytics tools such as Google Tag Manager and Azure Application Insights. Performance is moderate with some asynchronous script loading and deferred execution. The site is mobile-optimized with responsive design and accessibility tools like Monsido and Google Translate support multiple languages. However, the absence of some security headers and incomplete WHOIS data indicate areas for technical improvement. The site architecture supports dynamic content such as news, events, and public engagement portals, reflecting a well-maintained infrastructure suitable for a government entity.
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 fayetteville-ar.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 fayetteville-ar.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.