Skip to main content

Security report for ottawa.place

Technology · N/a

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 community-driven Mastodon instance serving residents of Ottawa, Gatineau, and surrounding regions. It provides a decentralized social networking platform leveraging Mastodon and the Hometown fork, targeting local users interested in federated social media. The platform is small in scale with approximately 88 active users, emphasizing community engagement without commercial advertising or tracking. The website content is bilingual and focuses on promoting local social connectivity within the fediverse ecosystem. Technically, the site uses modern web technologies including JavaScript ES modules and CSS, with a responsive design suitable for mobile users. The platform is hosted securely with HTTPS enforced, though lacks some advanced security headers and cookie consent mechanisms. Security posture is moderate with no visible vulnerabilities or exposed sensitive data. Privacy compliance is basic, with a privacy policy present but no cookie consent or terms of service pages. Business credibility is moderate given the clear administration presence and active user base, though contact information is not publicly disclosed. Overall, ottawa.place represents a legitimate, community-focused social platform with room for improvement in security and privacy transparency.

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

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 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
52
Security headers
65
Email security
60
DNS health
75
Network security
40
GDPR outside view
58
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 operates as a niche social networking service within the federated Mastodon ecosystem, targeting a geographically defined user base. Its competitive advantage lies in local community focus and open-source technology use. The business model is non-commercial, relying on community participation rather than monetization. The platform's ecosystem includes links to Mastodon and Hometown source code repositories, indicating transparency and open development. Growth indicators are limited due to small active user count. Partnership ecosystem is minimal with no identified commercial partners or subsidiaries. Strategic observations suggest the platform prioritizes privacy and decentralization, which aligns with the Mastodon ethos but limits commercial scalability. The absence of direct contact or business registration data suggests a volunteer or community-run operation rather than a formal corporate entity.

Security posture

The security maturity of ottawa.place is moderate. HTTPS is properly implemented ensuring encrypted communications. However, the absence of key security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options reduces protection against common web attacks like clickjacking and MIME sniffing. No evidence of vulnerable libraries or exposed sensitive data was found. The site lacks a published security policy or incident response contact, which limits transparency and preparedness for security incidents. Privacy compliance is partial; a privacy policy exists but cookie consent and GDPR compliance indicators are missing. The platform would benefit from enhanced security controls, formalized policies, and improved user privacy mechanisms to raise its security posture to a higher level.

Recommendations

  1. Implement and enforce security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web vulnerabilities.
  2. Add a cookie consent banner and detailed cookie policy to improve privacy compliance and user transparency.
  3. Publish terms of service and a dedicated security policy page to clarify user rights and security practices.
  4. Provide clear contact information for security incidents and general inquiries to enhance trust and incident response readiness.
  5. Regularly audit and update third-party libraries and dependencies to prevent vulnerabilities and maintain platform security.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Mastodon instance for residents of Ottawa, Gatineau, and surrounding regions. Instance de Mastodon pour les résidents d'Ottawa, de Gatineau et des régions avoisinantes.
Key services
Mastodon social networking, Profile directory, Live feeds
Content quality
good
Branding
consistent

Technology

Stack
Mastodon, Hometown (fork), JavaScript ES modules, CSS, HTML5
Frameworks
Mastodon, Hometown
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced

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
moderate

Key observations

  1. Website is a Mastodon instance targeting Ottawa and surrounding regions
  2. Content is bilingual (English and French) in description
  3. No direct contact emails or phone numbers found
  4. Privacy policy page exists but no cookie consent detected
  5. No terms of service or security policy pages found
  6. Uses modern JavaScript modules and Mastodon/Hometown frameworks
  7. No advertising or tracking scripts detected
  8. No security headers detected in HTML content
  9. HTTPS is enforced
  10. Active user count is low (88 active users)
Technical notes

Notes

The website is built on Mastodon with the Hometown fork, utilizing modern JavaScript ES modules and CSS for styling. The platform is web-based with responsive design elements for mobile optimization. Performance is moderate with no explicit indicators of slow loading or technical debt. SEO is basic with meta tags and Open Graph data present but no advanced structured data like JSON-LD. Accessibility features are minimal but present. Hosting provider details are not disclosed. The technical stack is appropriate for a community social platform but could be enhanced with improved accessibility and SEO practices. No CMS detected, as Mastodon is a custom platform. Overall, the technical implementation supports the platform's community focus but leaves room for modernization and 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

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.