Skip to main content

Security report for ottawa.place

ottawa.place · Technology · Canada

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

Security score

58/100

Risk levelMedium

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

ottawa.place is a small, community-focused Mastodon instance serving residents of Ottawa, Gatineau, and surrounding regions. It operates on the Hometown fork of Mastodon, emphasizing local community engagement and decentralized social networking. The platform is volunteer-administered and openly communicates its moderation policies and data residency practices, hosting user data primarily in Canadian data centers. The website content is bilingual and designed to foster a safe and inclusive environment for its users. Technically, the site leverages modern web technologies including JavaScript, HTML5, and CSS3, running on a Mastodon Hometown fork platform. Hosting is provided by OVH in Montreal and AWS Canada, ensuring data locality. The site demonstrates moderate performance and good mobile optimization, though accessibility and SEO features are basic. No major technical vulnerabilities or security issues are evident from the content and scripts. Security posture is solid with HTTPS enforced and clear anti-harassment policies. However, the absence of a formal security policy, vulnerability disclosure mechanism, and cookie consent banner indicates areas for improvement in compliance and transparency. The WHOIS data is unavailable due to TLD restrictions, but the site’s transparency and community focus support its legitimacy. Overall, ottawa.place presents a trustworthy and well-maintained community platform with room to enhance privacy compliance and formal security documentation. Strategically, ottawa.place should prioritize implementing cookie consent mechanisms, publishing terms of service, and establishing a vulnerability disclosure policy to strengthen user trust and regulatory compliance. Enhancing accessibility and SEO would improve user experience and discoverability. Continued transparency and community engagement will support sustainable growth and security maturity.

Scanned

This is an earlier scan of ottawa.place. View the latest report

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

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

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

This scan found 24 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
52
Security headers
65
Email security
60
DNS health
75
Network security
40
GDPR outside view
53
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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention ottawa.place, from OffSeq Breach.

No leaked records found

Breach holds no records for ottawa.place right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Brand lookalikes

Add-on

Domains that imitate ottawa.place and could be used for phishing or spoofed email, tracked in OffSeq Breach.

Tracked
10
Registered
10
Resolving
10
High or critical
0

Last checked 2026-06-19

Masked preview

  • xn•••••••••••.placeLowhomoglyph
  • xn•••••••••••••••.placeLowhomoglyph
  • xn•••••••••••.placeLowhomoglyph

See the full lookalike list

A one-off add-on that lists up to 20 of the highest-risk lookalikes of ottawa.place with registration, mail-server, certificate and DNS signals.

Select it in the checkout above.

Lookalike data refreshes continuously. Monitoring on Breach alerts you when a variant is registered, gains a mail server or starts serving HTTPS.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

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

Business context

Business profile

ottawa.place occupies a niche market as a localized Mastodon instance targeting the Ottawa region, differentiating itself by focusing on local community needs and bilingual support. Its business model is community-driven and volunteer-based, relying on open-source software and transparent administration. The platform’s competitive advantage lies in its regional focus and commitment to safe, harassment-free social networking. Revenue streams are not explicit, suggesting a non-commercial or donation-supported model. The target customer segment includes residents interested in decentralized social media alternatives. Growth indicators include active user count (~100 monthly active users) and ongoing translation efforts. The partnership ecosystem includes open-source Mastodon and Hometown communities, with no commercial partners identified. Strategic observations highlight the importance of maintaining data residency in Canada and fostering community trust through clear policies and moderation.

Security posture

The security maturity of ottawa.place is moderate to good. HTTPS is enforced, and the platform has clear policies against harassment and hate speech, with moderation powers defined. Data residency in Canadian data centers and encrypted backups on AWS indicate sound data protection practices. However, the absence of a published security policy, incident response plan, or vulnerability disclosure process limits transparency and formal readiness. No security headers were explicitly detected in the provided data, suggesting potential for improvement. The lack of cookie consent and GDPR compliance indicators may expose the platform to regulatory risks. Overall, the security culture appears community-oriented but would benefit from formalizing policies and enhancing compliance measures to reduce risk and improve user confidence.

Recommendations

  1. Implement a cookie consent mechanism to comply with privacy regulations and enhance user trust.
  2. Publish clear terms of service and a formal security policy outlining user rights and platform responsibilities.
  3. Establish and publicize a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  4. Enhance accessibility features to improve inclusivity and meet web standards.
  5. Regularly review and update security headers and perform security audits to identify and mitigate vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
ottawa.place
Description
Mastodon instance for residents of Ottawa, Gatineau, and surrounding regions. Decentralized social media powered by Mastodon with a focus on local communities.
Key services
Decentralized social networking, Local community engagement, User content hosting and federation
Content quality
good
Branding
consistent

Technology

Stack
Mastodon, Hometown fork, JavaScript, HTML5, CSS3
Frameworks
Hometown fork of Mastodon
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • User harassment reporting mechanisms
  • Moderation policies for harassment and hate speech

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a Mastodon instance focused on local Ottawa community.
  2. Content is bilingual (English and French) with ongoing translation efforts.
  3. No WHOIS registrar or domain creation data available due to TLD restrictions.
  4. No cookie consent mechanism detected, which may impact GDPR compliance.
  5. No explicit security.txt or vulnerability disclosure policy found.
  6. Moderation and anti-harassment policies are clearly stated.
  7. Hosting is located in Canada with data residency considerations.
  8. No phone numbers or physical addresses provided.
  9. No advertising or tracking technologies detected.
Technical notes

Notes

The website is built on the Mastodon Hometown fork platform, utilizing modern web technologies such as JavaScript, HTML5, and CSS3. Hosting is provided by OVH in Montreal and AWS Canada, ensuring data locality and redundancy. The site demonstrates moderate performance with good mobile optimization but basic accessibility and SEO features. No CMS is detected, indicating a custom or specialized platform. The use of open-source software and transparent versioning (v4.2.10+hometown-1.1.1) reflects a commitment to maintainability and community standards. Technical risks include the lack of visible security headers and absence of formal compliance mechanisms, which could impact security posture and regulatory adherence. Opportunities exist to modernize accessibility and SEO implementations and to formalize security and privacy 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

Earlier scans of this domain

  1. 58/100Medium31 findingsView report
Reviews of this site

Share your experience with ottawa.place. 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 ottawa.place.

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.