Skip to main content

Security report for 1805.cz

Bitva u Slavkova (Austerlitz) 1805 · Other · Czech Republic

High risk. 9 critical or high findings in GDPR outside view, Email security and 3 other checks.

Security score

45/100

Risk levelHigh

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

The website www.1805.cz is dedicated to the historical reenactment and commemoration of the Battle of Austerlitz (Bitva u Slavkova) from 1805. It serves as a cultural and educational platform targeting history enthusiasts, tourists, and the general public interested in European history. The site provides event programming, photo galleries, and historical information, supported by a network of regional partners and municipalities. The business model is non-profit and focused on cultural heritage promotion with a small organizational size based in the Czech Republic. Technically, the website is built on WordPress with a modern tech stack including Bootstrap, jQuery, and various plugins for UI enhancements and SEO optimization. The site is mobile-optimized and performs moderately well, with good SEO practices implemented via the Yoast SEO plugin. Analytics are handled through Google Analytics and Google Tag Manager, with a cookie consent mechanism in place. From a security perspective, the site uses HTTPS and has no visible exposed sensitive data. However, it lacks important security headers and does not provide explicit security policies or incident response contacts. The absence of WHOIS data for the domain is a concern for domain legitimacy verification, although the active social media presence and partner affiliations support its authenticity. Overall, the website is professionally maintained with good content quality and user experience. The main risks relate to incomplete privacy and security disclosures and the missing WHOIS information. Strategic improvements in security headers, privacy policy publication, and domain registration transparency would enhance trust and compliance.

Scanned

NIS2 and GDPR posture

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

  2. 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

  3. 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 1805.cz

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
60
DNS health
75
Network security
20
GDPR outside view
40
Average
45

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 1805.cz, from OffSeq Breach.

No leaked records found

Breach holds no records for 1805.cz 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 website operates in the cultural heritage and historical reenactment sector, focusing on the Battle of Austerlitz. It holds a regional market position with international participant involvement and partnerships with local municipalities and historical societies. The business model is event-driven, relying on partnerships and community engagement rather than commercial revenue streams. The target audience includes history buffs, tourists, and educational groups. The partnership ecosystem is robust, including official sites like the Austerlitz project and local castles. Growth indicators include annual event updates and active social media channels. The organization appears small but well-networked within its niche.

Security posture

The current security posture is moderate. The site enforces HTTPS and uses cookie consent banners, indicating awareness of privacy requirements. However, it lacks critical security headers such as Content-Security-Policy and X-Frame-Options, which are important for mitigating common web attacks. No security.txt or incident response information is published, limiting transparency for vulnerability reporting. The absence of WHOIS data reduces domain trustworthiness. There are no visible vulnerabilities or exposed sensitive data, but the site would benefit from enhanced security practices and compliance documentation to improve its security maturity.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Strict-Transport-Security.
  2. Publish a clear and accessible privacy policy and terms of service pages to improve compliance and user trust.
  3. Add a security.txt file to facilitate responsible vulnerability disclosure and incident reporting.
  4. Verify and update WHOIS domain registration information to improve legitimacy and trust.
  5. Enhance accessibility features to meet recognized standards and improve user experience for all visitors.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Bitva u Slavkova (Austerlitz) 1805
Description
Bitva u Slavkova - Austerlitz 1805, živá rekonstrukce a připomínka historie. Připomeňte si spolu s účastníky vojensko-historických klubů z celého světa významnou epochu evropských dějin. Podívejte se na program.
Key services
historical reenactment events, cultural heritage promotion, event programming and coordination, photo galleries and historical information dissemination
Content quality
good
Branding
consistent

Technology

Stack
WordPress 5.8.12, jQuery 3.6.0, Bootstrap 4 (CSS and JS), Slick Slider, AOS (Animate On Scroll), LazyLoad, Magnific Popup, Selectric, BasicTable, Yoast SEO plugin
Frameworks
Bootstrap
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of Google Analytics with async loading
  • Cookie consent banner implemented

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content about the Battle of Austerlitz historical reenactment.
  2. No WHOIS data available, which is a concern for domain legitimacy verification.
  3. No explicit privacy policy or terms of service pages found.
  4. Cookie consent banner is present and functional.
  5. Multiple social media channels are linked and active.
  6. Website uses modern web technologies and is mobile optimized.
  7. No security.txt or incident response information found.
  8. No contact emails or phone numbers explicitly provided on the homepage.
  9. Content is safe and suitable for general audiences.
  10. SEO and structured data are well implemented via Yoast SEO plugin.
Technical notes

Notes

The website uses a well-established CMS platform (WordPress) with a modern front-end stack including Bootstrap for responsive design and jQuery for interactivity. It integrates several plugins for enhanced UI components such as sliders, popups, and animations. SEO is managed via the Yoast SEO plugin, with structured data implemented in JSON-LD format for rich search results. Performance is moderate, with lazy loading of images and asynchronous loading of analytics scripts. The site is mobile-friendly and uses Google Fonts. There is no indication of hosting provider from the HTML content. Technical risks include potential outdated plugins or themes if not regularly updated, and missing security headers that could expose the site to certain web vulnerabilities.
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 1805.cz. 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 1805.cz.

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.