Skip to main content

Security report for papi.hu

Papi · Hospitality · Hungary

Medium risk. 7 critical or high findings in GDPR outside view and Security headers.

Security score

57/100

Risk levelMedium

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

Papi.hu is a small hospitality business website focused on transforming a family legacy into a farm and restaurant experience in Hungary. The website content centers around a personal story of the founder and his father, emphasizing heritage and love. The business is positioned as an emerging local hospitality venue with a unique cultural narrative. Technically, the site is built on Webflow with modern technologies such as Weglot for multilingual support and Google Tag Manager for analytics. Performance is moderate with a load time of approximately 4.5 seconds. Security posture is basic with HTTPS enabled and modern TLS protocols supported, but lacks advanced security headers, DMARC, and HSTS configurations. Privacy compliance is weak due to the absence of privacy and cookie policies. No contact information or forms are present on the homepage, limiting direct communication channels. Overall, the site is professional and consistent in branding but could improve in security and compliance aspects.

Scanned

NIS2 and GDPR posture

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

7 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

    • 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

  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 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 papi.hu

This scan found 21 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
87
Security headers
30
Email security
50
DNS health
75
Network security
100
GDPR outside view
0
Average
57

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 papi.hu, from OffSeq Breach.

No leaked records found

Breach holds no records for papi.hu 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

The business operates in the hospitality sector, targeting local and regional visitors interested in cultural and dining experiences. Its competitive advantage lies in the unique family story and transformation of a riding school into a restaurant and garden. The business model focuses on experiential hospitality services. The website leverages modern web technologies but lacks comprehensive compliance and security features. There is no evidence of partnerships or subsidiaries. Growth potential exists as the business prepares to open and establish itself as a notable venue in the Dunakanyar region.

Security posture

The website demonstrates a basic security posture with HTTPS enabled and support for TLS 1.3 and 1.2, and no known SSL vulnerabilities detected. However, it lacks important security headers such as HSTS, Content-Security-Policy, and OCSP stapling. Email security is weak due to the absence of DMARC records. No incident response or security policy information is published. The lack of privacy and cookie policies indicates non-compliance with GDPR requirements. No forms or input fields reduce the risk of injection vulnerabilities but also limit user interaction. Overall, the security maturity is low to moderate with room for significant improvements.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie consent mechanism to improve GDPR compliance.
  2. Add security headers including HSTS with preload, Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Configure DMARC DNS records to enhance email security and prevent spoofing.
  4. Enable OCSP stapling on the SSL certificate to improve revocation checking performance and security.
  5. Provide clear contact information and consider adding a security or incident response contact channel to improve trust and readiness.
Technical notes

Notes

The website is built using Webflow CMS platform, leveraging Google Fonts and Weglot for multilingual support. It uses Google Tag Manager for analytics and jQuery for JavaScript functionality. Hosting appears to be via Cloudflare or a similar CDN provider, inferred from IP addresses and DNS records. The site loads 26 resources with a total page size of approximately 139 KB and a load time of 4.5 seconds, indicating moderate performance. The site is mobile optimized with responsive design. SEO optimization is basic with meta viewport and title tags present but no Open Graph or structured data detected. Accessibility features are minimal but present. Technical debt is low given the use of modern frameworks, but security and compliance technical implementations need enhancement.
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 papi.hu. 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 papi.hu.

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.