Skip to main content

Security report for waverlyia.com

City of Waverly · Government · United States

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

Security score

58/100

Risk levelMedium

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

The City of Waverly's official website serves as a portal for residents and visitors to access information about city departments and services. The site is positioned as a local government resource, providing details on public works, leisure services, economic development, and other municipal functions. The target audience primarily includes local residents, businesses, and visitors seeking city-related information. The business model is that of a government entity focused on community service rather than commercial revenue generation. Technically, the website employs a traditional web stack with jQuery 1.7.2, Google Analytics, Microsoft Clarity, and various UI libraries such as FancyBox and Owl Carousel. The site demonstrates moderate performance and good mobile responsiveness but lacks modern frameworks or CMS indications. Accessibility and SEO optimizations are basic, with room for improvement. From a security perspective, the site lacks visible security headers and privacy compliance documentation such as privacy or cookie policies. The use of an outdated jQuery version may expose the site to vulnerabilities. The absence of WHOIS data raises questions about domain registration legitimacy, although the site content and branding strongly suggest a legitimate municipal government presence. Overall, the website is functional and professional but requires enhancements in security posture, privacy compliance, and domain legitimacy transparency to improve trust and resilience against threats.

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

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

    • 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

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

Keep watching waverlyia.com

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. 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
15
Email security
75
DNS health
75
Network security
100
GDPR outside view
35
Average
58

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 City of Waverly operates as a municipal government entity providing essential public services to its community. Its market position is that of a local authority with a focus on transparency and accessibility of city services. The website supports this by offering detailed department information and community resources. Revenue streams are typical of government funding rather than commercial sales. The partnership ecosystem is not explicitly detailed on the site, and no subsidiary or parent company relationships are evident. Growth indicators are not discernible from the website content. Strategic observations suggest a need for modernization in digital presence and compliance to meet evolving regulatory and security standards.

Security posture

The current security maturity level of the City of Waverly's website is basic. Key vulnerabilities include the use of outdated JavaScript libraries, lack of security headers, and absence of documented privacy and cookie policies. There is no evidence of incident response contact channels or security frameworks in place. Compliance gaps with GDPR or similar regulations are apparent due to missing privacy documentation. Data protection practices are unclear, and no vulnerability disclosure or security.txt files are present. The security culture appears minimal, likely reflecting limited resources typical of small municipal sites. Business impact of these gaps includes potential data privacy risks and reduced user trust.

Recommendations

  1. Implement HTTPS with strong SSL/TLS configuration and enforce HSTS.
  2. Add comprehensive privacy and cookie policies to comply with GDPR and other regulations.
  3. Update all JavaScript libraries, especially jQuery, to latest secure versions.
  4. Deploy security headers such as Content-Security-Policy, X-Frame-Options, and X-XSS-Protection.
  5. Establish a security incident response contact and publish vulnerability disclosure guidelines.

Contact details published on the site

Registration number
Chamber of Commerce
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
City of Waverly
Description
Official website providing information about city departments, services, and community resources for Waverly, Iowa.
Key services
City departments information, Community services, Public works, Leisure services, Economic development, Police department, Public library
Content quality
good
Branding
consistent

Technology

Stack
jQuery 1.7.2, Google Analytics, Microsoft Clarity, Font Awesome 4.0.3, FancyBox 2.1.4, Owl Carousel 1.3.2
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
50/100

Analytics and tracking

Services
Google Analytics, Microsoft Clarity
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
Microsoft Clarity
Transparency
poor

Site quality

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

Key observations

  1. Website is a municipal government site for City of Waverly, Iowa.
  2. WHOIS data unavailable, domain registration status unclear.
  3. No privacy, cookie, or terms of service policies found on site.
  4. No explicit contact emails or phone numbers identified in the HTML content.
  5. Uses older jQuery version (1.7.2) which may have security risks.
  6. Includes Google Analytics and Microsoft Clarity for user tracking.
  7. No visible security headers or advanced security configurations detected.
  8. Site design is professional and consistent with government branding.
  9. No adult or questionable content detected.
  10. No WAF or blocking mechanisms detected.
Technical notes

Notes

The website uses a legacy technology stack with jQuery 1.7.2 and older versions of UI libraries. It loads fonts from Google Fonts and icons from Font Awesome 4.0.3. Analytics are implemented via Google Analytics and Microsoft Clarity, indicating moderate digital maturity. The site is mobile responsive with a consistent design but lacks modern CMS or framework usage. Performance is moderate, with potential improvements in load speed and accessibility. Technical debt is evident in outdated libraries and missing security best practices. Modernization opportunities include adopting a CMS, upgrading libraries, and enhancing SEO and accessibility features. Technical risks include exposure to known vulnerabilities in legacy scripts and lack of security headers.
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 waverlyia.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 waverlyia.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.