Skip to main content

Security report for bellcom.ee

Bellcom Estonia · Technology · Estonia

High risk. 9 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

47/100

Risk levelHigh

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

Bellcom Estonia is a small but established technology service provider specializing in custom website development, hosting, and technical support. Founded in 2013, the company serves businesses and organizations seeking agile and innovative digital solutions. Their market position is supported by a portfolio of case studies and client testimonials, emphasizing their expertise in Drupal and other web technologies. Technically, the website is built on Drupal 8 with modern frontend libraries such as Bootstrap and jQuery, and integrates Google Analytics with IP anonymization for user tracking. The site is mobile optimized and presents a professional user experience. Security posture is moderate; while HTTPS usage is assumed but not confirmed, no security headers or explicit security policies are published, representing an area for improvement. Privacy compliance is weak due to the absence of privacy and cookie policies. Overall, the website is credible and trustworthy but would benefit from enhanced security and privacy disclosures.

Scanned

NIS2 and GDPR posture

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

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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  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 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 bellcom.ee

This scan found 23 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
0
Security headers
40
Email security
75
DNS health
65
Network security
100
GDPR outside view
0
Average
47

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

Bellcom Estonia operates in the technology sector, focusing on custom web development and hosting services primarily for regional clients in Estonia and Denmark. Their business model is service-oriented, leveraging expertise in Drupal and related technologies to deliver tailored solutions including webshops, web applications, and hosting support. The company demonstrates a strong client portfolio with municipalities, educational institutions, and commercial clients, indicating a stable market presence. Their partnership ecosystem includes integrations with third-party services and payment providers. Growth indicators include a diverse team with specialized skills and a consistent brand presence. The company’s digital maturity is reflected in their use of modern CMS and analytics tools, though privacy and security compliance require attention.

Security posture

The current security maturity level of Bellcom Estonia’s website is moderate. The site uses Google Analytics with IP anonymization, which is a positive privacy practice. However, the absence of visible security headers such as Content-Security-Policy, X-Frame-Options, and HSTS reduces the overall security posture. No vulnerability disclosure or incident response information is published, which limits transparency and readiness for security incidents. The contact information is clear but lacks dedicated security or abuse contacts. There is no evidence of GDPR compliance mechanisms such as cookie consent banners or privacy policies, which is a compliance gap. The site’s use of Drupal 8 is positive, but regular updates and security audits are recommended to mitigate risks from third-party modules. Overall, the security culture appears basic and would benefit from formalized policies and technical enhancements.

Recommendations

  1. Implement and enforce HTTPS with a strong SSL/TLS configuration to secure all communications.
  2. Publish comprehensive privacy and cookie policies with clear GDPR compliance statements and implement a cookie consent mechanism.
  3. Add essential security headers including Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, and Strict-Transport-Security.
  4. Establish and publish a vulnerability disclosure policy and incident response contact information to improve transparency and security readiness.
  5. Conduct regular security audits and update all CMS components and third-party libraries to mitigate vulnerabilities.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Bellcom Estonia
Description
Our primary competencies are technical advice, agile development, design and implementation of innovative websites, webshops and web applications of varying complexity.
Key services
Technical advice, Agile development, Custom website development, Webshops, Web applications, Hosting services, Technical support
Content quality
good
Branding
consistent

Technology

Stack
Drupal 8, Bootstrap 3.4.1, jQuery 3.2.1, Google Maps API, Slick Carousel
Frameworks
Drupal
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
50/100
Good practices seen
  • Anonymize IP in Google Analytics

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is a professional service provider site for custom web development and hosting.
  2. No privacy or cookie policies found, which is a compliance gap.
  3. Contact information is clearly provided including phone, email, physical address, and contact form.
  4. No explicit security policies or incident response info published.
  5. Uses Drupal 8 CMS with modern frontend libraries.
  6. Social media presence on Facebook, LinkedIn, and GitHub.
  7. Google Analytics used with IP anonymization.
  8. No WAF or blocking detected; site fully accessible.
Technical notes

Notes

The website is built on Drupal 8 CMS, utilizing Bootstrap 3.4.1 for responsive design and jQuery 3.2.1 for client-side scripting. Google Maps API and Slick Carousel are used for interactive content and slideshows. The site loads external resources from reputable CDNs such as jsdelivr.net and rawgit.com. Performance is moderate with good mobile optimization and basic accessibility features. SEO is supported by proper meta tags and Open Graph data. The hosting provider is likely linked to the registrar Radicenter OÜ, with nameservers in Denmark, indicating a regional hosting setup. The site lacks advanced security headers and privacy compliance features, which are technical debt areas. Overall, the infrastructure is modern but could be enhanced with improved security and privacy technical implementations.
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 bellcom.ee. 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 bellcom.ee.

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.