Skip to main content

Security report for is-quite.gay

Private by Design, LLC · Technology · United States

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

Security score

64/100

Risk levelMedium

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

The website is a niche, invite-only social platform branded as 'is-quite.gay', targeting individuals who identify as quite gay. It operates as a federated social media instance powered by the Misskey software, which supports ActivityPub federation. The platform is small with limited users and notes, emphasizing community exclusivity through invite codes. The business behind the domain is registered as Private by Design, LLC, a US-based entity, with the domain newly created in June 2024. The site content is consistent with its stated purpose and audience, with no adult or explicit content detected. Technically, the website uses modern web technologies including JavaScript ES modules, Vite bundler, and icon fonts. It leverages Cloudflare for DNS services but does not enable DNSSEC, which is a minor security gap. The site is served over HTTPS with domain status protections to prevent unauthorized changes. However, no security headers were detected in the HTML content, and no privacy or cookie policies are published, indicating room for compliance improvements. The site does not use advertising or tracking services, reflecting a privacy-conscious approach. From a security perspective, the platform shows a moderate security posture with HTTPS and domain protections but lacks published policies and security headers that would enhance trust and compliance. No vulnerabilities or exposed sensitive data were found. The absence of a privacy policy and cookie consent mechanism lowers the privacy compliance score. The domain registration details align well with the website content, supporting legitimacy. No WAF or blocking mechanisms were detected, allowing full content access. Overall, the website is a professionally presented, small-scale social platform with a clear niche audience and a solid technical foundation. Strategic recommendations include publishing privacy and cookie policies, enabling DNSSEC, adding security headers, and providing incident response contacts to improve security and compliance posture.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 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. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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 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 is-quite.gay

This scan found 19 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
75
Security headers
55
Email security
80
DNS health
85
Network security
40
GDPR outside view
50
Average
64

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 platform operates in the technology sector as a federated social media instance targeting the LGBTQ+ community, specifically those who identify as quite gay. Its invite-only model suggests a focus on community quality and exclusivity rather than mass adoption. The business model likely relies on community engagement rather than advertising or affiliate revenue, as no ads or tracking were detected. The company is small and newly founded, with no parent or subsidiary companies identified. The partnership with the Misskey software community and federation with other instances indicates a collaborative ecosystem approach. Growth potential depends on community expansion and federation network effects.

Security posture

The security maturity level is moderate. HTTPS is enforced, and domain registration includes protective status flags. However, the lack of DNSSEC, security headers, and published security or privacy policies indicates gaps in compliance and best practices. No incident response or abuse contact information is provided, which could hinder timely handling of security incidents. The absence of tracking and advertising reduces privacy risks. Overall, the platform demonstrates basic security hygiene but should enhance transparency and policy publication to meet GDPR and other regulatory standards.

Recommendations

  1. Publish a comprehensive privacy policy and cookie policy to improve GDPR compliance and user trust.
  2. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  3. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Provide clear incident response and abuse contact information to facilitate security issue reporting.
  5. Consider adding cookie consent mechanisms to comply with privacy regulations and improve transparency.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Private by Design, LLC
Description
for people who are quite gay
Key services
social networking, federated social media instance
Content quality
good
Branding
consistent

Technology

Stack
Misskey (ActivityPub software), Cloudflare DNS, JavaScript ES modules, Phosphor Icons, Vite bundler
Frameworks
Misskey
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • Domain status clientDeleteProhibited and clientTransferProhibited

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

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 invite-only social platform targeting a niche LGBTQ+ audience.
  2. Powered by Misskey, an ActivityPub federated social software.
  3. No privacy policy, cookie policy, or terms of service found on the site.
  4. Contact email is provided in meta JSON data but no visible contact form or phone number.
  5. No security headers detected in the HTML content.
  6. HTTPS is enabled and domain has protective status flags.
  7. No advertising or tracking scripts detected.
  8. Content is safe and appropriate for general audiences.
  9. Site uses modern JavaScript modules and icon fonts.
  10. Multiple federation partner instances linked and displayed.
Technical notes

Notes

The website uses a modern JavaScript-based front-end built with Vite and ES modules, leveraging the Misskey federated social platform software. It uses Cloudflare for DNS hosting but lacks DNSSEC. The site is served over HTTPS with a valid certificate. Performance is moderate with good mobile optimization and basic accessibility features. SEO optimization is basic with meta tags and Open Graph data present but no structured JSON-LD. No CMS is detected, indicating a custom or specialized platform. The site does not use third-party advertising or analytics, reducing external dependencies and privacy risks. Technical risks include missing DNSSEC and security headers, which should be addressed to improve resilience and 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

Reviews of this site

Share your experience with is-quite.gay. 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 is-quite.gay.

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.