Skip to main content

Security report for iceshrimp.net

Iceshrimp · Technology · N/a

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

Security score

66/100

Risk levelMedium

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

Iceshrimp is an open source project focused on providing a decentralized and federated social networking service implementing the ActivityPub standard. The project emphasizes performance, stability, and maintainability with a new .NET-based backend and Blazor WASM frontend. It targets users and developers interested in federated social networks and offers compatibility with Mastodon clients. The project operates without commercialization and prioritizes community-driven development. Technically, the website is hosted on a Forgejo instance and uses modern web technologies including .NET, Blazor, C#, and Docker. The site is performant, mobile-optimized, and structured for developer use. Security practices include HTTPS enforcement and CSRF protection, though explicit security headers and policies are not published. From a security perspective, the site shows good SSL configuration and secure form handling but lacks published privacy, cookie, and security policies, as well as incident response contacts. No vulnerabilities or exposed sensitive data were detected. The absence of privacy and cookie policies impacts compliance scoring. Overall, the website is trustworthy and professional with a strong technical foundation but would benefit from enhanced privacy and security disclosures to improve compliance and user trust.

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

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

    • 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

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

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching iceshrimp.net

This scan found 18 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
75
Security headers
60
Email security
80
DNS health
90
Network security
40
GDPR outside view
50
Average
66

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 Iceshrimp project positions itself as a community-centric alternative in the federated social networking space, competing with larger ActivityPub projects. Its open source business model relies on community contributions and transparency rather than commercialization. The project supports migration from previous versions and integrates with multiple Mastodon-compatible clients, indicating a broad target audience of decentralized social network users. The presence of active development, changelogs, and community chat rooms suggests ongoing growth and engagement. The project maintains a clear anti-commercialization stance and focuses on maintainability and stability, which may appeal to privacy-conscious and technically savvy users.

Security posture

The website demonstrates a moderate to good security maturity level with HTTPS enforced and CSRF tokens implemented in forms. However, it lacks explicit security headers such as Content-Security-Policy and X-Frame-Options, which could enhance protection against common web attacks. There is no published security policy, incident response plan, or vulnerability disclosure program, which limits transparency and preparedness. No sensitive data exposure or vulnerable libraries were detected in the analyzed content. The absence of privacy and cookie policies indicates compliance gaps with GDPR and similar regulations. Overall, the security posture is adequate for an open source project but could be improved with formalized policies and enhanced HTTP headers.

Recommendations

  1. Publish a comprehensive privacy policy and cookie policy with clear GDPR compliance statements.
  2. Implement and disclose a security policy including incident response procedures and contact channels.
  3. Add standard security HTTP headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Provide a vulnerability disclosure policy and security.txt file to facilitate responsible reporting.
  5. Include clear contact information for business and security inquiries to improve trust and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Iceshrimp
Description
Iceshrimp is a decentralized and federated social networking service implementing the ActivityPub standard, focusing on performance, stability, and maintainability with a new codebase.
Key services
Decentralized social networking platform, Mastodon-compatible API, Blazor WASM frontend, Migration support from Iceshrimp-JS
Content quality
good
Branding
consistent

Technology

Stack
.NET, Blazor WASM, C#, HTML, CSS, JavaScript, Docker
Frameworks
Forgejo (self-hosted Git service)
Platforms
Web
Performance
fast
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • CSRF tokens used in forms
  • No exposed sensitive data in HTML

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
high

Key observations

  1. Website is a public Forgejo-hosted repository for the Iceshrimp.NET project.
  2. Content is technical and developer-focused with no commercial or marketing emphasis.
  3. No explicit privacy, cookie, or terms of service policies found on the site.
  4. No direct contact emails or phone numbers are provided on the public pages.
  5. The site uses HTTPS with CSRF tokens for form security.
  6. No advertising or tracking scripts detected.
  7. The project is community-driven and open source with active development.
  8. External links mostly point to related federated social networking clients and documentation.
Technical notes

Notes

The website is built on a modern technology stack featuring .NET and Blazor WASM for backend and frontend respectively, with C# as the primary programming language. It is hosted on a Forgejo instance, a self-hosted Git service, indicating control over infrastructure. The site is well-structured with valid HTML and CSS, uses HTTPS, and includes CSRF tokens for form security. Performance is fast with good mobile optimization. However, accessibility features are basic and SEO optimization is minimal. There is no evidence of third-party analytics or tracking scripts, aligning with privacy-conscious design. The site could benefit from enhanced accessibility and SEO improvements as well as formalized security and privacy configurations.
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 iceshrimp.net. 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 iceshrimp.net.

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.