Skip to main content

Security report for bermudas.lv

Zivju restorāns "Bermudas" · Hospitality · Latvia

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

Security score

43/100

Risk levelHigh

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

Zivju restorāns "Bermudas" is a small local fish restaurant based in Latvia, offering fish dishes, specialties, banquets, and brunch services. The website serves as an informational platform with basic content, navigation, and social media integration. The business targets local customers interested in fish cuisine and hospitality services. Technically, the website is built on WordPress using common plugins for image sliders and galleries, with jQuery and Google Analytics integrated for functionality and visitor tracking. The site shows moderate performance and basic mobile optimization but lacks advanced SEO and accessibility features. Security posture is moderate with HTTPS usage but no visible security headers or privacy policies, indicating room for improvement in compliance and protection. No WHOIS data was available due to query limits, but the site appears legitimate based on content and social media presence. Overall, the website is functional but would benefit from enhanced security, privacy compliance, and richer business information to improve trust and user experience.

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

10 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 bermudas.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
80
Network security
20
GDPR outside view
10
Average
43

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 restaurant operates in the hospitality sector focusing on fish cuisine in a regional Latvian market. Its business model is traditional dine-in and banquet services with additional offerings like brunch and drinks. The company maintains an active social media presence on Facebook and Instagram, which supports customer engagement and marketing. The website lacks detailed business information such as company registration or VAT numbers, which limits transparency. There are no visible partnerships or subsidiaries linked to the domain. The business appears stable with a consistent brand image but could improve digital maturity by adding privacy policies, contact details, and enhanced SEO to attract a broader audience.

Security posture

The website uses HTTPS, which is a fundamental security requirement. However, no security headers such as Content Security Policy, X-Frame-Options, or HSTS were detected, which could expose the site to certain web-based attacks. There is no evidence of exposed sensitive data or vulnerable libraries in the provided content. The absence of privacy and cookie policies indicates non-compliance with GDPR, which is critical for EU-based businesses. No incident response or security contact information is provided, limiting the ability to report or respond to security issues. The use of Google Analytics without visible cookie consent banners suggests potential privacy compliance gaps. Overall, the security posture is basic and requires improvements to meet modern standards and regulatory requirements.

Recommendations

  1. Implement comprehensive privacy and cookie policies with visible consent mechanisms to ensure GDPR compliance.
  2. Add security headers such as Content Security Policy, X-Frame-Options, and HSTS to enhance protection against common web attacks.
  3. Publish clear contact information including emails and phone numbers for customer support and security incident reporting.
  4. Introduce a security.txt file or vulnerability disclosure policy to facilitate responsible security reporting.
  5. Improve mobile optimization and accessibility to enhance user experience and SEO performance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Zivju restorāns "Bermudas"
Description
A fish restaurant located in Ragaciems, Engures novads, Latvia, offering fish dishes, specialties, banquets, and brunch services.
Key services
Fish dishes, Fish specialties, Banquets, Menu offerings, Drinks, Brunch
Content quality
basic
Branding
consistent

Technology

Stack
jQuery, Google Analytics, Responsive Full Width Background Slider plugin, Colorbox jQuery plugin
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • Use of HTTPS (implied by https URLs)
  • No visible exposed sensitive data

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is a small local fish restaurant site with basic content and navigation.
  2. No privacy, cookie, or terms of service policies found on the site.
  3. No contact emails or phone numbers explicitly provided on the analyzed page.
  4. Social media links to Facebook and Instagram are present and appear legitimate.
  5. No forms detected on the main page; no data collection forms visible.
  6. Uses WordPress CMS with common plugins for sliders and image galleries.
  7. Google Analytics is used for visitor tracking without visible cookie consent.
  8. No security.txt or vulnerability disclosure information found.
  9. No visible security headers detected in provided data.
  10. No WHOIS data available due to query limit error.
Technical notes

Notes

The website is built on WordPress CMS with jQuery and several plugins for UI enhancements like sliders and image galleries. Google Analytics is used for visitor tracking. The site loads multiple CSS and JS resources from its own domain and Google Analytics domain. The HTML structure is basic but functional with meta tags for keywords and viewport settings. There is no evidence of modern frontend frameworks or advanced SEO structured data like JSON-LD or Open Graph tags. Performance is moderate with fixed large background images which may impact load times. Mobile optimization is basic with viewport meta tag but no advanced responsive design detected. Accessibility features are minimal. The site would benefit from modernization including improved SEO metadata, performance optimization, and enhanced accessibility compliance.
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 bermudas.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 bermudas.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.