Skip to main content

Security report for callmebymygender.top

Other · N/a

Medium risk. 9 critical or high findings in Email security, Security headers and 2 other checks.

Security score

58/100

Risk levelMedium

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

The website 'Call me by my gender' is a small educational platform focused on promoting respectful and inclusive language regarding gender identity. It provides detailed explanations on why certain terms like “female” or “male” can be problematic and offers alternatives for respectful communication. The site targets a general audience interested in gender inclusivity and language sensitivity. The business model is informational without commercial transactions or services. Technically, the site uses standard web technologies including HTML5, CSS3, JavaScript, and Google Fonts. It is hosted with DNS services provided by Cloudflare and uses Plausible Analytics for privacy-conscious visitor tracking. The site is mobile optimized with good SEO practices but lacks advanced accessibility features. Performance is moderate with no CMS detected. From a security perspective, the site uses HTTPS and has domain transfer protections enabled. However, it lacks DNSSEC and security headers such as Content-Security-Policy or X-Frame-Options, which are recommended for enhanced security. There are no privacy or cookie policies present, representing compliance gaps. The domain registration is recent (2023) and privacy protected, which is reasonable for this type of small educational site. Overall, the website is safe, professional, and trustworthy for its niche educational purpose. Key recommendations include adding privacy and cookie policies, implementing security headers, enabling DNSSEC, and considering a vulnerability disclosure policy to improve security posture and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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

9 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. 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';…

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

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

Keep watching callmebymygender.top

This scan found 26 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
65
Security headers
15
Email security
60
DNS health
70
Network security
100
GDPR outside view
35
Average
58

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 a niche educational resource focusing on gender inclusivity and respectful language use. It does not appear to be a commercial business but rather an informational platform created by an individual or small entity. The target audience includes individuals interested in gender issues, inclusivity, and language sensitivity. The site leverages external authoritative resources and images to support its content. There is no indication of revenue streams, partnerships, or subsidiaries. The business model is content-driven with a focus on awareness and education rather than monetization. The domain is newly registered, indicating a recent launch without extensive market presence.

Security posture

The website demonstrates a basic security posture with HTTPS enabled and domain transfer protection. However, it lacks DNSSEC, which could improve DNS security. No security headers are present in the HTML content, which exposes the site to potential risks such as clickjacking or MIME sniffing attacks. There is no evidence of a privacy policy or cookie consent mechanism, which are important for GDPR compliance. No incident response or vulnerability disclosure information is provided. The use of Plausible Analytics indicates a privacy-conscious approach to user tracking. Overall, the security maturity is moderate but could be improved with standard best practices and compliance documentation.

Recommendations

  1. Add a comprehensive privacy policy and cookie consent mechanism to improve GDPR compliance.
  2. Enable DNSSEC on the domain to enhance DNS security.
  3. Implement security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Consider publishing a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  5. Enhance accessibility features to improve inclusivity and SEO.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
An informational website discussing respectful language use related to gender identity, focusing on why certain terms like “female” or “male” can be problematic and suggesting alternatives.
Key services
educational content on gender and language inclusivity
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, Google Fonts, Cloudflare DNS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
60/100
Good practices seen
  • HTTPS enabled
  • Domain status clientTransferProhibited

Analytics and tracking

Services
Plausible Analytics
Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
plausible.avris.it
Transparency
basic

Site quality

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

Key observations

  1. Website is a small educational resource focused on gender-inclusive language.
  2. No privacy or cookie policies found, which is a compliance gap.
  3. No contact forms or phone numbers present; only an author email in meta tag.
  4. No security headers detected; DNSSEC not enabled.
  5. Uses Plausible Analytics for privacy-friendly tracking.
  6. No advertising or affiliate marketing detected.
  7. Content is safe and suitable for general audiences.
  8. Domain registration is recent and privacy protected but consistent with site purpose.
Technical notes

Notes

The website is built using standard web technologies without a detected CMS, indicating a custom or static site. It uses Google Fonts for typography and Plausible Analytics for lightweight tracking. Hosting appears to be supported by Cloudflare DNS services, but no CDN or advanced hosting platform is explicitly identified. The site is mobile responsive with a clean and consistent design. Performance is moderate with no obvious technical debt or errors. However, the absence of security headers and DNSSEC indicates areas for technical improvement. The site’s SEO is supported by proper meta tags and Open Graph data, enhancing social media sharing and search engine visibility.
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 callmebymygender.top. 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 callmebymygender.top.

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.