Skip to main content

Security report for mon.bg

Other · N/a

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

Security score

63/100

Risk levelMedium

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

The website mon.bg is currently inaccessible due to a Cloudflare Turnstile CAPTCHA challenge page, which blocks direct access to any business content or services. The domain is active and uses Cloudflare nameservers with DNSSEC enabled, indicating a level of security awareness. However, the lack of accessible content prevents a full assessment of the company's business operations, services, or market positioning. No privacy, cookie, or terms of service policies are visible, and no contact information is provided on the landing page. The technical infrastructure relies on Cloudflare's security and CDN services, but no further technology stack details are available due to content blocking. Security posture is limited to the presence of Cloudflare protection, with no additional security headers or policies detected. Overall, the site presents a low trust profile due to the absence of accessible information and transparency.

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

8 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

    • 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

  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 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 mon.bg

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. 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
75
Security headers
55
Email security
75
DNS health
65
Network security
100
GDPR outside view
10
Average
63

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

Due to the content being blocked by a security challenge, no direct business intelligence can be gathered from the website. The domain appears to be registered and active but lacks publicly available information about its business model, target audience, or market position. The use of Cloudflare suggests a focus on security and performance, but no partnerships, subsidiaries, or certifications are evident. Without accessible content or metadata, insights into revenue streams, customer segments, or competitive advantages cannot be determined.

Security posture

The website benefits from Cloudflare's security services, including DNSSEC and a CAPTCHA challenge to mitigate automated threats. However, the absence of visible security headers, privacy policies, or incident response contacts limits the assessment of its overall security maturity. The domain WHOIS data is privacy protected, which is common but reduces transparency. No vulnerabilities or exposed sensitive data are observable due to the blocked content. The security posture is moderate at best, relying heavily on Cloudflare's protections without visible internal security controls or disclosures.

Recommendations

  1. Provide a publicly accessible landing page with clear business and contact information.
  2. Publish comprehensive privacy, cookie, and terms of service policies to improve compliance and trust.
  3. Implement and disclose security headers and best practices beyond Cloudflare protections.
  4. Offer clear incident response and security contact channels to enhance transparency.
  5. Ensure SEO and accessibility improvements once content is accessible to improve user experience and discoverability.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. Website is behind Cloudflare WAF with Turnstile CAPTCHA challenge page blocking direct content access. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor

Technology

Stack
Cloudflare Turnstile, Cloudflare CDN

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is inaccessible due to Cloudflare Turnstile CAPTCHA challenge
  2. No visible business or contact information on the landing page
  3. No privacy, cookie, or terms of service policies found
  4. No forms or data collection fields detected
  5. Only external link is to Cloudflare domain
  6. No analytics or marketing scripts detected
  7. No social media or contact emails found
  8. Website likely uses Cloudflare for security and CDN
  9. No visible security headers or SSL info available from provided data
  10. WHOIS data is minimal and privacy protected
Technical notes

Notes

The website is hosted behind Cloudflare, utilizing their CDN and security services including DNSSEC and Turnstile CAPTCHA. No CMS or additional frameworks are detectable due to the content being blocked. The HTML is minimal and primarily serves the security challenge. Performance and mobile optimization cannot be assessed. The technical debt or modernization opportunities cannot be evaluated without access to the actual site content or backend technologies.
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 mon.bg. 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 mon.bg.

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.