Skip to main content

Security report for bazo.io

Bazo Sp. z.o.o · Technology · Poland

Partial score · DNS & email only

75/100

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

The website bazo.io is registered to Bazo Sp. z.o.o, a Polish technology company founded in 2015. However, the website is currently inaccessible, returning a 500 Internal Server Error with no accessible content or metadata. This severely limits the ability to assess the company's online presence, services, or compliance posture. The domain registration is consistent and legitimate, registered through OVH SAS with appropriate domain status protections, but DNSSEC is not enabled. Technically, the website lacks any detectable technologies, scripts, or frameworks, and no SEO or accessibility features are present. The hosting provider is OVH SAS, but the site performance and mobile optimization cannot be evaluated due to the error page. No privacy, cookie, or terms of service policies are found, and no contact information or forms are available, indicating a poor digital maturity level. From a security perspective, the site does not show evidence of security headers or HTTPS enforcement in the provided data, and the DNSSEC absence is a security gap. The 500 error indicates server-side issues that must be resolved to restore service. No WAF or blocking mechanisms are detected. Overall, the security posture is weak due to lack of visible protections and policies. Given the current state, the website poses a risk for users due to unavailability and lack of transparency. Strategic recommendations include fixing server errors promptly, implementing security best practices such as HTTPS and security headers, enabling DNSSEC, and publishing privacy and cookie policies to improve compliance and trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
Checks completed
6of 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

4 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.

    • 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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  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.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

Need hands-on remediation? Email guard@offseq.com

Keep watching bazo.io

This scan found 16 issues across 5 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
72
Email security
75
DNS health
80
Network security
100
GDPR outside view
50
Average
75

Not counted

  • Security headers: did not complete in this scan.
  • 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

Bazo Sp. z.o.o appears to be a small technology company based in Poland, with a domain registered since 2015. The lack of accessible website content prevents detailed analysis of its market positioning, business model, or key services. No partnerships or subsidiaries are identified. The company likely targets technology sector clients but without public-facing information, competitive advantages and revenue streams cannot be assessed. The absence of contact details and policies suggests limited digital engagement or an underdeveloped online presence.

Security posture

The security maturity of the website is low due to the absence of security headers, DNSSEC, and visible HTTPS enforcement. The 500 Internal Server Error indicates server instability or misconfiguration, which could expose the business to downtime risks. No incident response or vulnerability disclosure information is available, and no privacy or cookie policies are published, indicating compliance gaps with GDPR and other regulations. The domain registration is legitimate but technical security controls on the website are lacking.

Recommendations

  1. Resolve the 500 Internal Server Error to restore website availability immediately.
  2. Implement HTTPS with a valid SSL certificate and enforce secure connections.
  3. Enable DNSSEC to protect DNS integrity and prevent spoofing.
  4. Add comprehensive privacy and cookie policies to comply with GDPR and build user trust.
  5. Deploy security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  6. Publish contact information and incident response channels to improve transparency and security readiness.
  7. Conduct a security audit to identify and remediate server and application vulnerabilities.
  8. Improve website design and content quality to enhance user experience and business credibility.
  9. Consider implementing a vulnerability disclosure policy or security.txt file.
  10. Establish a data protection officer role or contact point to address privacy concerns.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Bazo Sp. z.o.o
Content quality
poor
Branding
inconsistent

Technology

Performance
slow
Mobile
poor
Accessibility
poor
SEO
poor

Security

Observed score
20/100

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 is currently inaccessible due to a 500 Internal Server Error.
  2. No privacy, cookie, or terms of service policies found on the main page.
  3. No contact information or forms are present on the error page.
  4. No scripts, analytics, or tracking technologies detected in the HTML content.
  5. No social media or external links except name servers in WHOIS data.
  6. DNSSEC is not enabled, which is a missed security opportunity.
  7. Domain is registered to a Polish company with a domain age of approximately 9 years.
  8. Website content quality and technical implementation are poor due to error page and lack of content.
  9. No evidence of WAF or security blocking mechanisms.
  10. No adult or questionable content detected.
Technical notes

Notes

The website currently serves only a minimal HTML error page indicating a 500 Internal Server Error, which prevents assessment of the underlying technology stack. No CMS, frameworks, or analytics scripts are detected. The domain is hosted by OVH SAS, a reputable provider. DNSSEC is not enabled, and no security headers are present in the provided data. The site lacks mobile optimization and accessibility features. The technical debt is high due to the server error and lack of modern web practices, posing risks to business continuity and user trust.
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 bazo.io. 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 bazo.io.

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.