Skip to main content

Security report for frequency.xyz

Frequency · Technology · N/a

Medium risk. 6 critical or high findings in Security headers and GDPR outside view.

Security score

69/100

Risk levelMedium

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

Frequency.xyz is a technology-focused website branded as "Frequency" with the tagline "Welcome to the People's Internet." The site appears to be a simple single-page application built with modern JavaScript frameworks, specifically SvelteKit, and hosted on GitHub Pages. It targets a technology-savvy audience interested in internet and privacy-related topics, though explicit business model details and market positioning are not provided. The site uses Matomo analytics and Klaro for cookie consent management, indicating a moderate level of privacy awareness. From a technical perspective, the website employs a modern tech stack with JavaScript and SvelteKit, and it is hosted on a reliable platform (GitHub Pages). Performance is fast with minimal resources loaded, but mobile optimization and accessibility are basic. SEO metadata is present but limited to Open Graph tags without structured data. The SSL certificate is valid but lacks advanced security features such as HSTS. Security posture is adequate with HTTPS enabled and no detected vulnerable cipher suites or subdomain takeover risks. However, the absence of security headers like HSTS and Content-Security-Policy reduces the overall security robustness. No privacy policy, terms of service, or contact information is provided, which impacts compliance and trust. Cookie consent is implemented properly via Klaro, requiring user consent before tracking. Overall, the website is functional and moderately secure but lacks comprehensive privacy and business transparency documentation. Strategic improvements in security headers, privacy disclosures, and contact information would enhance trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 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

6 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 frequency.xyz

This scan found 21 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
87
Security headers
15
Email security
85
DNS health
85
Network security
100
GDPR outside view
40
Average
69

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

Frequency.xyz operates in the technology sector with a focus on internet and privacy themes. The business model is not explicitly stated, but the use of Matomo analytics and Klaro consent management suggests a privacy-conscious approach possibly targeting users interested in decentralized or people-centric internet services. The site is small in scale, with no visible commercial transactions or detailed service offerings. The lack of contact information and legal documents limits the ability to assess market positioning or revenue streams. The partnership ecosystem is not evident from the data, and no subsidiaries or parent companies are identified. The site’s branding is consistent but minimalistic, indicating an early-stage or niche project rather than a large enterprise.

Security posture

The security maturity of frequency.xyz is moderate. HTTPS is enforced with a valid SSL certificate issued by a recognized authority, but the certificate validity period is short (about 3 months). No HSTS header is enabled, which is a missed opportunity to enforce strict transport security. The site lacks several recommended security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options. No vulnerabilities or exposed sensitive data were detected. Cookie consent is managed with Klaro, requiring explicit user consent before tracking, supporting GDPR compliance efforts. However, the absence of a privacy policy, terms of service, and security.txt file indicates gaps in formal security and privacy governance. Incident response contacts are not published, limiting transparency and readiness. Overall, the site is secure enough for informational purposes but requires enhancements for enterprise-grade security and compliance.

Recommendations

  1. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives to improve HTTPS enforcement.
  2. Publish a comprehensive privacy policy and terms of service to enhance legal compliance and user trust.
  3. Add security headers such as Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy to strengthen security posture.
  4. Create and publish a security.txt file to provide clear vulnerability disclosure and incident response contacts.
  5. Improve accessibility and SEO by adding structured data (JSON-LD) and enhancing mobile responsiveness.
Technical notes

Notes

The website is built using SvelteKit, a modern JavaScript framework, and is hosted on GitHub Pages, which provides reliable and scalable hosting. The site uses Matomo for analytics and Klaro for cookie consent management, indicating a privacy-focused technology stack. Performance is fast due to minimal resource loading, but the site lacks extensive content and interactive features. The HTML is valid and includes proper meta tags for Open Graph and Twitter cards, supporting social media sharing. However, no JSON-LD structured data is present, limiting SEO potential. The absence of advanced security headers and HSTS reduces the security hardening of the site. Overall, the technical implementation is modern but basic, suitable for a small informational site rather than a complex commercial platform.
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 frequency.xyz. 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 frequency.xyz.

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.