Skip to main content

Security report for meli-email.org

1337 Services LLC · Technology · Saint Kitts and Nevis

Medium risk. 6 critical or high findings in DNS health, Security headers and 2 other checks.

Security score

56/100

Risk levelMedium

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

The website meli-email.org represents a small technology project operated by 1337 Services LLC, focused on delivering a terminal-based email client named meli. The project targets terminal users and developers seeking a modern, extensible mail client with support for various email protocols and storage formats. The business model revolves around open source software distribution with downloadable binaries and source code repositories. The website is hosted on privacy-conscious infrastructure (Njalla) and provides clear navigation and relevant technical content, including installation instructions and screenshots. From a technical perspective, the site uses modern web technologies such as Rust for the client software, WebAssembly for an online demo, and standard HTML5 and CSS for the website. The site supports multiple Unix-like platforms and provides source code access via a dedicated git repository. Performance and mobile optimization are moderate, with basic accessibility and SEO features. Security posture is limited; the site lacks published privacy, cookie, or security policies, and no security headers were detected. The domain uses HTTPS but DNSSEC is not enabled. No contact information or incident response channels are provided, limiting transparency and trust. WHOIS data is public and consistent with the project timeline, indicating legitimacy but no strong business presence. Overall, the website is functional and informative for its niche audience but lacks formal privacy and security compliance measures. Strategic improvements in policy publication, security headers, and contact transparency would enhance trust and compliance.

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

6 findings rated critical or high. Fix these first.

  1. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • Critical

      DNS Resolution Failed

      Unable to resolve domain A records

      What to do: Verify domain is properly configured and not expired

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

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

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

Keep watching meli-email.org

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. 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
55
Email security
70
DNS health
45
Network security
40
GDPR outside view
50
Average
56

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 project is positioned as a niche open source terminal email client targeting technical users on Unix-like systems. Its competitive advantage lies in configurability, extensibility, and modern design principles for terminal applications. Revenue streams are likely indirect, possibly through donations or community support, as no commercial offerings are evident. The target customer segment includes developers, system administrators, and terminal enthusiasts. Growth indicators include recent software releases and active source code repositories. The partnership ecosystem is minimal, with no explicit partners or subsidiaries. The business operates under 1337 Services LLC, registered in Saint Kitts and Nevis, suggesting a small, possibly single-entity operation.

Security posture

The website demonstrates a basic security posture with HTTPS enabled but lacks advanced security headers and DNSSEC. No privacy or cookie policies are published, and no incident response or security contact information is provided. The absence of these elements indicates limited compliance with GDPR and other data protection regulations. No vulnerabilities or exposed sensitive data were detected in the content. The security culture appears minimal, focused on software development rather than formal security governance. This presents moderate risk in terms of user trust and regulatory compliance.

Recommendations

  1. Publish comprehensive privacy and cookie policies to improve GDPR compliance and user trust.
  2. Implement security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
  3. Provide clear contact information including security and abuse contacts to facilitate incident response and transparency.
  4. Enable DNSSEC for the domain to strengthen DNS security and prevent spoofing.
  5. Consider adding analytics with privacy-respecting configurations and cookie consent mechanisms to improve user experience and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
1337 Services LLC
Description
meli is a configurable and extensible terminal-based e-mail client with sane defaults, aimed at both new and power users of the terminal. It supports various email workflows and software stacks, integrating email storage, sync, tagging, SMTP client, contact management, and user-chosen editors.
Key services
Terminal email client, Email threading, Multi-threaded operation, Integration with various mail storage formats (IMAP, Maildir, notmuch, JMAP, mbox), Contact list management, Extensible editor embedding
Content quality
good
Branding
consistent

Technology

Stack
Rust (cargo package manager), WebAssembly (for online demo), SVG graphics, HTML5, CSS
Platforms
Debian, macOS, NetBSD, OpenBSD, NixOS
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
30/100

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. Website is a technical project site for an open source terminal email client named meli.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails or phone numbers explicitly provided.
  4. No security or incident response policies published.
  5. No analytics or advertising detected.
  6. Website is well structured with clear navigation and relevant content.
  7. No WAF or blocking detected; content fully accessible.
  8. WHOIS data is public and consistent with project age and scope.
Technical notes

Notes

The website is built using modern web standards with a focus on terminal-based software distribution. The tech stack includes Rust for the client application, WebAssembly for interactive demos, and standard HTML/CSS for the site. Hosting is via Njalla, a privacy-focused provider. Performance is moderate with no major issues detected. The site lacks advanced SEO and accessibility features but maintains good navigation and content relevance. Technical debt appears low given the recent domain registration and active development. Opportunities exist to modernize security configurations and improve mobile responsiveness.
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 meli-email.org. 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 meli-email.org.

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.