Skip to main content

Security report for tzkt.io

Baking Bad OU · Technology · Estonia

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

Security score

53/100

Risk levelMedium

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

TzKT.io is a specialized blockchain explorer and API provider focused on the Tezos blockchain. Operated by Baking Bad OU, an Estonian company founded in 2019, it offers comprehensive blockchain data, a user-friendly interface, and an open-source blockchain indexer. The platform targets developers, blockchain users, and the Tezos community, positioning itself as a niche service within the Tezos ecosystem. The business model revolves around providing free and open access to blockchain data and APIs, supporting the broader Tezos network and its users. Technically, the website employs modern frontend technologies including Vue.js and Vuetify, ensuring fast performance, excellent mobile optimization, and good accessibility. The site uses HTTPS and integrates Google Analytics and Google Tag Manager for user tracking. However, it lacks DNSSEC on its domain and does not implement cookie consent mechanisms, which are areas for improvement. The hosting provider is not explicitly identified beyond the registrar Gandi SAS. From a security perspective, the site benefits from HTTPS and domain transfer protection but lacks several security headers and explicit security or incident response policies. No vulnerabilities or exposed sensitive data were detected in the content. Privacy compliance is basic, with privacy and terms policies hosted on the parent Baking Bad developer site but no cookie consent or GDPR compliance indicators on the main site. Overall, TzKT.io presents a professional, trustworthy, and technically mature platform with some gaps in privacy compliance and security best practices. Strategic improvements in DNSSEC, cookie consent, and security policy transparency would enhance its security posture and compliance standing.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
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

6 findings rated critical or high. Fix these first.

  1. 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';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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

  3. 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 tzkt.io

This scan found 26 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
72
Security headers
30
Email security
70
DNS health
55
Network security
40
GDPR outside view
53
Average
53

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

TzKT.io operates in the blockchain technology sector, specifically serving the Tezos ecosystem. Its competitive advantage lies in providing the most comprehensive and user-friendly Tezos blockchain explorer and API, supported by open-source technology. The business model is service-oriented, offering free access to blockchain data which likely supports ancillary revenue streams such as partnerships or developer ecosystem growth. The target customers include blockchain developers, Tezos users, and decentralized application builders. The company shows growth indicators through active domain registration and integration with staking services. Partnerships with stake.tezos.com and the parent Baking Bad developer site indicate a collaborative ecosystem approach. The company maintains a focused market presence with consistent branding and high-quality content.

Security posture

The security maturity of TzKT.io is moderate. The site uses HTTPS with a valid SSL certificate and has domain transfer protections in place. However, it lacks DNSSEC, which could mitigate DNS spoofing risks. No security headers such as Content Security Policy or HSTS were detected, which are recommended to harden the site against common web attacks. There is no published security policy or incident response information, which limits transparency and preparedness visibility. The use of Google Analytics and Tag Manager without cookie consent mechanisms raises privacy compliance concerns. No vulnerabilities or exposed sensitive data were found in the analysis. Overall, the site follows basic security best practices but should enhance its security framework and privacy compliance to reduce risk and improve trust.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement comprehensive security headers including CSP, HSTS, X-Frame-Options, and X-Content-Type-Options.
  3. Publish explicit security and incident response policies to increase transparency and preparedness.
  4. Add a cookie consent mechanism to comply with privacy regulations and inform users about tracking.
  5. Regularly audit third-party scripts and dependencies to ensure no vulnerable libraries are used.

Contact details published on the site

Addresses
Legal name
Baking Bad OU
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Baking Bad OU
Description
Tezos Explorer and API with the most comprehensive blockchain data, user-friendly interface and free open-source blockchain indexer.
Key services
Blockchain explorer, API for Tezos blockchain data, Open-source blockchain indexer
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, Vue.js, Vuetify, Google Analytics
Frameworks
Vue.js, Vuetify
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Client transfer prohibited domain status

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is a specialized blockchain explorer for Tezos.
  2. Content is comprehensive and technical, targeting blockchain users and developers.
  3. No direct contact emails or phone numbers found on the site.
  4. Privacy and terms policies are hosted on the parent Baking Bad developer site.
  5. No cookie consent mechanism detected despite use of tracking scripts.
  6. No explicit security or incident response policies published.
  7. Modern frontend technologies used with good performance and mobile optimization.
  8. No DNSSEC enabled on domain, which is a security improvement opportunity.
Technical notes

Notes

The website is built using modern JavaScript frameworks Vue.js and Vuetify, providing a responsive and performant user experience. The site loads quickly and is optimized for mobile devices. SEO is supported by proper meta tags and Open Graph data. The site does not use a traditional CMS, indicating a custom or static site generation approach. Hosting details beyond the registrar are not explicit, but the domain is registered with Gandi SAS. The site integrates Google Analytics and Tag Manager for analytics and tracking. There is no evidence of technical debt or deprecated technologies. Opportunities exist to improve security configurations and privacy compliance to align with best 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 tzkt.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 tzkt.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.