Skip to main content

Security report for eleven.sm

Splash · Other · N/a

High risk. 8 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

42/100

Risk levelHigh

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

The website eleven.sm currently serves as a minimal splash page indicating a temporary pause in service or activity. It provides very limited business information, with the only contact method being a WhatsApp chat link. The site uses modern web technologies such as Webflow for CMS, Cloudflare for hosting and CDN, Google Tag Manager for analytics, and third-party widgets like Jetboost and Elfsight. However, the content is minimal and lacks detailed business descriptions, legal information, or privacy policies. From a security perspective, the site lacks a valid SSL certificate and does not support any TLS protocols, resulting in no HTTPS protection. Critical security headers and best practices are partially implemented but insufficient. The absence of privacy and cookie policies indicates non-compliance with GDPR and related regulations. The domain is mature and active but lacks domain protection mechanisms such as DNSSEC or CAA records, which could pose risks. Overall, the website's risk profile is elevated due to missing HTTPS, minimal content, and lack of compliance documentation. The technical infrastructure is modern but underutilized, and the business credibility is low due to the absence of clear company information. Strategic improvements in security, privacy compliance, and content development are recommended to enhance trust and operational readiness.

Scanned

NIS2 and GDPR posture

GDPR outside view
0/ 100 · Critical
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

8 findings rated critical or high. Fix these first.

  1. GDPR outside view

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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • 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

  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

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

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

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

Keep watching eleven.sm

This scan found 20 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
30
Email security
50
DNS health
70
Network security
100
GDPR outside view
0
Average
42

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 business behind eleven.sm appears to be in a holding or transitional state, as evidenced by the splash page indicating a pause. The lack of detailed business information, absence of privacy and terms policies, and minimal contact options suggest limited current operations or a forthcoming relaunch. The use of WhatsApp as the sole contact channel targets direct customer engagement but limits broader accessibility. The domain's maturity suggests an established presence, but the minimal website content and lack of domain protection may indicate underinvestment or low prioritization of digital assets. No partnerships or subsidiaries are evident, and no revenue or market positioning data is available.

Security posture

The security posture of eleven.sm is weak. The absence of a valid SSL certificate and HTTPS support is a critical vulnerability that exposes users to interception and undermines trust. The lack of modern TLS protocols and security headers further weakens the site's defenses. No incident response or security policy information is provided, and no vulnerability disclosure or security.txt files are present. The domain lacks DNSSEC and CAA records, increasing risk of DNS spoofing or unauthorized certificate issuance. Overall, the site does not meet basic security best practices and requires urgent remediation to protect users and data.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the site immediately.
  2. Implement and enforce modern TLS protocols (TLS 1.2 or TLS 1.3) and enable HSTS with includeSubDomains and preload options.
  3. Develop and publish comprehensive privacy and cookie policies to comply with GDPR and inform users about data handling.
  4. Add security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options to enhance protection.
  5. Enable DNSSEC and configure CAA records to improve domain security and prevent certificate mis-issuance.
  6. Expand website content to include clear business information, contact details, and legal disclosures to improve credibility and user trust.
Technical notes

Notes

The website is built using Webflow CMS and hosted behind Cloudflare CDN, leveraging modern front-end technologies and third-party integrations such as Google Tag Manager, Jetboost, and Elfsight widgets. Despite this, performance metrics are unavailable or zero, indicating possible measurement gaps or minimal resource loading. The site is mobile optimized with responsive design and basic accessibility features. However, the lack of a valid SSL certificate and disabled TLS protocols represent significant technical debt and security risks. The absence of structured data and minimal metadata limits SEO effectiveness. Overall, the technical infrastructure is modern but underutilized and requires security and content improvements.
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 eleven.sm. 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 eleven.sm.

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.