Skip to main content

Security report for quispamsis.ca

Town of Quispamsis · Government · Canada

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

Security score

73/100

Risk levelMedium

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

The Town of Quispamsis website serves as the official digital presence for the municipal government of Quispamsis, New Brunswick, Canada. It provides residents and visitors with access to essential public services such as transit information (KV Go), permits, council meetings, garbage and recycling, job postings, parks, and payment options. The site is well-structured with clear navigation and relevant content tailored to its local audience. The business model is that of a government entity focused on community service and information dissemination. Technically, the website employs a uSkinned Sitebuilder CMS platform with integrations including Google Analytics, Google reCAPTCHA, and Google Custom Search Engine. The site is mobile-optimized and accessible, with a cookie consent mechanism and privacy policy in place. Performance is moderate, and SEO practices are adequately implemented. However, some modern security headers are missing, and no explicit security or incident response policies are publicly disclosed. From a security perspective, the site uses HTTPS and basic security best practices but lacks advanced HTTP security headers and public incident response information. No vulnerabilities or exposed sensitive data were detected. The absence of WHOIS data for the domain is unusual for a government site and warrants further verification, though the website content and contact details appear legitimate. Overall, the website is a trustworthy and professional municipal portal with room for improvement in security transparency and WHOIS registration clarity. Strategic recommendations include enhancing security headers, publishing security policies, and verifying domain registration details to 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

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

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

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

Keep watching quispamsis.ca

This scan found 19 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
65
Email security
85
DNS health
85
Network security
100
GDPR outside view
53
Average
73

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 Town of Quispamsis holds a stable position as a local government authority serving its community with essential municipal services. Its competitive advantage lies in providing centralized, accessible information and services to residents and stakeholders. The business model is non-commercial, focusing on public service delivery and community engagement. Revenue streams are typical of municipal governments, including taxes and fees for permits and services. The target customer segments are local residents, businesses, and visitors. Growth indicators include digital engagement through events, news, and online payments. The partnership ecosystem includes integration with Google services and local GIS reporting tools. Strategic observations highlight the importance of maintaining digital trust and transparency to support community confidence.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforcement and use of Google reCAPTCHA to protect forms. However, the lack of several key HTTP security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options reduces its defense-in-depth posture. No public security or incident response policies were found, which limits transparency and preparedness perception. There are no visible vulnerabilities or exposed sensitive data. Compliance with privacy regulations is basic, with a privacy policy and cookie consent banner present but no explicit GDPR or NIS2 references. Incident response readiness and security culture indicators are not publicly documented. Overall, the security posture is adequate for a municipal website but could be improved with enhanced headers, policy disclosures, and vulnerability management.

Recommendations

  1. Implement comprehensive HTTP security headers including Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy to strengthen browser security.
  2. Publish a clear security policy and incident response plan on the website to improve transparency and preparedness.
  3. Conduct regular audits of third-party scripts and dependencies to identify and mitigate vulnerabilities.
  4. Enhance privacy compliance by explicitly addressing GDPR and other relevant regulations in the privacy policy.
  5. Verify and update WHOIS domain registration information to ensure legitimacy and trustworthiness.

Contact details published on the site

Addresses
Legal name
Town of Quispamsis
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Town of Quispamsis
Description
The official website for Town of Quispamsis.
Key services
KV Go transit information, Permits and building development, Council meetings information, Garbage and recycling services, Job postings, Parks and recreation facilities, Payments, Community events and news
Content quality
good
Branding
consistent

Technology

Stack
Google Analytics, Google reCAPTCHA, jQuery, Flickity, jQuery Cookie, Google Custom Search Engine
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • Cookie consent banner
  • Use of Google reCAPTCHA for forms

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
Google Adsense
Marketing tools
Google Custom Search Engine
Transparency
basic

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 Town of Quispamsis, Canada
  2. Content is well structured with clear navigation and relevant services
  3. No WHOIS data available, which is unusual for a government domain
  4. Uses HTTPS with Google Analytics and reCAPTCHA integration
  5. Cookie consent banner and privacy policy present indicating basic privacy compliance
  6. No visible security policy or incident response information publicly available
  7. No terms of service page detected
  8. No vulnerability disclosure or security.txt found
  9. Accessibility statement and contact info provided
  10. No suspicious or malicious content detected
Technical notes

Notes

The website is built on the uSkinned Sitebuilder CMS platform, leveraging modern web technologies including Google Analytics, Google reCAPTCHA, and Google Custom Search Engine for search functionality. The site is mobile responsive and optimized for accessibility, with a clean and consistent design. Performance is moderate, with lazy loading of images and asynchronous script loading. However, the absence of some security headers and limited hosting provider information indicate areas for technical improvement. The integration of multiple external domains for fonts, analytics, and social media is standard but requires ongoing monitoring for security and privacy compliance. Overall, the technical infrastructure supports the business needs but could benefit from modernization and enhanced security controls.
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 quispamsis.ca. 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 quispamsis.ca.

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.