Skip to main content

Security report for aitinlauvas.lv

Aitiņlauvas · Hospitality · Latvia

High risk. 11 critical or high findings in GDPR outside view, Security headers and 2 other checks.

Security score

42/100

Risk levelHigh

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

AitiņLauvas is a small family-owned hospitality business located in Latvia, offering a combination of restaurant (krogs), bistro, guesthouse accommodations, and banquet services. The business emphasizes a hunting lodge atmosphere with a focus on game meat dishes and caters to families, hunters, and tourists in the region near Riga and Jurmala. The website provides detailed menus, accommodation pricing, and contact information, supporting a clear business presence in the hospitality sector. Technically, the website uses a traditional tech stack including jQuery 1.11.1, fullPage.js for navigation, and W3.CSS for styling. While the site is functional and well-structured with good content quality and navigation, it lacks modern security best practices such as updated libraries, security headers, and privacy compliance documentation. No forms or analytics scripts are present, reducing attack surface but also limiting user engagement and data insights. From a security perspective, the site is accessible without WAF or blocking mechanisms, but the use of outdated jQuery and absence of security headers present moderate risks. The lack of privacy and cookie policies indicates compliance gaps with GDPR and related regulations. Contact information is clearly provided, enhancing business credibility. WHOIS data could not be retrieved due to query limits, but no suspicious indicators were found on the site. Overall, the website scores moderately in content quality and business credibility but requires improvements in technical security and privacy compliance to enhance trust and reduce risk. Strategic recommendations include updating JavaScript libraries, implementing security headers, adding privacy and cookie policies, and considering a vulnerability disclosure policy to improve security posture and regulatory compliance.

Scanned

NIS2 and GDPR posture

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

      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. 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

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

This scan found 26 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
62
Security headers
15
Email security
70
DNS health
75
Network security
20
GDPR outside view
10
Average
42

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention aitinlauvas.lv, from OffSeq Breach.

No leaked records found

Breach holds no records for aitinlauvas.lv right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

AitiņLauvas operates in the hospitality sector as a small family business offering a niche experience centered on game meat cuisine and a hunting lodge ambiance. Its market positioning targets local and regional visitors seeking authentic dining and lodging experiences near major Latvian cities. The business model combines on-site restaurant services, bistro lunch offerings, overnight accommodations, and event hosting including banquets and conferences. Revenue streams likely derive from food and beverage sales, room bookings, and event space rentals. The company maintains an active social media presence on Facebook and Instagram, supporting customer engagement and marketing. No partnerships or subsidiaries are evident from the website. Growth indicators are limited but the detailed menu and accommodation info suggest a stable operational setup.

Security posture

The website demonstrates a basic security posture with HTTPS assumed but not explicitly confirmed in the HTML content. The use of an outdated jQuery version (1.11.1) introduces known vulnerabilities that could be exploited if not mitigated. No security headers such as Content-Security-Policy, X-Frame-Options, or X-XSS-Protection are detected, reducing protection against common web attacks. The absence of forms limits data input risks but also reduces user interaction capabilities. No privacy or cookie policies are present, indicating non-compliance with GDPR requirements. No incident response or vulnerability disclosure information is provided, which could hinder timely handling of security issues. Overall, the security maturity is low to moderate, with clear areas for improvement to protect business and customer data.

Recommendations

  1. Update all JavaScript libraries, especially jQuery, to the latest stable versions to mitigate known vulnerabilities.
  2. Implement essential HTTP security headers including Content-Security-Policy, X-Frame-Options, and X-XSS-Protection to enhance protection against web attacks.
  3. Add comprehensive privacy and cookie policies on the website to comply with GDPR and inform users about data handling practices.
  4. Consider deploying a security.txt file or vulnerability disclosure policy to facilitate responsible reporting of security issues.
  5. Ensure HTTPS is enforced site-wide and verify SSL/TLS configuration for strong encryption and trust.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Aitiņlauvas
Description
Krogs, Bistro, naktsmītne, banketi un daudz citu labumu. Ģimenes uzņēmums, kas piedāvā mednieku namiņa atmosfēru, specializējoties uz medījumu gaļas ēdieniem, bistro pusdienu piedāvājumiem, naktsmītnes pakalpojumiem un banketu apkalpošanu.
Key services
Krogs ar medījumu gaļas ēdieniem, Bistro pusdienu piedāvājumi, Naktsmītne ar dažāda izmēra numuriņiem, Banketu un pasākumu apkalpošana
Content quality
good
Branding
consistent

Technology

Stack
jQuery 1.11.1, jquery.fullPage.js, W3.CSS, Google Fonts (Great Vibes, Cuprum)
Frameworks
fullPage.js
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
50/100
Good practices seen
  • No forms detected to collect user input
  • No exposed sensitive data in HTML

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is fully accessible with rich content about hospitality services.
  2. No privacy, cookie, or terms of service policies found, indicating compliance gaps.
  3. No forms present, reducing attack surface but limiting user interaction.
  4. Use of outdated jQuery version is a security concern.
  5. No security headers detected in HTML source.
  6. Contact information is clearly presented with phone, email, and physical address.
  7. Social media links to Facebook and Instagram are present.
  8. No analytics or tracking scripts detected.
  9. No WHOIS data available due to query limit error; domain appears legitimate based on content.
Technical notes

Notes

The website is built using a combination of jQuery 1.11.1, fullPage.js for smooth scrolling navigation, and W3.CSS for styling. Google Fonts are used for typography. The site is a static HTML structure without CMS detected. Performance is moderate with no heavy scripts or analytics slowing load times. Mobile optimization is basic but functional. Accessibility features are minimal but navigation is clear. SEO optimization is basic with meta description and title tags present but no structured data or Open Graph tags detected. Hosting provider and SSL details are not discernible from the HTML content. The site lacks modern JavaScript frameworks or CMS platforms, indicating a traditional web development approach with potential technical debt.
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 aitinlauvas.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 aitinlauvas.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.