Skip to main content

Security report for osm.town

OSM Town · Technology · N/a

Medium risk. 5 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

69/100

Risk levelMedium

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

OSM Town operates as a specialized Mastodon server catering to the OpenStreetMap community, providing a decentralized social networking platform within the Fediverse. It is a small-scale, community-driven initiative supported financially by the OpenStreetMap Foundation, positioning itself as a niche player focused on geographic and mapping enthusiasts. The website offers Mastodon-based social features with a clear focus on community engagement and open collaboration. Technically, the site leverages modern web technologies including React and the Mastodon platform version 4.4.1, ensuring a contemporary user experience with mobile optimization and moderate performance. The infrastructure supports WebSocket streaming for real-time updates, indicating a well-maintained technical environment. However, some standard security headers appear to be missing, and there is no visible cookie consent mechanism, which could be improved for better privacy compliance. From a security perspective, the site enforces HTTPS and uses WebSocket Secure (wss) for streaming, which is positive. The absence of exposed sensitive data and lack of detected vulnerabilities contribute to a moderate security posture. The WHOIS data is unavailable due to privacy or query failure, but the presence of funding from a reputable foundation and visible admin contact enhance trust. Overall, the site is safe, with no adult or questionable content detected. The overall risk is low given the community nature and technical setup, but improvements in privacy compliance, security headers, and published security policies would strengthen the posture. Strategic recommendations include implementing security headers, adding cookie consent, and publishing incident response contacts to enhance trust and compliance.

Scanned

This is an earlier scan of osm.town. View the latest report

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

  2. 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 384-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

  3. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • High

      Weak SPF Policy

      SPF record has permissive policy allowing any server to send email

      What to do: Use -all or ~all qualifier for better email security

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

Keep watching osm.town

This scan found 22 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
52
Security headers
80
Email security
70
DNS health
55
Network security
100
GDPR outside view
58
Average
69

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

OSM Town serves a niche market of OpenStreetMap contributors and Fediverse users, leveraging a community-driven business model supported by a non-profit foundation. Its competitive advantage lies in its specialized focus and integration with the Fediverse social network, offering decentralized social media tailored to mapping enthusiasts. Revenue streams are likely limited or non-commercial, focusing on community funding and donations. The target audience is geographically and technically savvy users interested in open mapping and social networking without ads or algorithms. Growth indicators include active user counts (~281 monthly active users) and ongoing platform updates. Partnerships with the OpenStreetMap Foundation and Mastodon project reinforce credibility and ecosystem integration. Operationally, the server is small but consistent in branding and community engagement.

Security posture

The security maturity of OSM Town is moderate. HTTPS and secure WebSocket connections are in place, ensuring encrypted communications. However, the lack of visible security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options indicates room for improvement. No explicit security or incident response policies are published, and no contact channels for security incidents or abuse are visible. Privacy compliance is partial, with a privacy policy present but no cookie consent mechanism detected. The absence of WHOIS transparency is typical for privacy reasons and does not raise immediate red flags. Overall, the site demonstrates basic security hygiene but would benefit from enhanced policies, headers, and transparency to improve trust and compliance.

Recommendations

  1. Implement comprehensive security headers including CSP, HSTS, and X-Frame-Options to mitigate common web attacks.
  2. Add a cookie consent banner or mechanism to comply with GDPR and enhance user privacy transparency.
  3. Publish a clear security policy and incident response contact information to improve trust and readiness.
  4. Enhance accessibility features and SEO optimization for better user experience and discoverability.
  5. Regularly audit and update dependencies and libraries to avoid potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
OSM Town
Description
An independent, community of OpenStreetMap people on the Fediverse/Mastodon. Funding graciously provided by the OpenStreetMap Foundation.
Key services
Mastodon social networking, Community engagement for OpenStreetMap users
Content quality
good
Branding
consistent

Technology

Stack
Mastodon 4.4.1, React, JavaScript ES Modules, CSS, WebSockets
Frameworks
Mastodon, React
Platforms
Fediverse
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
70/100
Good practices seen
  • HTTPS enforced (implied by wss:// streaming API URL)

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 dedicated to OpenStreetMap community
  2. Content is accessible and not blocked by WAF
  3. No contact emails or phone numbers publicly listed
  4. Privacy policy present but no cookie consent mechanism detected
  5. No terms of service or security policy pages found
  6. No visible security headers in HTML source
  7. Modern tech stack with React and Mastodon platform
  8. No advertising or tracking scripts detected
  9. No adult or questionable content detected
Technical notes

Notes

The website is built on the Mastodon social networking platform version 4.4.1, utilizing React and modern JavaScript ES modules for frontend interactivity. The presence of WebSocket streaming endpoints indicates real-time data capabilities. The site uses standard favicon and apple-touch-icon assets for cross-device compatibility. DNS prefetching for cdn.masto.host suggests use of external content delivery networks for media. The HTML is well-structured with meta tags for viewport and theme color, supporting mobile responsiveness. However, no CMS is detected, and hosting provider details are not disclosed. Performance is moderate with no obvious blocking scripts or heavy assets. Accessibility is basic but could be improved with ARIA roles and better keyboard navigation support.
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. 74/100Medium26 findingsView report
Reviews of this site

Share your experience with osm.town. 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 osm.town.

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.