Skip to main content

Security report for h2.gay

Private by Design, LLC · Technology · United States

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

Security score

67/100

Risk levelMedium

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

The website h2.gay is a personal site operated by an individual known as Hydrogen, serving as a hub for personal internet services such as XMPP and a Git forge. The site is not commercial and targets internet users interested in personal blogs and technology hobbyist content. The domain is recently registered and privacy-protected, consistent with the personal nature of the site. Technically, the site uses nginx and hosts services including XMPP and Git. The hosting is in a datacenter with stable infrastructure. The site has basic design and SEO features, with moderate performance and basic mobile optimization. No CMS or advanced frameworks are detected. From a security perspective, the site lacks published privacy, cookie, or security policies and does not implement DNSSEC or security headers. The domain status flags clientTransferProhibited and clientDeleteProhibited provide some protection. No vulnerabilities or exposed sensitive data were detected. The site is accessible without WAF blocking. Overall, the site is low risk with no adult or explicit content. Recommendations include adding privacy and cookie policies, enabling DNSSEC, implementing security headers, and publishing incident response contacts to improve security posture and compliance.

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

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

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

Keep watching h2.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
15
Email security
73
DNS health
90
Network security
100
GDPR outside view
50
Average
67

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 site operates as a personal presence rather than a commercial business, with no revenue streams or market positioning. The owner uses privacy-focused registration and hosting services, indicating a preference for privacy and control. The site links to partner domains greatsword.xyz and fsky.io, which may be related personal or community projects. The business model is hobbyist and self-hosted, targeting a niche audience of internet and technology enthusiasts. Growth indicators and partnerships are minimal, consistent with a personal site.

Security posture

The security maturity level is basic. The domain uses registrar locks to prevent unauthorized transfers or deletions but lacks DNSSEC and security headers. No privacy or security policies are published, and no incident response contacts are provided. The site does not appear to collect user data or use tracking, reducing privacy risks. There are no visible vulnerabilities or exposed credentials. Compliance with GDPR or other regulations is not demonstrated. Overall, the security posture is adequate for a personal site but could be improved with standard best practices.

Recommendations

  1. Enable DNSSEC to enhance DNS security and prevent spoofing.
  2. Publish a clear privacy policy and cookie policy to improve transparency and compliance.
  3. Implement security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Use HTTPS site-wide if not already enforced and verify SSL configuration.
  5. Add incident response contact information and consider a security policy page.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Private by Design, LLC
Description
Personal website of an individual named Hydrogen, hosting various internet-related services including XMPP and a Git forge. The site serves as a personal hub rather than a commercial business.
Key services
XMPP hosting, Personal blog, Git forge hosting
Content quality
basic
Branding
moderate

Technology

Stack
nginx, XMPP, Git forge
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
50/100
Good practices seen
  • Domain status includes clientTransferProhibited and clientDeleteProhibited

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a personal site of an individual named Hydrogen.
  2. No privacy, cookie, or terms of service policies found.
  3. Contact information limited to email and XMPP address.
  4. No commercial or business-related content detected.
  5. No security policies or incident response information published.
  6. No analytics or advertising detected.
  7. Website content is accessible and not blocked by WAF.
  8. WHOIS data shows domain is recently registered and privacy-protected by a known registrar.
  9. Site uses nginx and hosts XMPP and Git forge services.
  10. No explicit or adult content detected.
Technical notes

Notes

The website is hosted on nginx in a datacenter environment with stable infrastructure. The tech stack includes XMPP and a Git forge, indicating some self-hosted services. The site uses basic HTML and CSS with no detected CMS or frameworks. Performance is moderate with basic mobile and accessibility features. SEO is minimal but includes meta description and favicon. There is no evidence of modern JavaScript frameworks or analytics tools. The site could benefit from modernization and improved technical SEO and accessibility.
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 h2.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 h2.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.