Skip to main content

Security report for malpils.lv

Other · N/a

Medium risk. 8 critical or high findings in GDPR outside view, Email security and 2 other checks.

Security score

64/100

Risk levelMedium

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

The website malpils.lv/login_up.php serves as a login portal for a Plesk hosting control panel instance. It primarily provides access to server management functions and does not present any public-facing business content or services. The site uses the Plesk UI library and standard JavaScript frameworks to deliver a functional login interface with cookie consent mechanisms aligned with GDPR requirements. However, the site lacks visible privacy policies, terms of service, or contact information, limiting transparency and user trust. The absence of WHOIS data due to query limits restricts domain legitimacy assessment, but the site content and structure align with typical hosting control panel login portals. Technically, the site employs modern JavaScript libraries and is mobile optimized with basic accessibility features. Security posture is moderate but could be improved by adding security headers and ensuring HTTPS enforcement. Cookie consent is implemented, but privacy compliance documentation is missing. No external advertising or tracking beyond error monitoring (Sentry) is detected. Overall, the site is functional for its intended purpose but lacks comprehensive business and security transparency. The risk is moderate due to limited public information and missing security best practices. Strategic improvements in security headers, privacy documentation, and contact transparency are recommended to enhance trust and compliance.

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

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

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

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

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

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. 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
40
DNS health
75
Network security
100
GDPR outside view
40
Average
64

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 domain malpils.lv appears to be used solely for hosting control panel access rather than a commercial business website. There is no identifiable company name, business description, or sector information. The business model is likely internal or service-provider focused, targeting server administrators or hosting customers. No revenue streams, partnerships, or growth indicators are visible. The lack of contact details and public business information suggests a small-scale or internal use case rather than a public-facing enterprise. The site’s branding is minimal and consistent with Plesk’s default styling, indicating no custom corporate branding or market positioning.

Security posture

Security maturity is basic to moderate. The site uses HTTPS (assumed from typical Plesk deployments) and includes a cookie consent mechanism, indicating some GDPR awareness. However, no security headers such as Content-Security-Policy, X-Frame-Options, or HSTS are visible in the HTML content, which are important for mitigating common web attacks. The password input field includes a show/hide toggle, improving usability but not security. No incident response or security contact information is provided. The absence of privacy policy and terms of service reduces compliance transparency. No known vulnerabilities or exposed sensitive data were detected in the HTML content. Overall, the site would benefit from enhanced security headers, documented policies, and incident response readiness.

Recommendations

  1. Implement and enforce HTTPS with strong SSL/TLS configuration and verify via external tools.
  2. Add security headers including Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, and Strict-Transport-Security.
  3. Publish a clear privacy policy and terms of service accessible from the login page.
  4. Provide visible contact information for support and security incident reporting.
  5. Regularly audit and update third-party libraries and monitor for vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
basic
Branding
moderate

Technology

Stack
Plesk, Prototype.js, RequireJS, JavaScript, CSS, HTML5
Frameworks
Plesk UI Library
Platforms
Plesk Hosting Control Panel
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
50/100
Good practices seen
  • Cookie consent mechanism present
  • Password input field with show/hide toggle

Analytics and tracking

Services
Sentry (error tracking)
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Sentry
Transparency
poor

Site quality

Design
basic
User experience
basic
Content relevance
poor
Navigation
basic
Professionalism
basic
Trustworthiness
low

Key observations

  1. Website is a Plesk hosting control panel login page.
  2. No WHOIS data available due to query limit error.
  3. No privacy policy or terms of service found on the login page.
  4. Cookie consent mechanism is implemented with GDPR considerations.
  5. No contact information or business details provided on the page.
  6. No security headers or advanced security configurations visible in HTML.
  7. Site uses Plesk UI library and standard JavaScript libraries.
  8. No external advertising or affiliate links detected.
  9. No social media or company contact emails found.
  10. Content is minimal and functional for login purposes only.
Technical notes

Notes

The website is built on the Plesk hosting control panel platform, utilizing the Plesk UI library, Prototype.js, RequireJS, and standard web technologies (HTML5, CSS, JavaScript). The site is mobile optimized and includes accessibility features such as labels and aria attributes. Performance appears moderate based on included scripts and CSS. No CMS or third-party hosting provider information is evident. The site lacks advanced SEO optimization and metadata beyond basic title and viewport settings. No structured data (JSON-LD) or Open Graph tags are present. The site uses Sentry for error tracking and AWS Firehose for telemetry. Overall, the technical stack is standard for a hosting control panel but lacks enhancements for SEO, security, and business transparency.
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 malpils.lv. 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 malpils.lv.

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.