Skip to main content

Security report for obshtini.bg

Government · Bulgaria

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

Security score

59/100

Risk levelMedium

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

The website obshtini.bg serves as a centralized portal providing access to municipal normative acts for various Bulgarian municipalities. It primarily functions as a gateway linking to municipality-specific subdomains such as Sofia, Varna, Plovdiv, and others. The site targets residents and officials seeking local government legal documents. Technically, the site is built using Angular 9 with PrimeNG components, indicating a modern frontend framework, though some legacy scripts like jQuery are commented out. The site demonstrates basic mobile optimization and moderate performance but lacks advanced SEO and accessibility features. Security posture is moderate; HTTPS is assumed but no security headers were detected in the provided data, and no privacy or cookie policies are present, which impacts compliance. The WHOIS data is privacy protected due to GDPR, typical for domains related to government or public services in the EU, and the domain appears legitimate and active. Overall, the site is functional and safe but would benefit from enhanced security headers, privacy compliance, and contact transparency to improve trust and compliance.

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

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

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

This scan found 25 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
82
Security headers
15
Email security
70
DNS health
60
Network security
100
GDPR outside view
25
Average
59

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

Obshtini.bg occupies a niche position as a government-related information portal aggregating municipal normative acts for Bulgarian municipalities. Its business model is informational, serving public sector transparency and citizen access to legal documents. The site likely operates with limited commercial intent, focusing on public service. The target audience includes municipal officials, legal professionals, and residents interested in local regulations. The lack of visible business or contact information suggests a small-scale operation or a government-managed service. The site’s partnership ecosystem is limited to municipality subdomains, with no evident commercial partnerships or advertising. Growth indicators are not visible from the site content. The portal’s competitive advantage lies in centralized access to multiple municipalities’ legal acts, which may not be widely available elsewhere online.

Security posture

The security maturity of obshtini.bg is moderate. The site uses HTTPS (assumed from URL), but no security headers such as Content-Security-Policy or X-Frame-Options were detected, which are important for mitigating common web attacks. No forms or input fields were found, reducing attack surface, but also limiting user interaction. The absence of privacy and cookie policies indicates compliance gaps with GDPR and related regulations. No incident response or security contact information is provided, which reduces transparency and readiness perception. No vulnerable libraries or exposed sensitive data were detected in the provided content. Overall, the site would benefit from implementing standard security headers, publishing privacy and cookie policies, and providing clear contact channels for security incidents to enhance trust and compliance.

Recommendations

  1. Implement and enforce HTTPS with strong SSL/TLS configuration and regularly monitor certificate validity.
  2. Add standard security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to improve protection against common web vulnerabilities.
  3. Publish comprehensive privacy and cookie policies to comply with GDPR and inform users about data handling practices.
  4. Provide clear contact information including security incident response contacts to improve transparency and trust.
  5. Enhance SEO and accessibility features to improve user experience and reach.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
The website provides access to municipal normative acts for various Bulgarian municipalities such as Sofia, Petrich, Varna, Plovdiv, and others. It serves as a portal linking to subdomains dedicated to different municipalities.
Key services
Access to municipal normative acts, Links to municipality-specific portals
Content quality
basic
Branding
moderate

Technology

Stack
Angular 9.0.6, PrimeNG, jQuery (commented out), JavaScript
Frameworks
Angular
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
50/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is an Angular-based portal linking to multiple municipality subdomains.
  2. No visible privacy, cookie, or terms of service policies found.
  3. No contact emails, phone numbers, or social media links detected.
  4. No security headers detected in provided data; SSL status unknown.
  5. No advertising or analytics scripts detected.
  6. Content is safe and targeted at general public interested in municipal legal acts.
Technical notes

Notes

The website is built on Angular 9, a modern frontend framework, using PrimeNG UI components. The presence of commented-out jQuery scripts suggests some legacy code or phased migration. The site loads multiple JavaScript bundles asynchronously, indicating modular design. The HTML structure is semantic but minimal, with no meta description or Open Graph tags detected, limiting SEO effectiveness. The site is mobile responsive with viewport meta tag and inline styles for layout. No CMS or backend technology is identifiable from the frontend content. Hosting provider and server details are not available. Performance is moderate based on script loading patterns and minimal content. Accessibility is basic with no ARIA roles or landmarks detected. Overall, the technical infrastructure is modern but could be improved with better SEO, accessibility, and security practices.
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 obshtini.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 obshtini.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.