Skip to main content

Security report for balticseaculinary.com

Other · N/a

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

Security score

47/100

Risk levelHigh

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

Baltic Sea Culinary Routes is a regional cultural project website dedicated to promoting the culinary heritage and traditions of countries surrounding the Baltic Sea. The site offers rich content including country-specific culinary descriptions, recipes, chef testimonials, and project documentation aimed at strengthening regional identity and supporting rural vitality through culinary tourism. The target audience includes tourists, culinary enthusiasts, chefs, and cultural stakeholders interested in Baltic Sea cuisine. Technically, the website employs a traditional tech stack with jQuery 1.8.1, jQuery UI, and several JavaScript libraries for UI components and sliders. The site is mobile responsive and has a clear navigation structure, but uses outdated JavaScript libraries that pose security risks. SEO and accessibility are basic but functional. No CMS or hosting provider details are explicitly detected. From a security perspective, the site uses HTTPS and has domain transfer protections, but lacks DNSSEC and security headers such as Content-Security-Policy or X-Frame-Options. The use of outdated jQuery versions introduces potential vulnerabilities. No privacy or cookie policies are present, indicating compliance gaps with GDPR. No contact emails or incident response information is provided, limiting transparency and user trust. Overall, the website is functional and content-rich with moderate business credibility but has notable security and privacy compliance shortcomings. Strategic improvements in security headers, library updates, and privacy policy implementation are recommended to enhance trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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. 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';…

  2. GDPR outside view

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

    • 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

Need hands-on remediation? Email guard@offseq.com

Keep watching balticseaculinary.com

This scan found 27 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
72
Security headers
20
Email security
55
DNS health
80
Network security
20
GDPR outside view
35
Average
47

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 Baltic Sea Culinary Routes project operates as a non-profit cultural initiative promoting culinary tourism and regional identity among Baltic Sea countries. Its niche market position leverages cooperation among ten countries, offering unique culinary content and fostering cross-border cultural exchange. The business model focuses on information dissemination, culinary event promotion, and regional branding rather than direct commercial sales. Growth potential lies in expanding digital presence and partnerships with tourism stakeholders. The project is supported by the CBSS Project Support Facility, indicating institutional backing. However, lack of direct contact information and formal business credentials limits commercial credibility.

Security posture

The website demonstrates a basic security posture with HTTPS enabled and domain transfer protection. However, the absence of DNSSEC and security headers reduces resilience against DNS spoofing and clickjacking attacks. The use of an outdated jQuery version (1.8.1) is a significant vulnerability, exposing the site to known exploits. No privacy or cookie policies are present, indicating non-compliance with GDPR requirements. The lack of incident response contacts and security policies further weakens the security culture. No analytics or tracking scripts reduce privacy risks but also limit user behavior insights. Overall, the security maturity is low to moderate, requiring urgent updates to libraries and implementation of security best practices.

Recommendations

  1. Update all JavaScript libraries, especially jQuery, to the latest secure versions to mitigate known vulnerabilities.
  2. Implement DNSSEC to enhance domain name system security and prevent DNS spoofing.
  3. Add comprehensive privacy and cookie policies to comply with GDPR and inform users about data practices.
  4. Deploy security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to protect against common web attacks.
  5. Provide clear contact information including incident response or abuse contacts to improve transparency and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
The website promotes the Baltic Sea Culinary Routes project, focusing on culinary traditions, recipes, and cultural food heritage of countries around the Baltic Sea. It aims to strengthen regional identity and preserve rural vitality through culinary tourism and cooperation.
Key services
Information on Baltic Sea cuisine, Country-specific culinary content, Recipes, Gallery and culinary events, Project documentation and reports
Content quality
good
Branding
consistent

Technology

Stack
jQuery 1.8.1, jQuery UI, Slick Carousel, Swipebox, ResponsiveSlides, Retina.js
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
55/100
Good practices seen
  • HTTPS enabled (implied by base href https://)
  • Domain status clientTransferProhibited

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 a cultural and culinary project site with rich content about Baltic Sea region cuisine.
  2. No privacy, cookie, or terms of service policies found, indicating compliance gaps.
  3. No contact emails or phone numbers explicitly provided on the homepage or footer.
  4. Uses outdated JavaScript libraries which may pose security risks.
  5. No visible security headers or advanced security configurations detected.
  6. No analytics or tracking scripts detected, indicating minimal user tracking.
  7. Navigation is clear with multiple country and recipe sections.
  8. No advertising or marketing scripts detected.
  9. WHOIS data is consistent and domain is well maintained.
Technical notes

Notes

The website uses a traditional front-end stack with jQuery 1.8.1, jQuery UI, Slick Carousel, Swipebox, and ResponsiveSlides for UI and interactive elements. The HTML structure is valid and includes meta tags for SEO and Open Graph for social sharing. The site is mobile responsive and uses Google Fonts for typography. No modern frameworks like React or Angular are detected, indicating a legacy or custom CMS platform. Performance is moderate with no explicit optimization scripts detected. Accessibility is basic with some semantic HTML but no ARIA roles or advanced features. The site lacks analytics or tracking scripts, indicating minimal user data collection. Hosting provider details are not disclosed. Overall, the technical infrastructure is functional but dated, with modernization opportunities to improve security and performance.
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 balticseaculinary.com. 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 balticseaculinary.com.

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.