Skip to main content

Security report for tech.lgbt

tech.lgbt Moderators · Technology · Iceland

Medium risk. 3 critical or high findings in GDPR outside view and DNS health.

Security score

65/100

Risk levelMedium

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

tech.lgbt operates as a niche Mastodon instance providing a federated social networking platform primarily for LGBTQIA+ individuals and allies interested in technology and academic topics. The platform fosters community engagement through posts, hashtags, and news aggregation from across the fediverse, positioning itself as a trusted space for marginalized identities within the tech sector. The website's content and user base reflect a focused community with approximately 2.7K active users, indicating a small but engaged audience. The business model centers on community-driven social networking without commercial advertising or tracking, emphasizing privacy and inclusivity. From a technical perspective, the site leverages modern web technologies including React and JavaScript ES modules, hosted on DigitalOcean with domain registration via NameCheap. The platform runs Mastodon version 4.4.0-alpha.5+glitch, indicating active maintenance and use of open-source social networking software. The website demonstrates good mobile optimization and basic accessibility features, though SEO and performance optimizations are moderate. The absence of cookie consent mechanisms and some security headers suggests areas for improvement in compliance and security hardening. Security posture is solid with HTTPS enforced and no exposed sensitive data detected. However, the lack of DNSSEC and security headers such as CSP or HSTS represents potential vulnerabilities. The WHOIS data shows privacy protection for the domain registrant, which is justified given the community nature of the platform. No incident response or vulnerability disclosure policies are publicly available, which could be enhanced to improve trust and security readiness. Overall, tech.lgbt presents a professional, trustworthy, and community-focused platform with a strong emphasis on privacy and inclusivity. Strategic recommendations include enabling DNSSEC, implementing comprehensive security headers, adding cookie consent and vulnerability disclosure policies, and providing clearer contact information for security incidents. These steps would enhance compliance, security posture, and user trust, supporting sustainable growth and resilience in the federated social networking space.

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

3 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. 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 tech.lgbt

This scan found 20 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
95
Security headers
75
Email security
65
DNS health
55
Network security
40
GDPR outside view
58
Average
65

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

tech.lgbt occupies a specialized market niche as a Mastodon instance catering to LGBTQIA+ and tech-interested communities. Its competitive advantage lies in its focused audience and commitment to inclusivity and privacy. The platform operates on an open-source model, leveraging Mastodon's federated architecture to provide decentralized social networking without reliance on advertising revenue. Target customers are individuals seeking safe, ad-free social spaces aligned with marginalized identities and technology interests. Growth indicators include a stable active user base and ongoing software updates. The partnership ecosystem is limited but includes upstream Mastodon developers and hosting providers. Operationally, the platform emphasizes community moderation and privacy protection, reflecting strategic priorities around user safety and trust.

Security posture

The security maturity of tech.lgbt is moderate. HTTPS is enforced, and no sensitive data leaks are evident in the HTML content. The use of WHOIS privacy protection aligns with protecting administrator identities. However, the absence of DNSSEC and key security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options indicates gaps in defense-in-depth. No explicit security policy or incident response contacts are published, limiting transparency and preparedness for security events. Compliance with GDPR is implied through privacy policy presence and privacy protection, but cookie consent mechanisms are missing. The platform would benefit from formalizing vulnerability disclosure and incident response processes to enhance security culture and readiness. Overall, the security posture supports safe operation but requires enhancements to meet best practices and regulatory expectations.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement comprehensive HTTP security headers including CSP, HSTS, X-Frame-Options, and X-Content-Type-Options.
  3. Add a cookie consent banner and detailed cookie policy to comply with privacy regulations.
  4. Publish a vulnerability disclosure policy and security.txt file to facilitate responsible reporting.
  5. Provide clear incident response contact information to improve transparency and user trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
tech.lgbt Moderators
Description
We welcome all marginalized identities. This Mastodon instance is generally for folks who are LGBTQIA+ and Allies with an interest in tech work, academics, or technology in general.
Key services
Social networking, Federated Mastodon server, Profile directory, Content exploration (posts, hashtags, news)
Content quality
good
Branding
consistent

Technology

Stack
Mastodon 4.4.0-alpha.5+glitch, React, JavaScript ES Modules, CSS, DigitalOcean hosting, NameCheap registrar
Frameworks
React
Platforms
Mastodon (Fediverse)
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced (implied by wss:// streaming API)
  • No exposed sensitive data in HTML
  • Use of privacy protection in WHOIS

Analytics and tracking

Tracking level
minimal
Privacy practices
good

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 social network instance focused on LGBTQIA+ and tech communities.
  2. Content is user-generated posts aggregated from the fediverse.
  3. No direct company contact emails or phone numbers found.
  4. Privacy and terms of service pages are present and linked.
  5. No cookie consent banner or explicit cookie policy detected.
  6. No security.txt or vulnerability disclosure policy found.
  7. No explicit security policy or incident response contacts found.
  8. Website uses modern JavaScript modules and React framework.
  9. Hosting is on DigitalOcean with domain registered via NameCheap.
  10. No advertising or tracking scripts detected in the HTML.
Technical notes

Notes

The website is built on a modern technology stack featuring React and JavaScript ES modules, running Mastodon 4.4.0-alpha.5+glitch. Hosting is provided by DigitalOcean, with domain registration through NameCheap using privacy protection. The site includes responsive design and basic accessibility features, though SEO optimization is basic. Performance is moderate, with no major blocking issues detected. The absence of cookie consent and some security headers suggests technical debt in compliance and security hardening. The platform benefits from open-source software and active maintenance but should prioritize implementing security best practices and privacy compliance features to reduce operational risks and improve user experience.
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 tech.lgbt. 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 tech.lgbt.

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.