Skip to main content

Security report for mirekbenes.cz

Mirek Beneš · Technology · Czech Republic

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

Security score

45/100

Risk levelHigh

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

Mirek Beneš operates as a freelance frontend developer based in the Czech Republic, offering specialized services in HTML template coding, JavaScript programming, WordPress development, graphic design, and email newsletter coding. The website serves as a professional portfolio showcasing client references and detailed service offerings, targeting businesses and clients across the Czech Republic seeking quality frontend development and web design solutions. The business model is focused on external collaboration and contract work, with a clear emphasis on usability and modern web standards. Technically, the website is well-constructed using modern web technologies including HTML5, CSS3, SVG graphics, and JavaScript libraries such as Swiper.js for carousels. The site is mobile-optimized, fast-loading, and SEO-friendly, with minimal but privacy-conscious analytics implemented via Plausible Analytics. However, there is no detected CMS or hosting provider information, and no advanced frameworks are identified. From a security perspective, the site uses HTTPS and does not expose sensitive data. However, it lacks explicit security headers and formal privacy or cookie policies, which are important for GDPR compliance and user trust. There is no visible incident response or vulnerability disclosure information, which could be improved to enhance security posture and transparency. Overall, the website presents a professional and trustworthy image for a small freelance business but would benefit from improved privacy compliance and security best practices. The absence of WHOIS data reduces domain trustworthiness slightly, but the content quality and business transparency mitigate this concern. Strategic recommendations include implementing privacy and cookie policies, adding security headers, and publishing incident response contacts to strengthen compliance and security.

Scanned

NIS2 and GDPR posture

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

12 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 mirekbenes.cz

This scan found 22 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
52
Security headers
35
Email security
65
DNS health
70
Network security
20
GDPR outside view
25
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

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 is positioned as a specialized freelance frontend developer serving clients primarily in the Czech Republic. Competitive advantages include a focus on modern web standards, usability, and a broad service offering covering coding, design, and WordPress development. Revenue streams likely come from project-based contracts and external collaborations. The target customer segments are businesses and organizations needing professional web presence and frontend solutions. Growth indicators include a portfolio of reputable clients and a professional online presence. The partnership ecosystem is limited to client relationships, with no detected subsidiaries or parent companies. Strategic observations suggest maintaining a strong portfolio and expanding privacy and security compliance to enhance market trust.

Security posture

The current security maturity level is moderate. The site uses HTTPS, which is mandatory, and avoids exposing sensitive information. However, the lack of security headers such as Content Security Policy, X-Frame-Options, and HSTS reduces protection against common web attacks. No vulnerability disclosure or incident response information is provided, limiting transparency and preparedness. GDPR compliance is incomplete due to missing privacy and cookie policies. Data protection practices appear minimal but adequate for the business scale. Incident response readiness is not evident. Overall, the security culture appears basic but can be improved with formal policies and technical enhancements.

Recommendations

  1. Implement comprehensive privacy and cookie policies to ensure GDPR compliance.
  2. Add standard security headers (CSP, HSTS, X-Frame-Options) to improve site security.
  3. Publish incident response and vulnerability disclosure contacts to enhance transparency.
  4. Regularly audit and update third-party scripts and dependencies to avoid vulnerabilities.
  5. Consider adding a security.txt file and formal data protection officer contact information.

Contact details published on the site

Addresses
Legal name
Mirek Beneš
Registration number
IČ: 87797330
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Mirek Beneš
Description
Připravuji kvalitní šablony a weby s použitím moderních technologií. Externí spolupráce pro celou ČR.
Key services
HTML template coding, JavaScript programming, WordPress development, Graphic design, Newsletter and email coding
Content quality
excellent
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, SVG, Swiper.js carousel
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS usage implied by URL
  • No visible exposed sensitive data

Analytics and tracking

Services
Plausible Analytics
Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
plausible.mirekbenes.cz
Marketing tools
Plausible Analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is a professional portfolio for a Czech frontend developer.
  2. No WHOIS data available, possibly due to domain not registered or privacy protection.
  3. No privacy or cookie policies found, which is a compliance gap.
  4. Contact information is clearly provided with email, phone, and physical address.
  5. No forms detected on the website for data collection.
  6. Uses modern web technologies and good SEO practices.
  7. Minimal tracking via Plausible Analytics, respecting privacy.
  8. No security incident or vulnerability disclosure information present.
Technical notes

Notes

The website is built with clean, modern HTML5 and CSS3, incorporating SVG graphics and JavaScript for interactive elements like carousels. It uses external fonts from Adobe Typekit and minimal external scripts, including Plausible Analytics for privacy-focused tracking. The site is mobile responsive and optimized for performance with minified CSS and JS files. No CMS or backend platform is detected, indicating a static or custom-coded site. Hosting provider details are not available. The technical implementation is solid with good SEO and accessibility considerations, but security headers and formal privacy mechanisms are missing, representing technical debt and compliance risks.
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 mirekbenes.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 mirekbenes.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.