Skip to main content

Security report for picaguru.lv

PicaGuru · Hospitality · Latvia

Medium risk. 6 critical or high findings in Email security, Security headers and 2 other checks.

Security score

68/100

Risk levelMedium

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

PicaGuru is a small local restaurant based in Riga, Latvia, specializing in pizza delivery and takeaway services. The website provides a comprehensive menu with detailed pizza options, drinks, and beers, supported by images and pricing. The business targets local customers seeking convenient food delivery and takeaway options. Technically, the website is built on a modern Next.js and React stack, hosted via a CDN, and optimized for mobile devices. Security posture is adequate with HTTPS enabled, though security headers are missing, and no advanced security policies are visible. Privacy and cookie policies are present, indicating basic GDPR compliance. Overall, the site is professional and trustworthy for its business type, though WHOIS data is unavailable due to query limits, limiting domain legitimacy verification.

Scanned

NIS2 and GDPR posture

GDPR outside view
68/ 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. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

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

  3. GDPR outside view

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

    • 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

  4. 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 picaguru.lv

This scan found 23 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
52
Security headers
50
Email security
60
DNS health
75
Network security
100
GDPR outside view
68
Average
68

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

PicaGuru operates in the hospitality sector focusing on pizza delivery and takeaway in Riga. The business model is direct-to-consumer food service with online ordering capabilities. The website's detailed menu and social media presence on Facebook support customer engagement. The company appears to be a small-sized local restaurant without visible parent or subsidiary companies. The use of a third-party platform for client login suggests reliance on external service providers for order management. The market position is local with no evident expansion or partnership domains. The business benefits from clear contact information and consistent branding, supporting customer trust and operational transparency.

Security posture

The website enforces HTTPS, ensuring encrypted communication. However, the absence of security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options reduces defense-in-depth. No forms or input fields are present on the main site, minimizing attack surface. No visible vulnerabilities or exposed sensitive data were detected. Privacy policies are present but no dedicated incident response or vulnerability disclosure mechanisms were found. The security posture is moderate, suitable for a small restaurant, but could be improved by implementing recommended security headers and a security.txt file for vulnerability reporting.

Recommendations

  1. Implement standard security headers (CSP, X-Frame-Options, X-Content-Type-Options) to enhance protection against common web attacks.
  2. Add a security.txt file to facilitate responsible vulnerability disclosure and improve security transparency.
  3. Enhance privacy compliance by adding a cookie consent mechanism to comply with GDPR cookie requirements.
  4. Regularly review and update privacy and cookie policies to maintain compliance with evolving regulations.
  5. Consider integrating analytics with privacy-respecting configurations to better understand user behavior while maintaining compliance.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
PicaGuru
Description
PicaGuru is a restaurant located in Riga, Latvia offering pizza delivery and takeaway services. The website presents a menu of pizzas, drinks, and beers with detailed options and pricing.
Key services
Pizza delivery, Takeaway orders, Online menu browsing
Content quality
good
Branding
consistent

Technology

Stack
Next.js, React, Google Fonts, Sentry (error tracking)
Frameworks
Next.js
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
Sentry
Transparency
basic

Site quality

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

Key observations

  1. Website content is fully accessible and not blocked by WAF or security mechanisms.
  2. WHOIS data unavailable due to query limit error; no registrar or domain age info extracted.
  3. Clear contact information including phone, email, and physical address present in footer.
  4. Privacy, cookie, and terms of service policies are present and linked in footer.
  5. Website uses modern Next.js framework and React technology.
  6. No visible security headers detected; HTTPS is enabled.
  7. No forms detected in the main HTML content; login link points to external client portal.
  8. Social media presence limited to Facebook.
  9. Menu is detailed with images, prices, and options, indicating good content quality.
  10. No signs of adult or NSFW content; content is safe for general audiences.
Technical notes

Notes

The website uses Next.js and React frameworks, leveraging server-side rendering and client-side hydration for performance and SEO benefits. Google Fonts are used for typography, and media assets are served via a CDN for optimized delivery. The site is mobile responsive with good navigation clarity and user experience. Hosting is via choiceqr.com CDN, indicating reliance on a third-party platform for content delivery and order management. Performance is moderate with no major issues detected. Accessibility features are basic, with room for improvement in ARIA roles and keyboard navigation. SEO is basic with meta tags and Open Graph data present but could be enhanced with structured data markup for local business and menu items.
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 picaguru.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 picaguru.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.