Skip to main content

Security report for stackmail.com

Webmail :: Welcome to Webmail · Technology · N/a

Medium risk. 6 critical or high findings in SSL/TLS, Security headers and 1 other check.

Security score

52/100

Risk levelMedium

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

Stackmail.com operates as a webmail service platform, providing users with access to email via a web interface. The website is primarily a login portal built on the Roundcube webmail platform, targeting users who require email access. The business appears to be small and technology-focused, with a domain age of 18 years indicating a mature presence. However, the public-facing content is minimal, lacking detailed business descriptions or contact information. From a technical perspective, the site uses common web technologies such as jQuery and Bootstrap, but suffers from slow load times and lacks modern security implementations. Critically, the site does not have a valid SSL/TLS certificate, resulting in unencrypted HTTP access, which severely impacts user trust and security. The DNS configuration includes a valid SPF record but lacks DMARC, and no security headers or advanced TLS features are enabled. Security posture is weak due to the absence of HTTPS, missing security headers, and no visible privacy or cookie policies. There is no evidence of incident response or vulnerability disclosure mechanisms. The WHOIS data is consistent and indicates a legitimate domain registration with moderate domain protection. Overall, the site presents significant security and privacy compliance gaps that should be addressed to improve trust and protect users. Strategic recommendations include immediate deployment of a valid SSL certificate, implementation of security headers and DMARC, and publication of privacy and cookie policies. Enhancing performance and adding clear business and contact information would also improve credibility and user experience.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
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. 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

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

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

Keep watching stackmail.com

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. 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
0
Security headers
50
Email security
50
DNS health
70
Network security
100
GDPR outside view
40
Average
52

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

Stackmail.com is positioned as a niche email service provider focusing on webmail access. Its competitive advantage lies in providing a straightforward webmail interface likely integrated with Microsoft Outlook protection services as indicated by DNS MX records. The business model is service-based, targeting end-users requiring email hosting or access. Revenue streams are not publicly visible but likely derive from email hosting subscriptions or related services. The lack of marketing or social media presence suggests a focused, possibly B2B or existing customer base. Growth indicators and partnerships are not evident from the public data. The domain's longevity supports operational stability but the minimal public footprint limits broader market visibility.

Security posture

The current security maturity level of stackmail.com is low. The absence of HTTPS is a critical vulnerability exposing users to interception and man-in-the-middle attacks. Missing DMARC records increase the risk of email spoofing. Lack of security headers and no OCSP stapling or session resumption further weaken the security posture. No privacy or cookie policies indicate non-compliance with GDPR and other privacy regulations. Incident response readiness and vulnerability disclosure mechanisms are not found, suggesting limited security governance. These gaps pose significant risks to user data confidentiality and trust. Immediate remediation is necessary to mitigate potential business impact and regulatory penalties.

Recommendations

  1. Deploy a valid SSL/TLS certificate to enable HTTPS and protect user data in transit.
  2. Implement DMARC along with SPF and DKIM to strengthen email security and prevent spoofing.
  3. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Publish comprehensive privacy and cookie policies to comply with GDPR and enhance transparency.
  5. Establish an incident response process and provide clear security contact channels for vulnerability reporting.
Technical notes

Notes

The website is built on a standard Roundcube webmail platform using jQuery and Bootstrap for UI components. The technical infrastructure includes DNS records with SPF configured but lacks DMARC. Hosting details are not explicit but the IP address does not reveal a major cloud provider. Performance is poor with a load time exceeding 8 seconds, indicating potential server or network inefficiencies. The absence of HTTPS and modern TLS protocols is a major technical deficiency. No CMS or advanced frameworks detected. The site is minimally optimized for mobile and accessibility. There is no evidence of analytics or marketing technologies, suggesting a simple, functional deployment focused solely on webmail access.
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 stackmail.com. 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 stackmail.com.

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.