Skip to main content

Security report for webtoo.ls

webtoo.ls · Technology · N/a

Low risk. 4 critical or high findings in Email security, GDPR outside view and 1 other check.

Security score

76/100

Risk levelLow

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

webtoo.ls operates as a small, community-focused Mastodon server dedicated to open source tools within the web ecosystem. It serves maintainers, collaborators, and community members interested in federated social networking. The platform leverages Mastodon 4.3.4, a modern open source social network framework, and is hosted with performance and security considerations including HTTPS and script integrity checks. The site is well-structured, mobile-optimized, and provides a good user experience with clear navigation and branding consistency. However, it lacks visible contact information and cookie consent mechanisms, which impacts privacy compliance. From a security perspective, the site benefits from HTTPS and some security best practices but could improve by adding explicit security headers and publishing security policies or incident response contacts. The absence of WHOIS data suggests privacy protection or a new domain, which is common for small community servers but limits trust verification. No adult or explicit content is present, making the site safe for general audiences. Overall, webtoo.ls demonstrates a solid technical foundation and community-oriented business model but should enhance privacy compliance and transparency to improve trust and security posture. Strategic improvements in contact availability and security documentation would benefit the platform's credibility and user confidence.

Scanned

NIS2 and GDPR posture

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

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

  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 webtoo.ls

This scan found 19 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
75
Email security
75
DNS health
75
Network security
100
GDPR outside view
53
Average
76

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention webtoo.ls, from OffSeq Breach.

No leaked records found

Breach holds no records for webtoo.ls right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

webtoo.ls occupies a niche position as an independent Mastodon instance focused on open source web tools and their community. Its business model centers on providing a federated social networking platform without ads or algorithms, appealing to privacy-conscious and open source advocates. The server has a small active user base (~19 monthly active users) indicating a tight-knit community. The platform's reliance on Mastodon and open source technologies aligns with its target audience of developers and maintainers. Partnerships with Mastodon.org and GitHub reinforce its open source ecosystem integration. The lack of commercial advertising or affiliate programs suggests a non-commercial or community-supported operation. Growth potential depends on community engagement and federation within the fediverse.

Security posture

The security posture of webtoo.ls is generally good, with mandatory HTTPS and use of script/style integrity attributes enhancing protection against tampering. The presence of a content security policy nonce indicates awareness of security best practices. However, the absence of explicit security headers such as X-Frame-Options and X-Content-Type-Options represents an area for improvement. No vulnerabilities or exposed sensitive data were detected in the analyzed content. Privacy compliance is limited by the lack of cookie consent mechanisms and minimal contact information for incident response. The WHOIS privacy protection is typical for small community servers but reduces transparency. Overall, the site is secure but could benefit from enhanced security documentation and compliance measures.

Recommendations

  1. Implement a cookie consent banner to comply with GDPR and improve privacy transparency.
  2. Add security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to strengthen security posture.
  3. Publish a security policy page with incident response contact information to enhance trust and readiness.
  4. Provide clear contact information such as support or admin emails to improve user confidence and compliance.
  5. Regularly review and update WHOIS information if possible to improve domain transparency and legitimacy.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
webtoo.ls
Description
webtoo.ls is a small server dedicated to Open Source tools in the Web ecosystem and their maintainers, collaborators, and close community members.
Key services
Mastodon social networking, Community hosting for open source web ecosystem
Content quality
good
Branding
consistent

Technology

Stack
Mastodon 4.3.4, JavaScript, React, SVG, Cloudflare Insights
Frameworks
Mastodon
Platforms
Fediverse
Performance
fast
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of integrity attributes on scripts and stylesheets
  • Content Security Policy nonce present (style-nonce meta tag)

Analytics and tracking

Services
Cloudflare Insights
Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
Cloudflare Insights
Transparency
poor

Site quality

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

Key observations

  1. Website is a Mastodon instance dedicated to open source web tools community.
  2. No WHOIS data available, indicating privacy protection or new domain.
  3. No contact emails or phone numbers found on the site.
  4. Privacy policy page exists but no cookie consent mechanism detected.
  5. No terms of service or security policy pages found.
  6. Site uses HTTPS with good security practices but lacks some security headers.
  7. No advertising or affiliate marketing detected.
  8. Minimal user tracking via Cloudflare Insights.
  9. No adult or explicit content detected; safe for general audiences.
  10. Good mobile optimization and user experience.
Technical notes

Notes

The website is built on Mastodon 4.3.4, a modern open source social networking platform using React and JavaScript. It employs SVG for logos and icons, and uses Cloudflare Insights for performance and analytics monitoring. The site is mobile-optimized with responsive design and includes meta tags for SEO and social sharing (Open Graph). Script and stylesheet integrity attributes are used to prevent tampering. Hosting appears to be behind Cloudflare, providing CDN and security benefits. Performance is fast with minimal external dependencies. Accessibility is basic but functional. The site lacks a CMS and relies on Mastodon's built-in platform features. Technical risks are low but could be mitigated further by adding missing security headers and improving privacy compliance mechanisms.
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 webtoo.ls. 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 webtoo.ls.

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.