Skip to main content

Security report for gregtech.eu

Technology · N/a

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

Security score

63/100

Risk levelMedium

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

The website gregtech.eu serves as a sleek client interface for the Lemmy federated social platform, targeting general users interested in decentralized community discussions. The site demonstrates a modern technical infrastructure built on SvelteKit and hosted via Cloudflare, ensuring fast performance and mobile optimization. However, it lacks explicit privacy, cookie, and terms of service policies, which are critical for compliance and user trust. Security posture is adequate with HTTPS and service worker usage but could be improved by adding security headers and incident response information. Overall, the site appears legitimate and consistent with a small technology project but would benefit from enhanced compliance and transparency measures.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
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

8 findings rated critical or high. Fix these first.

  1. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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

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

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

Keep watching gregtech.eu

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
75
Security headers
15
Email security
70
DNS health
90
Network security
100
GDPR outside view
25
Average
63

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 business operates in the technology sector, focusing on providing a client for the Lemmy platform. It targets users of federated social networks, likely enthusiasts and privacy-conscious communities. The business model appears to be service-oriented, offering a user interface rather than monetized content. There is no visible revenue stream or partnership ecosystem disclosed. The site maintains consistent branding and content quality but lacks detailed business information or certifications. Growth indicators and market positioning are unclear due to limited public business data.

Security posture

The website employs HTTPS and registers a service worker, indicating a baseline security awareness. However, it lacks critical security headers such as Content-Security-Policy and Strict-Transport-Security, which could enhance protection against common web attacks. No vulnerabilities or exposed sensitive data were detected in the content. The absence of privacy and incident response policies suggests gaps in compliance and readiness. The site does not provide contact channels for security incidents, which is a notable deficiency. Overall, the security maturity is moderate but requires improvements to meet best practices and regulatory requirements.

Recommendations

  1. Implement and publish comprehensive privacy and cookie policies with user consent mechanisms.
  2. Add security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Provide clear contact information and an incident response policy to improve trust and compliance.
  4. Include terms of service and vulnerability disclosure policies to enhance transparency.
  5. Enhance SEO metadata and structured data to improve discoverability and user engagement.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
A sleek client for Lemmy
Key services
Lemmy client
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, SvelteKit, Cloudflare Insights
Frameworks
SvelteKit
Performance
fast
Mobile
excellent
Accessibility
good
SEO
basic

Security

Observed score
85/100
Good practices seen
  • HTTPS enabled
  • Service worker registered

Analytics and tracking

Services
Cloudflare Insights
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Cloudflare Insights
Transparency
poor

Site quality

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

Key observations

  1. Website is a client interface for Lemmy, a federated social platform.
  2. No explicit privacy, cookie, or terms of service policies found.
  3. No direct contact information or business registration details provided.
  4. Site uses modern web technologies and is well optimized for mobile.
  5. No security policy or incident response information is available.
  6. External links mostly point to federated instances and related community sites.
  7. No advertising or affiliate marketing detected except Cloudflare analytics.
  8. Content is safe and suitable for general audiences.
  9. No WAF or blocking mechanisms detected.
Technical notes

Notes

The website is built using modern web technologies, primarily SvelteKit, which supports fast, reactive user interfaces. Hosting via Cloudflare provides performance benefits and security features. The site loads quickly and is optimized for mobile devices, with responsive design and accessibility considerations. However, SEO optimization is basic, with minimal meta tags and no structured data like JSON-LD detected. The technical implementation is solid but could be improved with enhanced SEO and security configurations. No CMS or backend platform is explicitly identified.
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 gregtech.eu. 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 gregtech.eu.

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.