Skip to main content

Security report for lovelysystems.com

Lovely Systems GmbH · Technology · Germany

High risk. 9 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

Lovely Systems GmbH is a small technology company specializing in building and operating digital platforms, focusing on multi-platform applications and large-scale web services. Their website presents a modern chat interface and highlights their expertise in scalable digital solutions. The company maintains a presence on GitHub and LinkedIn, supporting their credibility and outreach to developers and businesses seeking digital platform services. Technically, the website uses modern JavaScript and CSS features but suffers from slow load times and lacks a content management system. Security posture is weak due to the absence of a valid SSL certificate, no HTTPS support, and missing security headers, which exposes users to potential risks. Privacy compliance is minimal, with no visible privacy or cookie policies, and limited user tracking via GoatCounter analytics. Overall, the site is functional but requires significant improvements in security and privacy to meet industry standards.

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

9 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

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

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
0
Security headers
15
Email security
50
DNS health
85
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

Lovely Systems operates as a niche service provider in the technology sector, targeting businesses and developers needing scalable digital platforms. Their business model centers on service provision rather than product sales, with key services including multi-platform app development and large-scale web services. The company leverages open-source and social coding platforms like GitHub to enhance transparency and collaboration. Market positioning is modest but focused, with no evidence of large-scale enterprise operations. The lack of detailed business information such as founding year or parent company suggests a small, independent entity. Their partnership ecosystem is limited to social media and code repositories, with no visible payment or third-party service integrations. Growth indicators and revenue streams are not disclosed on the website.

Security posture

The security maturity of Lovely Systems' website is low. The absence of a valid SSL certificate and HTTPS support is a critical vulnerability, severely impacting user trust and data security. No security headers or advanced SSL configurations are present, and no incident response or vulnerability disclosure policies are published. Email security is partially addressed with SPF records, but no DMARC or DKIM records were noted. The site does not implement GDPR compliance mechanisms such as privacy or cookie consent banners. While no known vulnerabilities or malware were detected, the lack of basic security controls exposes the site to potential risks. Incident response readiness and security culture indicators are not evident from the website content or WHOIS data.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire website.
  2. Implement security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web attacks.
  3. Publish comprehensive privacy and cookie policies with GDPR compliance mechanisms and consent management.
  4. Add a security.txt file and vulnerability disclosure policy to improve transparency and incident response readiness.
  5. Optimize website performance to reduce load times and improve user experience, especially on mobile devices.
Technical notes

Notes

The website is built with modern front-end technologies including JavaScript modules, CSS custom properties, and web fonts. It uses the marked library for Markdown parsing and fetch API for asynchronous communication with a backend API. Hosting appears to be via GitHub Pages, inferred from IP addresses and DNS records, with DNS managed by AWS Route53. Performance is suboptimal with a load time exceeding 11 seconds, likely due to unoptimized resources or network latency. Accessibility features are basic, with some responsive design elements and semantic HTML usage. SEO optimization is minimal, relying on basic meta tags and Open Graph properties without structured data markup. The absence of a CMS suggests a static site or custom-built frontend. Technical debt includes missing HTTPS and lack of security best practices, which pose operational risks.
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 lovelysystems.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 lovelysystems.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.