Skip to main content

Security report for feddit.rocks

kavin · Technology · N/a

Partial score · DNS & email only

46/100

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

Feddit.rocks is a small, community-driven Lemmy instance within the Fediverse ecosystem, powered by the kavin.rocks verse. It offers a platform for open and respectful discussions on a wide range of topics including technology, privacy, programming humor, and European buying initiatives. The platform emphasizes moderation, community rules, and supports federation with captcha-enabled registration to prevent abuse. The business model relies on donations via cryptocurrency and Liberapay, targeting users interested in decentralized social networking and privacy-conscious communities. Technically, the website is built on the Lemmy open-source platform, hosted and registered through Cloudflare, Inc. It uses HTTPS with a valid SSL certificate, ensuring secure communications. The site is mobile optimized and includes basic SEO metadata, but lacks advanced security headers and privacy policies. The technical infrastructure is modern and adequate for its community-focused purpose, though there is room for improvement in security hardening and privacy compliance. From a security perspective, the site enforces HTTPS and uses captcha with hard difficulty for registrations, which helps mitigate automated abuse. However, the absence of DNSSEC and security headers like Content-Security-Policy or X-Frame-Options represents potential vulnerabilities. No direct contact or incident response information is published, limiting transparency in security management. The domain registration is transparent and consistent with the website's claims, supporting legitimacy. Overall, Feddit.rocks presents a trustworthy and functional community platform with good content quality and technical implementation. To enhance trust and compliance, it should publish privacy and cookie policies, implement security headers, and provide clear contact information. These improvements would strengthen its security posture and user confidence.

Scanned

NIS2 and GDPR posture

GDPR outside view
58/ 100 · Medium
Checks completed
6of 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

4 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. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • Critical

      Unable to retrieve SSL certificate

      Could not establish secure connection to retrieve certificate information

      What to do: Check if the server is accessible and SSL/TLS is properly configured

  3. GDPR outside view

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

    • 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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

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

Keep watching feddit.rocks

This scan found 14 issues across 5 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
0
Email security
60
DNS health
70
Network security
40
GDPR outside view
58
Average
46

Not counted

  • Security headers: did not complete in this scan.
  • 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

Feddit.rocks operates as a niche social community platform within the decentralized Fediverse network, leveraging the Lemmy software. Its competitive advantage lies in its open, respectful community ethos and federation capabilities, appealing to privacy-conscious and tech-savvy users. The donation-based revenue model aligns with its community-driven nature. The platform fosters partnerships and content sharing with other Fediverse instances and related communities, enhancing its ecosystem presence. Growth indicators include active moderation, federation features, and multilingual support. Strategic observations suggest focusing on improving privacy compliance and security transparency to attract a broader user base and institutional trust.

Security posture

The security maturity of Feddit.rocks is moderate. Key strengths include enforced HTTPS, captcha protection on registration, and domain transfer lock status. However, the lack of DNSSEC, security headers, and published security policies indicates gaps in defense-in-depth and transparency. No vulnerabilities or exposed sensitive data were detected in the analyzed content. Compliance with GDPR and incident response readiness appear limited due to missing policies and contact channels. The security culture is community-oriented but would benefit from formalized security documentation and proactive vulnerability disclosure mechanisms.

Recommendations

  1. Implement DNSSEC to enhance domain name system security.
  2. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish comprehensive privacy and cookie policies to improve GDPR compliance and user trust.
  4. Provide clear contact information including security and abuse reporting channels.
  5. Enable federation signed fetch to improve federation security and data integrity.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
kavin
Description
A lemmy instance powered by the kavin.rocks verse. Feddit.rocks is a community platform dedicated to fostering open and respectful conversations covering a wide range of topics and encouraging diverse perspectives.
Key services
Community discussions, Content sharing, Federated social networking
Content quality
good
Branding
consistent

Technology

Stack
Lemmy (open source federated platform), Cloudflare DNS and registrar, JavaScript, Bootstrap (data-bs-theme attribute)
Frameworks
Lemmy
Platforms
Fediverse
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Captcha enabled with hard difficulty
  • Client transfer prohibited domain status

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. The website is a Lemmy instance focused on community discussions within the Fediverse.
  2. Content is diverse, covering topics like programming humor, privacy, memes, technology, and European buying initiatives.
  3. No explicit privacy, cookie, or terms of service policies found on the homepage or metadata.
  4. No direct company contact emails or phone numbers found.
  5. Moderation and community rules are clearly stated in the sidebar content.
  6. Donation options are provided via cryptocurrency and Liberapay.
  7. The site uses HTTPS with a valid SSL certificate.
  8. No security headers detected in the provided data; potential area for improvement.
  9. No advertising or tracking scripts detected in the provided content.
  10. The site is mobile optimized and accessible with basic SEO metadata.
Technical notes

Notes

Feddit.rocks is built on the Lemmy open-source federated social platform, hosted and registered via Cloudflare, Inc. The site uses HTTPS with a valid SSL certificate and is mobile optimized with basic SEO metadata. The technology stack includes JavaScript and Bootstrap for UI theming. Performance is moderate with no major issues detected. However, the absence of DNSSEC and security headers suggests technical debt in security hardening. The platform supports federation and captcha for user registration, indicating a focus on community integrity. Opportunities exist to modernize security configurations and enhance privacy compliance to reduce operational 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 feddit.rocks. 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 feddit.rocks.

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.