Skip to main content

Security report for finblog.cz

Finance · Czech Republic

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

Security score

39/100

Risk levelHigh

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

Finblog.cz is a Czech financial information website established in 2018, providing articles and advice on public finances, loans, mortgages, and investments. The site targets Czech-speaking individuals seeking financial guidance. It operates on WordPress CMS using the Newspaper theme, with integration of Google services such as Google Fonts and Google Tag Manager. The website demonstrates a moderate level of digital maturity with good content quality and mobile optimization. Security posture is adequate with HTTPS enabled and secure login forms, but lacks advanced security headers and explicit privacy or cookie policies. Overall, the site is legitimate and trustworthy for its niche but would benefit from enhanced privacy compliance and security best practices.

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

11 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 finblog.cz

This scan found 30 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
15
Email security
55
DNS health
80
Network security
20
GDPR outside view
10
Average
39

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 website positions itself as a niche financial blog serving the Czech market, focusing on financial education and advice. Its business model relies on content publishing and advertising partnerships with related Czech websites. The site shows consistent branding and professional content, appealing to individuals interested in finance and investments. The domain age and WHOIS data support its legitimacy. However, the absence of detailed company information and contact phone numbers limits full business transparency. The partnership ecosystem includes several Czech media and finance-related domains, indicating a networked approach to content and advertising.

Security posture

The website employs HTTPS and secure login forms, which are positive security indicators. However, it lacks visible security headers such as Content-Security-Policy, X-Frame-Options, and X-XSS-Protection, which are recommended to mitigate common web vulnerabilities. No vulnerabilities or exposed sensitive data were detected in the HTML content. The absence of a vulnerability disclosure policy and incident response contact channels suggests limited preparedness for security incidents. Privacy compliance is weak due to missing privacy and cookie policies. Overall, the security posture is moderate but can be improved by implementing recommended headers, policies, and incident response mechanisms.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie consent mechanism to improve GDPR compliance.
  2. Add security headers like Content-Security-Policy, X-Frame-Options, and X-XSS-Protection to enhance protection against common attacks.
  3. Establish a vulnerability disclosure policy and provide clear incident response contact information.
  4. Enhance accessibility features to improve usability for all users.
  5. Regularly update WordPress core, themes, and plugins to mitigate security risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Finblog.cz is a Czech financial magazine website providing articles and information about public finances, loans, mortgages, investments, money management, and financial advice.
Key services
Financial articles, Advice on loans and mortgages, Investment information, Financial guides and tutorials
Content quality
good
Branding
consistent

Technology

Stack
WordPress, jQuery, Google Fonts, Site Kit by Google
Frameworks
Newspaper WordPress Theme
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Secure login forms with password fields

Analytics and tracking

Services
Google Analytics (via Site Kit)
Tracking level
moderate
Privacy practices
poor

Advertising

Marketing tools
Site Kit by Google
Transparency
basic

Site quality

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

Key observations

  1. Website is a Czech financial blog with active content and regular updates
  2. No explicit privacy or cookie policies found
  3. Login forms present but no visible multi-factor authentication or advanced security notices
  4. Uses WordPress CMS with Newspaper theme and common plugins
  5. No visible security headers detected in HTML content
  6. External links mostly to related Czech sites and Google services
  7. No suspicious or malicious content detected
  8. No phone numbers or physical addresses explicitly provided
  9. Social media links present but URLs are placeholders or generic
Technical notes

Notes

The website is built on WordPress CMS with the Newspaper theme, leveraging jQuery and Google Fonts for frontend functionality and styling. It uses Site Kit by Google for analytics integration. The site is mobile optimized with responsive design and good navigation clarity. Performance is moderate, with potential for improvement through optimization of assets and caching. The technical implementation is standard for content publishing sites but lacks advanced accessibility features and security headers. Hosting provider details are limited to the registrar REG-WEDOS, a Czech domain registrar, with no explicit hosting provider identified.
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 finblog.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 finblog.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.