Skip to main content

Security report for neos.social

Neos Foundation e.V. · Technology · Germany

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

Security score

70/100

Risk levelMedium

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

Neos.social is a niche Mastodon instance operated by Neos Foundation e.V., focused on providing a social networking platform for discussions related to Neos and connecting users to the broader Fediverse. The platform leverages the open-source Mastodon software (version 4.4.1) and modern web technologies such as React and JavaScript ES modules, delivering a responsive and user-friendly experience. The website content is well-structured and relevant to its target audience, with a consistent branding approach and clear community focus. From a technical perspective, the site employs modern frameworks and technologies, including WebSockets for real-time communication, and uses CDN resources for media delivery. However, some security best practices such as enabling DNSSEC and implementing security headers are not observed, which could be improved to enhance the overall security posture. The absence of cookie consent mechanisms and limited privacy compliance indicators suggest room for improvement in regulatory adherence. Security-wise, the domain registration is transparent and consistent with the organization's identity, enhancing trustworthiness. The domain is protected against unauthorized transfers, but lacks DNSSEC. No critical vulnerabilities or exposed sensitive data were detected in the analyzed content. Overall, the site maintains a moderate security posture but would benefit from enhanced security policies and compliance measures. Strategically, Neos.social serves a small but focused community, positioning itself as a specialized social platform within the Fediverse ecosystem. The lack of commercial advertising and tracking aligns with privacy-conscious user expectations. To strengthen its market position and trust, the platform should consider publishing more comprehensive privacy and security policies, implementing cookie consent, and improving technical security controls.

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

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

Keep watching neos.social

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
75
Email security
60
DNS health
75
Network security
100
GDPR outside view
58
Average
70

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

Neos Foundation e.V. operates neos.social as a community-driven Mastodon instance targeting users interested in Neos-related topics and the Fediverse. The business model is non-commercial, focusing on social networking and community engagement rather than monetization. The platform's competitive advantage lies in its niche focus and alignment with privacy and open-source principles. Growth indicators include active user engagement (17 active users in last 30 days) and integration with federated social networks. Partnerships with Mastodon and use of open-source software reduce operational costs and increase transparency. The organization is based in Germany, founded in 2019, and maintains consistent domain registration information. The ecosystem is primarily community and technology-focused, with no evident commercial subsidiaries or partners.

Security posture

The security maturity of neos.social is moderate. The domain uses HTTPS and has clientTransferProhibited status to prevent unauthorized domain transfers, which are positive indicators. However, DNSSEC is not enabled, and no security headers were detected in the analyzed content, which are gaps in best practices. There is no public security policy or incident response information available, and no contact channels for security incidents are provided. Privacy compliance is limited, with no cookie consent mechanism and no GDPR compliance indicators beyond a basic privacy policy. No vulnerabilities or exposed sensitive data were found, but the lack of explicit security controls and policies could pose risks. The platform would benefit from implementing security headers, DNSSEC, and publishing incident response and security policies to improve trust and compliance.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish a comprehensive security policy and incident response plan accessible to users.
  4. Add cookie consent mechanisms to comply with GDPR and improve privacy compliance.
  5. Provide clear contact information for security incidents and data protection officer if applicable.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Neos Foundation e.V.
Description
This Mastodon instance serves as a platform for discussing Neos-related topics and as a connection to the Fediverse.
Key services
Social networking, Fediverse connectivity, Discussion platform for Neos-related topics
Content quality
good
Branding
consistent

Technology

Stack
Mastodon 4.4.1, React, JavaScript ES Modules, SVG icons, CSS with integrity hashes, WebSockets (wss://neos.social)
Frameworks
Mastodon, React
Platforms
Fediverse
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • Domain status clientTransferProhibited to prevent unauthorized transfers

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 Neos community discussions.
  2. Content is accessible with no blocking or WAF challenges.
  3. No explicit privacy or cookie consent mechanisms detected despite GDPR relevance.
  4. No visible contact emails or phone numbers on the explored page.
  5. Technical implementation uses modern JavaScript modules and React framework.
  6. No advertising or tracking services detected.
  7. WHOIS data is consistent and supports legitimacy.
  8. Security headers and DNSSEC are missing or not detected.
Technical notes

Notes

The website is built on Mastodon 4.4.1, utilizing React and modern JavaScript ES modules, which indicates a contemporary and modular technical stack. The use of CDN resources for media and assets supports performance optimization. The site is mobile optimized with responsive design and basic accessibility features. SEO optimization is basic but includes relevant meta tags and Open Graph data. The absence of CMS-specific indicators suggests a custom or Mastodon-native content management approach. Performance is moderate, with no evident blocking or errors. Technical risks include missing DNSSEC and security headers, which could be addressed to reduce attack surface and improve security posture.
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 neos.social. 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 neos.social.

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.