Skip to main content

Security report for alphavilletraduzioni.eu

Plesk Obsidian 18.0.70 · Technology · Italy

High risk. 8 critical or high findings in GDPR outside view, Network security and 1 other check.

Security score

41/100

Risk levelHigh

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

The website alphavilletraduzioni.eu currently serves a default Plesk Obsidian control panel interface rather than a public-facing business website. This indicates that the domain is either under development or used solely for server management purposes. The technical infrastructure is based on Plesk 18.0.70 running on an nginx server, with JavaScript libraries such as Prototype.js and RequireJS. However, the site lacks a valid SSL certificate, resulting in no HTTPS support, which significantly impacts security posture. Security headers are partially implemented but insufficient without encryption. No privacy policy, terms of service, or contact information is present, limiting compliance and business credibility. The domain registration is consistent and legitimate, but the lack of active business content reduces trustworthiness and user engagement.

Scanned

NIS2 and GDPR posture

GDPR outside view
15/ 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

      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. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

  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 alphavilletraduzioni.eu

This scan found 16 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
50
Security headers
55
Email security
50
DNS health
75
Network security
0
GDPR outside view
15
Average
41

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 · found on this site
  • 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 is registered through a reputable registrar, Key-Systems GmbH, and uses DNS servers from telemar.it, indicating an Italian hosting environment. The absence of business content, contact details, or marketing materials suggests the site is not yet operational for commercial purposes. The target audience appears to be server administrators or hosting customers managing the Plesk control panel. There are no indications of partnerships, subsidiaries, or revenue streams from the website content. The business model is likely related to web hosting or translation services (implied by the domain name), but no explicit information is provided.

Security posture

The security posture is weak due to the absence of a valid SSL certificate and lack of HTTPS support. Although some security headers like X-Frame-Options, X-XSS-Protection, and X-Content-Type-Options are present, they do not compensate for the missing encryption. No advanced security features such as HSTS, OCSP stapling, or session resumption are enabled. The site does not expose sensitive data or show signs of vulnerabilities like Heartbleed or POODLE, but the lack of HTTPS is a critical issue. No incident response or security policy information is available, and GDPR compliance is not demonstrated.

Recommendations

  1. Install and configure a valid SSL/TLS certificate to enable HTTPS and improve security posture.
  2. Develop and publish privacy policy and terms of service pages to enhance compliance and user trust.
  3. Add clear business contact information including email and phone numbers to improve credibility.
  4. Enable advanced security headers and features such as HSTS, OCSP stapling, and session resumption.
  5. Replace the default Plesk control panel page with a professional business website to engage visitors and support business goals.
Technical notes

Notes

The website runs on an nginx server with Plesk Obsidian 18.0.70 and uses JavaScript libraries Prototype.js and RequireJS. The DNS is managed by telemar.it with no DNSSEC or CAA records enabled. The SSL certificate is invalid or missing, and no TLS protocols are enabled, resulting in unencrypted HTTP traffic. Performance metrics are unavailable, but the lack of SSL and minimal content suggest slow or incomplete deployment. The site is not optimized for SEO or accessibility beyond basic meta tags. The hosting provider is not explicitly identified beyond IP and DNS information. Overall, the technical setup is incomplete and requires modernization and security 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 alphavilletraduzioni.eu. 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 alphavilletraduzioni.eu.

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.