Skip to main content

Security report for milev.hu

Hungarian Jewish Museum and Archives · Non-profit · Hungary

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

Security score

59/100

Risk levelMedium

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

The Hungarian Jewish Museum and Archives is a well-established non-profit cultural institution founded in 1909, dedicated to preserving and presenting Jewish heritage in Hungary. The website serves as a portal for museum exhibitions, archival research, genealogy, and educational projects, targeting researchers, historians, and the general public interested in Jewish history. The institution maintains a strong social media presence and offers multilingual content in Hungarian, English, and Hebrew. Technically, the website is built on the Weebly platform, leveraging common web technologies such as jQuery and Google Analytics, with embedded calendar and lead form functionalities. While the site enforces HTTPS and avoids exposing sensitive data, it uses an outdated jQuery version and lacks some modern security headers, indicating room for improvement in security posture. Privacy compliance is basic, with a child protection policy available but no explicit cookie consent mechanism. Overall, the site is professional, trustworthy, and content-rich, but could enhance security and privacy practices to align with best standards.

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

9 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 milev.hu

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
62
Security headers
20
Email security
85
DNS health
75
Network security
100
GDPR outside view
10
Average
59

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 museum occupies a niche market position as one of the oldest Jewish museums globally, focusing on Hungarian Jewish culture and history. Its business model is non-profit, relying on grants, donations, and public engagement through exhibitions and research services. The website links to several partner projects and related domains, indicating a collaborative ecosystem. The target audience includes academics, genealogists, and cultural visitors. The museum's digital presence is moderate, with opportunities to modernize technical infrastructure and improve GDPR compliance. The absence of phone contact details on the website suggests a preference for digital communication channels. The institution's longevity and cultural significance provide strong trust signals.

Security posture

The website demonstrates a basic security posture with HTTPS enabled and no visible exposure of sensitive information. However, the use of an outdated jQuery version (1.8.3) introduces potential vulnerabilities. The absence of security headers such as HSTS, X-Frame-Options, and Content Security Policy reduces defense-in-depth. No explicit incident response or security policy pages are found, and no vulnerability disclosure or security.txt files are present. The site lacks a cookie consent mechanism, which may pose compliance risks under GDPR. Recommendations include updating libraries, implementing security headers, and enhancing privacy controls to improve overall security maturity.

Recommendations

  1. Update jQuery and other JavaScript libraries to current secure versions to mitigate known vulnerabilities.
  2. Implement security headers including HSTS, X-Content-Type-Options, and Content Security Policy to strengthen browser security.
  3. Add a clear cookie policy and consent mechanism to comply with GDPR and enhance user privacy transparency.
  4. Publish a security policy and incident response contact information to improve trust and preparedness.
  5. Conduct a privacy audit and ensure all data collection practices are GDPR compliant, including explicit user consent.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Hungarian Jewish Museum and Archives
Description
One of the oldest Jewish museums in the world, founded in 1909, focused on Hungarian Jewish history, archives, exhibitions, research, and collections.
Key services
Museum exhibitions, Archival research, Genealogy research, Educational projects, Publications
Content quality
good
Branding
consistent

Technology

Stack
jQuery 1.8.3, Google Analytics, Stripe.js, Weebly platform scripts, Tockify calendar embed
Platforms
Weebly
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
65/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of Google reCAPTCHA script (though not clearly implemented in forms)

Analytics and tracking

Services
Google Analytics, Snowplow Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Snowplow Analytics
Marketing tools
Weebly lead form, Visitor Analytics, Tockify calendar
Transparency
basic

Site quality

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

Key observations

  1. Website is a cultural and historical museum site with multilingual support (HU, EN, HE).
  2. Content is rich with links to collections, projects, and research resources.
  3. Uses Weebly platform with embedded calendar and lead form.
  4. No explicit privacy or cookie banners detected despite GDPR relevance.
  5. Security practices are basic but HTTPS is enforced.
  6. No visible security.txt or vulnerability disclosure page.
  7. Contact information is available but phone numbers are not explicitly found.
  8. Social media presence is strong with official accounts on Facebook, Twitter, Instagram, Pinterest, and YouTube.
Technical notes

Notes

The website is hosted on the Weebly platform, utilizing standard web technologies such as jQuery, Google Analytics, and Stripe for payment processing. The site includes embedded third-party widgets like Tockify calendar and lead forms. Performance is moderate with a responsive design suitable for mobile devices. SEO optimization is basic with meta tags and Open Graph data present but no advanced structured data like JSON-LD for organization or breadcrumbs. Accessibility features are minimal but functional. The technical stack is stable but could benefit from modernization and enhanced security configurations to reduce technical debt and improve resilience.
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 milev.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 milev.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.