Skip to main content

Security report for pages.gay

besties · Technology · Iceland

High risk. 11 critical or high findings in Email security, Network security and 3 other checks.

Security score

38/100

Risk levelHigh

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

pages.gay is a small technology startup offering a niche service for hosting static websites quickly and easily, tightly integrated with the git.gay source code repository platform. The service targets developers and users who want to deploy static sites with minimal setup, leveraging open source software and git repositories. The website is modern, built with SvelteKit, and uses Cloudflare for DNS hosting, providing fast performance and good mobile optimization. However, the site lacks formal privacy, cookie, and terms of service policies, and does not provide contact information, which limits trust and compliance. Security posture is decent with HTTPS and domain transfer protection, but could be improved by enabling DNSSEC and adding security headers. No analytics or advertising tools are present, indicating minimal user tracking.

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

11 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. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: Redis

      Port 6379 (Redis) is publicly accessible - Redis - In-memory database

      What to do: Immediately restrict access to Redis using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

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

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

Keep watching pages.gay

This scan found 29 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
52
Security headers
15
Email security
40
DNS health
70
Network security
0
GDPR outside view
50
Average
38

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 · found on this site
  • 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 operates in the technology sector, focusing on developer tools and static site hosting. Its open source nature and integration with git.gay position it as a community-driven project with a lean business model. The domain is newly registered in 2023 and privacy protected, which is typical for small startups. The lack of contact details and formal policies suggests early-stage maturity. The project benefits from partnerships with git.gay and uses Cloudflare DNS services. Growth potential depends on adoption by developers seeking simple static hosting solutions. The open source code availability supports transparency and community trust.

Security posture

The website enforces HTTPS and uses clientTransferProhibited status to prevent unauthorized domain transfers, which are positive security measures. However, the absence of DNSSEC and security headers such as Content Security Policy or HSTS reduces defense in depth. No vulnerability disclosures or incident response contacts are published, limiting transparency in security management. The use of WHOIS privacy protection is justified given the small scale and nature of the project. Overall, the security posture is moderate but could be enhanced with additional best practices and formal policies.

Recommendations

  1. Enable DNSSEC to improve DNS security and prevent spoofing.
  2. Implement and publish a comprehensive privacy policy and cookie policy to enhance compliance and user trust.
  3. Add standard security headers including Content Security Policy, HSTS, and X-Frame-Options to strengthen security posture.
  4. Provide clear contact information including security incident response contacts to improve transparency and readiness.
  5. Consider publishing a vulnerability disclosure policy or security.txt file to encourage responsible reporting and improve security culture.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
besties
Description
host a static site for your project in minutes, all from the comfort of a source code repository.
Key services
static site hosting, integration with git.gay repositories, custom domain support
Content quality
good
Branding
consistent

Technology

Stack
SvelteKit, JavaScript, CSS, Cloudflare DNS
Frameworks
SvelteKit
Platforms
git.gay
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Domain status clientTransferProhibited
  • Use of privacy protection in WHOIS

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 a niche static site hosting service integrated with git.gay
  2. No privacy, cookie, or terms policies found
  3. No contact emails or phone numbers provided
  4. Open source code is publicly available
  5. Modern tech stack with SvelteKit and Cloudflare DNS
  6. Good mobile optimization and SEO metadata present
  7. No security headers detected, DNSSEC not enabled
  8. No analytics or tracking scripts detected
  9. No advertising or marketing tools present
  10. WHOIS privacy protection used, domain is new and legitimate
Technical notes

Notes

The website is built using modern web technologies including SvelteKit and JavaScript, with CSS for styling. It leverages Cloudflare for DNS hosting but does not enable DNSSEC. The site is well-structured with proper meta tags for SEO and Open Graph for social sharing. Performance is fast and mobile optimization is good. Accessibility is basic but acceptable. No CMS or third-party analytics/tracking scripts are detected, indicating a lightweight and privacy-conscious implementation. The site could benefit from adding accessibility enhancements and security headers to reduce technical risks.
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 pages.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 pages.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.