Skip to main content

Security report for beige.party

beige.party · Technology · Iceland

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

Security score

72/100

Risk levelMedium

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

beige.party is an independent Mastodon server providing a social networking platform within the Fediverse. It targets users interested in decentralized social media and offers features such as profile directories and content exploration. The platform is relatively new, founded in 2022, and operates with a small user base. Technically, it leverages the Mastodon open-source software, modern JavaScript frameworks, and WebSocket streaming for real-time updates. The website is mobile-optimized with a good user experience and consistent branding. Security posture is moderate with domain privacy protection and clientTransferProhibited status, but lacks advanced security headers and DNSSEC. Privacy compliance is basic with a privacy policy present but no cookie consent mechanism or detailed GDPR compliance indicators. Overall, the platform is trustworthy for its niche audience but could improve in security and privacy transparency.

Scanned

This is an earlier scan of beige.party. 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

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

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

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
67
Security headers
75
Email security
70
DNS health
65
Network security
100
GDPR outside view
53
Average
72

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

The business operates as a small independent social media server within the decentralized Fediverse ecosystem. Its competitive advantage lies in community-driven content and privacy-conscious hosting. The business model is based on providing free social networking services without evident monetization or advertising. Target customers are privacy-aware social media users and Fediverse participants. Growth indicators include active user statistics and ongoing content activity. The platform integrates with other Fediverse nodes and open-source projects, fostering a collaborative ecosystem. Strategic observations suggest focusing on enhancing security, privacy compliance, and user trust to strengthen market position.

Security posture

The security maturity level is moderate. The domain uses privacy protection and has clientTransferProhibited status, reducing domain hijacking risk. However, DNSSEC is not enabled, and no security headers are detected in the HTML content, which could expose users to certain web attacks. No exposed sensitive data or vulnerable libraries were identified. The platform lacks explicit incident response or security policies. Compliance gaps exist regarding GDPR and cookie consent. Incident response readiness and security culture indicators are not evident from the content. Overall, the platform should prioritize implementing security headers, DNSSEC, and transparent security policies to improve its security posture.

Recommendations

  1. Enable DNSSEC to protect against DNS spoofing and improve domain security.
  2. Implement standard security headers such as Content Security Policy, HSTS, and X-Frame-Options.
  3. Develop and publish comprehensive privacy and security policies including GDPR compliance details.
  4. Add a cookie consent mechanism to comply with privacy regulations and enhance user trust.
  5. Establish clear incident response procedures and provide dedicated security contact channels.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
beige.party
Description
A home to friendly weirdos. The Grey Gardens of the Fediverse (but beige). Occasionally graphically cacographic. Definitely probably not a cult (though you'll never be 100% sure). Beige-bless 🙏
Key services
Mastodon social networking, Profile directory, Content exploration
Content quality
good
Branding
consistent

Technology

Stack
Mastodon 4.3.8, JavaScript, SVG icons, WebSockets (wss://beige.party)
Frameworks
Mastodon, React (likely)
Platforms
Fediverse, Mastodon
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • Domain status clientTransferProhibited
  • Use of privacy protection in WHOIS

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 an independent Mastodon social media server
  2. Content is user-generated social posts with diverse topics
  3. No explicit security or privacy policies beyond basic privacy policy found
  4. No cookie consent or terms of service pages detected
  5. WHOIS privacy protection used, common for small social platforms
  6. No signs of WAF or content blocking
  7. No advertising or tracking detected in HTML content
  8. Good mobile optimization and basic accessibility features
Technical notes

Notes

The website is built on the Mastodon platform version 4.3.8, utilizing modern JavaScript and React-based components. It uses WebSocket streaming for real-time content updates. The site is mobile-optimized and includes accessibility features, though basic. Performance is moderate with chunked CSS and JS assets. Hosting provider details are limited, but domain registrar is NameCheap with privacy protection. No CMS detected beyond Mastodon. Technical risks include lack of DNSSEC and missing security headers. Opportunities exist to modernize security practices and improve SEO and accessibility compliance.
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. 75/100Medium24 findingsView report
Reviews of this site

Share your experience with beige.party. 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 beige.party.

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.