Skip to main content

Security report for pukarags.lv

Pūķarags · Hospitality · Latvia

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

Security score

61/100

Risk levelMedium

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

Pūķarags is a small hospitality business located on the Baltic Sea coast within the Pape Nature Park in Latvia. The website presents the company as a leisure complex offering accommodation and beach-related activities, targeting tourists seeking a memorable coastal experience. The business maintains a regional market position with a focus on natural surroundings and active leisure. Technically, the website is built on modern frameworks such as Nuxt.js and Vue.js, integrating Google Maps for location services. The site is moderately optimized for performance and mobile use, with basic accessibility and SEO features. Security posture is good with HTTPS enforced and secure forms, though some security headers are missing. Privacy and cookie policies are present and indicate GDPR compliance. Contact information is comprehensive, including phone, email, physical address, and a contact form. However, the site lacks terms of service, incident response, and vulnerability disclosure information. Overall, the website is professional, trustworthy, and safe for general audiences, reflecting a legitimate small hospitality business in Latvia.

Scanned

NIS2 and GDPR posture

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

6 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 Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • 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

  2. 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 pukarags.lv

This scan found 25 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. See sample alerts.

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
65
Security headers
40
Email security
55
DNS health
80
Network security
100
GDPR outside view
28
Average
61

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 company operates in the hospitality sector, providing accommodation and leisure services primarily to tourists visiting the Baltic Sea coast. Its business model centers on regional tourism with a focus on natural and beach experiences. The website's content and social media presence support its market positioning as a local leisure destination. Revenue streams likely include accommodation bookings and possibly event or activity services. The company targets a broad audience of leisure travelers and families. There is no evidence of large-scale partnerships or subsidiaries. The business appears to be small in size with consistent branding and good content quality. The lack of detailed corporate information such as VAT or registration numbers suggests a small or privately held entity.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enabled and secure contact forms. However, it lacks several recommended security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options, which could improve protection against common web attacks. There is no visible incident response or vulnerability disclosure information, which limits transparency and preparedness for security incidents. Privacy compliance is well addressed with clear privacy and cookie policies and a consent mechanism. No exposed sensitive data or vulnerable libraries were detected. Overall, the security posture is adequate for a small hospitality website but could benefit from enhancements in headers and incident response readiness.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection.
  2. Publish terms of service and a security policy page to improve legal clarity and user trust.
  3. Establish and publicize a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  4. Enhance accessibility features to improve usability for all users.
  5. Regularly audit third-party scripts and dependencies to mitigate potential vulnerabilities.

Contact details published on the site

Addresses
Legal name
Pūķarags
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Pūķarags
Description
Pūķarags ir atpūtas komplekss Baltijas jūras krastā, Papes dabas parka teritorijā, kas, pateicoties savam izvietojumam, piedāvā īpašu un neaizmirstamu atpūtu tā apmeklētājiem.
Key services
Accommodation, Beach access, Volleyball, Virtual tours
Content quality
good
Branding
consistent

Technology

Stack
Nuxt.js, Vue.js, Google Maps API
Frameworks
Vue.js, Nuxt.js
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • Secure contact forms

Analytics and tracking

Tracking level
minimal
Privacy practices
good

Advertising

Transparency
poor

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. WHOIS data unavailable due to query limit error; domain registration details unknown.
  3. Privacy and cookie policies are present and GDPR compliant.
  4. Contact information is complete and includes phone, email, physical address, and contact form.
  5. No terms of service or security policy pages found.
  6. No incident response or vulnerability disclosure information available.
  7. Website uses modern JavaScript frameworks (Nuxt.js, Vue.js) and Google Maps API.
  8. No advertising or tracking scripts detected beyond Google Maps.
  9. Content is relevant to hospitality and tourism, safe for general audiences.
  10. Security posture is good with HTTPS but lacks some security headers.
Technical notes

Notes

The website is built using modern JavaScript frameworks Nuxt.js and Vue.js, indicating a contemporary front-end architecture. It integrates Google Maps API for location services and uses lazy loading for images to improve performance. The site is moderately optimized with preloading of scripts and stylesheets. Mobile optimization is good, and navigation is clear and user-friendly. However, there is no detected CMS or hosting provider information. The site could improve SEO and accessibility features further. No major technical debt or risks were identified, but security header implementation and performance tuning could enhance overall robustness.
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 pukarags.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 pukarags.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.