Skip to main content

Security report for saintjohnpolice.ca

Saint John Police Force · Government · Canada

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

50/100

Risk levelMedium

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

The Saint John Police Force website serves as the official online presence for the municipal police department of Saint John, New Brunswick, Canada. It provides comprehensive information about the police force's services, community engagement initiatives, and contact channels. The site targets residents and visitors seeking public safety information and police services. The business model is public service, with a focus on law enforcement and community safety. The website is well-branded and consistent with government standards, reflecting a medium-sized organization founded in 2011. Technically, the website is built on WordPress using Elementor, leveraging modern web technologies such as jQuery and Font Awesome. The site demonstrates good mobile optimization and SEO practices, though performance is moderate. Hosting details are not explicitly disclosed, but DNS is managed via Constellix and the domain registrar is Rebel.ca Corp. The site lacks some advanced security headers and DNSSEC, which are recommended for enhanced security. From a security perspective, the site uses HTTPS and has domain transfer protections enabled, indicating a secure baseline. However, the absence of DNSSEC and security headers like Content-Security-Policy and HSTS reduces its security posture. No incident response or vulnerability disclosure policies are found, which could be improved. Privacy compliance is partial, with a privacy policy present but no cookie consent mechanism detected. Overall, the website is trustworthy and professional, with clear contact information and active social media links. The content is safe for general audiences with no adult or questionable material. Strategic recommendations include implementing DNSSEC, adding security headers, and introducing cookie consent to improve privacy compliance and security posture.

Scanned

NIS2 and GDPR posture

GDPR outside view
58/ 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

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

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

Keep watching saintjohnpolice.ca

This scan found 28 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
62
Security headers
15
Email security
70
DNS health
75
Network security
20
GDPR outside view
58
Average
50

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

Saint John Police Force operates as a government entity providing law enforcement and community safety services in Saint John, New Brunswick. Its market position is that of a local municipal police force with a stable presence since 2011. The organization offers a wide range of services including criminal investigations, patrol, community engagement, and victim services. The website supports public interaction through online reporting, tips submission, and information requests. The force maintains an active social media presence to engage with the community. The business model is non-commercial, focused on public safety and community trust. There is no indication of parent or subsidiary companies. The website content and structure reflect a mature organization with consistent branding and professional communication.

Security posture

The website demonstrates a basic to moderate security maturity level. HTTPS is enforced, and domain transfer restrictions are in place, which are positive indicators. However, the lack of DNSSEC and missing security headers such as Content-Security-Policy, X-Frame-Options, and HSTS represent gaps that could expose the site to certain attacks like DNS spoofing or clickjacking. No explicit incident response or vulnerability disclosure policies are published, which limits transparency and preparedness. Forms are present for user interaction but no explicit security measures (e.g., CAPTCHA, input validation) are visible in the HTML. Overall, the security posture is adequate for a government informational site but could be enhanced to meet higher standards and compliance requirements.

Recommendations

  1. Enable DNSSEC on the domain to protect against DNS spoofing and improve domain security.
  2. Implement key security headers including Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, and HSTS to harden the website against common web attacks.
  3. Introduce a cookie consent banner and cookie policy to comply with privacy regulations and improve user transparency.
  4. Publish an incident response and vulnerability disclosure policy to enhance security transparency and readiness.
  5. Conduct regular security audits of website forms and inputs to prevent injection attacks and ensure secure data handling.

Contact details published on the site

Addresses
Legal name
Saint John Police Force
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Saint John Police Force
Description
Saint John Police Force (SJPF) is committed to the safety and well-being of the city of Saint John.
Key services
Criminal investigations, Patrol services, Community engagement, Support services, Public safety communications
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Elementor, jQuery, Font Awesome, Constellix DNS
Frameworks
WordPress, Elementor
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
65/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited and clientUpdateProhibited domain status

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Marketing tools
Rank Math SEO, Elementor
Transparency
basic

Site quality

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

Key observations

  1. Website is professionally designed and maintained using WordPress and Elementor.
  2. Content is comprehensive for a municipal police force, including detailed service descriptions and community engagement.
  3. Contact information is clearly provided with multiple channels including email, phone, and physical address.
  4. No privacy or cookie policy banner detected, which is a minor compliance gap.
  5. Security headers and DNSSEC are missing, representing an area for improvement.
  6. No signs of malicious or suspicious content or domains.
  7. Social media presence is active and linked to official channels.
Technical notes

Notes

The website is built on a WordPress CMS platform with Elementor page builder, utilizing jQuery and Font Awesome libraries. DNS is managed by Constellix, and the domain registrar is Rebel.ca Corp. The site uses HTTPS with a valid SSL certificate, but DNSSEC is not enabled. The site loads external resources from trusted CDNs such as maxcdn.bootstrapcdn.com. Performance is moderate, with good mobile responsiveness and basic accessibility features. SEO is enhanced by the Rank Math plugin and structured data in JSON-LD format. There is room for improvement in security headers and privacy compliance. The technical infrastructure is stable but could benefit from modernization in security practices and performance optimization.
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 saintjohnpolice.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 saintjohnpolice.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.