Skip to main content

Security report for pronouns.page

Other · N/a

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

Security score

73/100

Risk levelMedium

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

Pronouns.page is a specialized educational platform providing usage examples of personal pronouns and promoting gender neutral language. It serves a general audience interested in linguistics and inclusivity, offering multilingual support through various language-specific subdomains. The website is positioned as a niche resource with a focus on accessibility and educational content rather than commercial services. Technically, the site is built on modern frameworks such as Nuxt.js and Vue.js, hosted on Cloudflare infrastructure with CDN support, ensuring good performance and mobile optimization. The use of privacy-conscious analytics tools like Plausible and error monitoring via Sentry indicates a mature approach to technical operations. Security posture is strong with HTTPS enforcement and standard security headers, though the absence of explicit privacy and cookie policies suggests room for improvement in compliance. Overall, the site is trustworthy and professional but would benefit from enhanced transparency and formal policies to strengthen user trust and regulatory adherence.

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 pronouns.page

This scan found 18 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
60
Email security
65
DNS health
90
Network security
100
GDPR outside view
50
Average
73

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 website operates as an educational and informational resource in the linguistics and inclusivity sector, targeting individuals seeking guidance on pronoun usage and gender neutral language. Its business model appears non-commercial, focusing on content dissemination and community support, as evidenced by links to social platforms and a Shopify storefront likely for merchandise. The multilingual approach broadens its reach internationally. The lack of detailed company information or certifications suggests a small-scale operation. The presence of multiple language domains indicates strategic internationalization. Partnerships or subsidiaries are not evident, and the site maintains a focused niche presence without overt commercial expansion.

Security posture

Pronouns.page demonstrates a solid security foundation with HTTPS, security headers, and no visible vulnerabilities or exposed sensitive data. The use of Sentry for error tracking enhances incident awareness. However, the absence of a published security policy, incident response contacts, or vulnerability disclosure mechanisms limits transparency and preparedness from a compliance and user assurance perspective. GDPR compliance indicators are minimal due to missing privacy and cookie policies. The site’s security maturity is adequate for its informational role but could be improved by formalizing policies and response procedures.

Recommendations

  1. Publish a comprehensive privacy policy detailing data collection, usage, and user rights to improve GDPR compliance.
  2. Implement a cookie policy and consent mechanism to align with privacy regulations and enhance user trust.
  3. Add a terms of service page to clarify legal usage and responsibilities.
  4. Establish and publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Provide clear incident response contact information to improve transparency and readiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Usage examples of personal pronouns and gender neutral language.
Key services
providing usage examples of personal pronouns, supporting gender neutral language education
Content quality
good
Branding
consistent

Technology

Stack
Nuxt.js, Vue.js, Cloudflare Insights, Shopify (storefront token present), Plausible Analytics, Sentry
Frameworks
Nuxt.js, Vue.js
Platforms
Cloudflare
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Use of security headers
  • No exposed sensitive data in HTML
  • Use of Sentry for error monitoring

Analytics and tracking

Services
Plausible Analytics, Cloudflare Insights, Sentry
Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
Plausible Analytics, Cloudflare Insights, Sentry
Marketing tools
Shopify storefront token
Transparency
basic

Site quality

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

Key observations

  1. Website is an educational resource focused on personal pronouns and gender neutral language.
  2. No explicit privacy, cookie, or terms of service policies found on the main page.
  3. Contact emails are provided via mailto links but no phone numbers or physical addresses.
  4. Uses modern web technologies including Nuxt.js and Vue.js with Cloudflare hosting and CDN.
  5. Good security posture with HTTPS and security headers.
  6. Analytics usage is privacy-conscious with Plausible and Sentry.
  7. No adult or questionable content detected.
  8. No visible forms collecting user data on the main page.
  9. Multiple language versions linked, indicating internationalization focus.
Technical notes

Notes

The website leverages a modern tech stack with Nuxt.js and Vue.js frameworks, ensuring a performant and responsive user experience. Hosting on Cloudflare with Cloudfront CDN optimizes delivery and security. The integration of Plausible Analytics and Sentry indicates a focus on lightweight, privacy-respecting analytics and robust error monitoring. The site is well-structured with appropriate meta tags for SEO and accessibility features. No CMS is explicitly detected, suggesting a custom or static site generation approach. Performance is fast, and mobile optimization is good. Opportunities exist to enhance compliance-related technical implementations such as cookie consent management.
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.page. 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.page.

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.