Skip to main content

Security report for lopesan.com

Lopesan Hotel Group · Hospitality · Spain

Medium risk. 6 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

71/100

Risk levelMedium

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

Lopesan Hotel Group operates a well-established hospitality business focused on providing hotel and resort accommodations primarily in Spain. The website serves as the official online presence for the group, offering booking capabilities and showcasing their unique destinations and services. The company has a strong market position with a domain age of over 25 years, indicating stability and trustworthiness. Technically, the website leverages modern web technologies including React and Liferay CMS, ensuring a robust and scalable platform. The site is mobile optimized and performs moderately well, with good SEO practices in place. Security posture is solid with HTTPS enforced and domain transfer protections, though DNSSEC is not enabled and explicit security policies are not published. Privacy compliance is partially addressed with a cookie consent mechanism but lacks explicit privacy and terms of service documentation. Overall, the website is professional, trustworthy, and suitable for its target audience of travelers and tourists.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
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

6 findings rated critical or high. Fix these first.

  1. 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 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';…

  2. GDPR outside view

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

    • 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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics, Facebook, Twitter, LinkedIn, YouTube, Google APIs

      What to do: Document all third-party data sharing in your privacy policy

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

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching lopesan.com

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
52
Security headers
60
Email security
80
DNS health
85
Network security
100
GDPR outside view
50
Average
71

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 Lopesan Hotel Group targets the hospitality sector, offering hotel and resort services with an online booking model. Their competitive advantage lies in their established brand, multiple resort locations, and a professional digital presence. The business model focuses on direct customer engagement through their website, facilitating reservations and promoting their unique experiences. The company appears to be large in size, founded in 1998, and operates primarily in Spain. The website's content and structure support a clear customer journey, though contact information is not prominently displayed in the analyzed content. Marketing and analytics tools such as Google Tag Manager and Liferay Analytics are used to monitor user behavior and optimize engagement. The absence of explicit privacy and security policies suggests areas for improvement in compliance and transparency.

Security posture

The website demonstrates a mature security posture with HTTPS enforced and domain status flags that prevent unauthorized transfers or updates. The use of nonce attributes in scripts indicates some level of Content Security Policy implementation. However, DNSSEC is not enabled, which could be a potential risk for DNS spoofing. No vulnerabilities or exposed sensitive data were detected in the provided content. The lack of published security policies, incident response contacts, or vulnerability disclosure mechanisms indicates gaps in transparency and readiness. Privacy compliance is partially implemented via cookie consent but lacks comprehensive documentation. Overall, the security posture is good but could be enhanced by publishing explicit policies and enabling DNSSEC.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Publish comprehensive privacy policy and terms of service pages accessible from the main site.
  3. Add a security policy page detailing frameworks, certifications, and incident response procedures.
  4. Implement and publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Improve accessibility features to meet higher standards and enhance user experience for all visitors.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Lopesan Hotel Group
Description
Descubre los hoteles Lopesan: destinos únicos, playas paradisíacas, confort y experiencias inolvidables diseñadas para ti. ¡Reserva ya!⛱️🌴🛎️
Key services
Hotel accommodations, Resort experiences, Online reservations
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, React, Liferay, YUI, Bootstrap, Swiper
Frameworks
Liferay DXP
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited and clientUpdateProhibited domain status
  • Use of nonce in CSP scripts

Analytics and tracking

Services
Liferay Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Liferay Analytics, Privacy Center SDK
Marketing tools
Liferay Analytics
Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is professionally presented and relevant to hospitality industry.
  3. Privacy and terms pages are not explicitly found, but cookie consent is implemented.
  4. No direct contact emails or phone numbers found in the HTML content provided.
  5. Strong use of Liferay CMS and modern JavaScript frameworks.
  6. Good SEO and social media integration implied.
  7. Security posture is good but can be improved with DNSSEC and explicit security policies.
Technical notes

Notes

The website is built on the Liferay CMS platform, utilizing React and YUI JavaScript libraries, along with Bootstrap for styling and Swiper for interactive components. The infrastructure appears modern and well-maintained, with combined and minified JavaScript resources to optimize performance. The site uses Google Tag Manager and Liferay Analytics for tracking and marketing insights. While performance is moderate, there is room for improvement in accessibility and SEO. The absence of DNSSEC and explicit security headers beyond standard HTTPS suggests some technical debt in security hardening. Overall, the technical implementation supports a professional and scalable web presence suitable for a large hospitality business.
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

Earlier scans of this domain

  1. 73/100Medium27 findingsView report
Reviews of this site

Share your experience with lopesan.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 lopesan.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.