Skip to main content

Security report for renatesanz.com

Renate Sanz · Other · Germany

High risk. 11 critical or high findings in GDPR outside view, SSL/TLS and 3 other checks.

Security score

27/100

Risk levelHigh

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

The website renatesanz.com serves as an online portfolio for the artist Renate Sanz, showcasing various artworks including paintings and sculptures. The site targets art enthusiasts and potential gallery visitors, providing exhibition information and artist biography. The business model is focused on personal branding and promotion of artistic work within a niche market. The website is primarily in German with options for English and Spanish, indicating a European and international audience. Technically, the site is built on Drupal 7, an outdated CMS version, and uses jQuery and Google Analytics for tracking. The hosting provider is kasserver.com. Performance is slow with basic mobile optimization and accessibility features. Security posture is weak due to lack of HTTPS, visible deprecated PHP warnings, and minimal security headers. No privacy or cookie policies are present, indicating poor GDPR compliance. Contact information is not explicitly provided on the site. Overall, the site shows basic professionalism but requires significant improvements in security, privacy compliance, and technical modernization.

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

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

  4. 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 renatesanz.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
40
Email security
50
DNS health
70
Network security
0
GDPR outside view
0
Average
27

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

Renate Sanz operates as an individual artist with a small-scale online presence. The website functions as a portfolio and informational hub rather than a commercial e-commerce platform. Market positioning is niche, targeting art collectors and enthusiasts interested in contemporary art. The business model relies on exhibitions and direct contact for sales or commissions. There is no evidence of partnerships or subsidiaries. The site lacks advanced marketing or advertising integrations beyond Google Analytics. Growth indicators and revenue streams are not discernible from the website content. The partnership ecosystem appears minimal or non-existent.

Security posture

The security maturity level of the website is low. The absence of HTTPS exposes visitors to risks of data interception and man-in-the-middle attacks. Deprecated PHP warnings indicate outdated backend code that may harbor vulnerabilities. Security headers are minimal, with only X-Content-Type-Options and X-Frame-Options present. No HSTS, OCSP stapling, or session resumption mechanisms are implemented. The SPF record is valid but uses a neutral qualifier, which weakens email spoofing protection. No incident response or vulnerability disclosure policies are found. GDPR compliance is lacking due to missing privacy and cookie policies. Overall, the site is vulnerable to common web threats and does not follow best practices for security or privacy.

Recommendations

  1. Implement HTTPS with a valid SSL/TLS certificate to secure all traffic.
  2. Update Drupal to a supported version and fix deprecated PHP code to eliminate warnings and reduce vulnerabilities.
  3. Add comprehensive privacy and cookie policies to comply with GDPR requirements.
  4. Enhance email security by tightening SPF records and consider adding DMARC and DKIM.
  5. Introduce security headers such as Content Security Policy and enable HSTS with includeSubDomains.
  6. Deploy a security.txt file to facilitate vulnerability disclosure and incident response.
  7. Improve website performance and mobile optimization to enhance user experience and SEO.
Technical notes

Notes

The website is built on Drupal 7, which is no longer supported and may contain unpatched security vulnerabilities. The frontend uses jQuery and several Drupal modules including views_slideshow and fancybox for image display. Google Analytics is integrated for visitor tracking with IP anonymization enabled. The site is hosted on kasserver.com with DNS records pointing to a single IPv4 address. No IPv6 records are present. The HTTP headers indicate no caching and basic security headers but lack modern protections like CSP or HSTS. The site is served over HTTP only, with no SSL/TLS protocols enabled. Performance metrics are missing but the presence of multiple CSS and JS files from an external domain (renatesanz.de) may impact load times. Accessibility features are basic with skip links and language switching. SEO is minimal with basic meta tags and no structured data or Open Graph tags detected.
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 renatesanz.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 renatesanz.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.