Skip to main content

Security report for pronouns.cc

pronouns.cc · Technology · N/a

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

52/100

Risk levelMedium

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

pronouns.cc is a small, community-driven technology project focused on providing a platform for users to create and share their preferred pronouns and names. The service supports multiple linked pronoun lists per user, catering to plural systems and other identity needs. The website is open source, licensed under GNU AGPL, and encourages community contributions. It is positioned as a niche alternative inspired by similar projects such as Pronouns.page and pronouny.xyz. Technically, the site uses modern frameworks like SvelteKit and Bootstrap, with Plausible Analytics for privacy-conscious user tracking. The site is performant, mobile-optimized, and well-structured, offering a good user experience.

Scanned

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

7 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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

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

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

Keep watching pronouns.cc

This scan found 24 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
75
Security headers
15
Email security
70
DNS health
60
Network security
40
GDPR outside view
53
Average
52

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 model appears to be a free, open source service supported by community donations, with no direct monetization evident. The target audience is broad, including anyone interested in sharing pronouns, especially plural systems and kin communities. The project maintains transparency through public code repositories and status pages. Partnerships or inspirations include similar pronoun sharing platforms. The lack of explicit company contact emails or phone numbers suggests a primarily volunteer or small team operation. Growth potential lies in community adoption and contributions.

Security posture

The website enforces HTTPS and does not expose sensitive data in its HTML content. However, it lacks several security headers that could enhance protection against common web attacks. There is no published security policy or incident response contact information, which limits transparency in handling security issues. The use of Plausible Analytics indicates a privacy-conscious approach, but the absence of a cookie consent mechanism is a compliance gap. Overall, the security posture is good for a small project but could be improved with formal policies and enhanced headers.

Recommendations

  1. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to improve defense-in-depth.
  2. Add a cookie consent banner or mechanism to comply with GDPR and other privacy regulations given the use of analytics.
  3. Publish a clear security policy and incident response contact information to improve transparency and trust.
  4. Consider adding a vulnerability disclosure policy or security.txt file to facilitate responsible reporting of security issues.
  5. Enhance accessibility features and conduct regular security audits to maintain and improve the security posture.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
pronouns.cc
Description
pronouns.cc is a service where users can create and share lists of their preferred names, pronouns, and terms. It supports multiple lists linked to a main profile, useful for plural systems and people who kin.
Key services
Create and share preferred pronouns and names, Multiple linked pronoun lists per user, Open source platform
Content quality
good
Branding
consistent

Technology

Stack
SvelteKit, Bootstrap, Plausible Analytics
Frameworks
SvelteKit
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • No visible vulnerable libraries

Analytics and tracking

Services
Plausible Analytics
Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
Plausible Analytics
Transparency
excellent

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is fully accessible with no blocking or WAF challenges
  2. Content is relevant and well-structured for the target audience
  3. Open source and community-driven project with transparent links
  4. No contact emails or phone numbers explicitly listed, only contact form via about page
  5. No cookie consent mechanism present despite use of analytics
  6. No explicit security or incident response policies published
Technical notes

Notes

The website is built using modern web technologies including SvelteKit and Bootstrap, ensuring a responsive and performant user experience. The use of modulepreload and deferred scripts indicates optimization for loading speed. The site is mobile-friendly and uses semantic HTML elements. No CMS is detected, suggesting a custom or framework-based build. Hosting details are not explicit but the presence of a status page and open source repository indicates a well-maintained infrastructure. There is room for improvement in accessibility and security header implementation.
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 pronouns.cc. 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 pronouns.cc.

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.