Skip to main content

Security report for azero.dev

Technology · N/a

Medium risk. 9 critical or high findings in Email security, Security headers and 2 other checks.

Security score

60/100

Risk levelMedium

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

Azero.Dev is a technology-focused website serving as a blockchain explorer interface, likely related to the Aleph Zero blockchain ecosystem. The site provides a user interface for blockchain data exploration but currently lacks substantive content, privacy policies, or contact information. The target audience appears to be developers or blockchain enthusiasts interested in Aleph Zero technology. The business model and market position are not explicitly stated, but the site links to the Aleph Zero foundation's GitHub and homepage, indicating a close association with the Aleph Zero project. Technically, the website is built using modern JavaScript frameworks, specifically React, and utilizes Font Awesome for icons. The site loads multiple JavaScript modules and stylesheets, indicating a modular and component-based architecture. However, the content is minimal, with a loading state visible and no SEO or accessibility optimizations detected. Performance is moderate, and mobile optimization is basic. From a security perspective, the site does not expose any security headers or explicit security policies in the HTML content. There is no evidence of privacy or cookie policies, incident response contacts, or vulnerability disclosure mechanisms. The domain uses privacy protection for WHOIS data, which is common for small tech projects but reduces transparency. No WAF or blocking mechanisms are detected, and the site is accessible. Overall, the website presents a basic blockchain explorer interface with limited content and security posture. Strategic improvements in privacy compliance, security headers, contact information, and content richness are recommended to enhance trust and usability.

Scanned

NIS2 and GDPR posture

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

9 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

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

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

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

Keep watching azero.dev

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. 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
77
Security headers
15
Email security
40
DNS health
75
Network security
100
GDPR outside view
50
Average
60

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

Azero.Dev operates within the blockchain technology sector, focusing on providing blockchain explorer services for the Aleph Zero ecosystem. The site appears to be a small-scale project or component of the larger Aleph Zero foundation's offerings. Its competitive advantage lies in its association with Aleph Zero, a known blockchain project. The business model likely revolves around supporting the Aleph Zero network by providing transparency and data access to users and developers. Revenue streams and growth indicators are not evident from the site content. The partnership ecosystem includes GitHub and the official Aleph Zero homepage, suggesting open-source collaboration and community engagement. Strategic observations highlight the need for improved transparency, compliance, and user engagement to strengthen market presence.

Security posture

The current security maturity level of Azero.Dev is low to moderate. The absence of security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options indicates potential exposure to common web vulnerabilities. The lack of privacy and cookie policies suggests non-compliance with GDPR and other data protection regulations. No incident response or abuse contact channels are provided, which may hinder timely handling of security incidents. The use of privacy-protected WHOIS data is typical but reduces transparency. No vulnerable libraries or exposed sensitive data were detected in the provided HTML content. Overall, the security culture appears nascent, with significant room for improvement in compliance, transparency, and technical safeguards.

Recommendations

  1. Implement comprehensive privacy and cookie policies to ensure GDPR compliance and user trust.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
  3. Provide clear contact information including security and abuse email addresses to facilitate incident response.
  4. Enhance website content with detailed business information, terms of service, and user guidance to improve professionalism and credibility.
  5. Conduct regular security audits and vulnerability assessments to identify and remediate potential risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
basic
Branding
moderate

Technology

Stack
JavaScript, React, Font Awesome 6
Frameworks
React
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a blockchain explorer interface for Aleph Zero related technology.
  2. No privacy, cookie, or terms of service policies found on the main page.
  3. No contact emails, phone numbers, or physical addresses found.
  4. External links point to GitHub and Aleph Zero official homepage.
  5. Website uses React and Font Awesome for UI components.
  6. No security headers or explicit security policies detected in HTML content.
  7. No analytics or tracking scripts detected in the provided HTML.
  8. Content is minimal and mostly UI framework with loading state; no substantive textual content.
  9. No forms or data collection fields detected in the HTML.
  10. No structured data (JSON-LD) or Open Graph metadata found.
Technical notes

Notes

Azero.Dev employs a modern JavaScript stack with React as the primary framework and Font Awesome for iconography. The site uses modular JavaScript bundles and deferred script loading to optimize performance. However, the site currently displays a loading state with minimal content, indicating incomplete or dynamic content loading. There is no evidence of a CMS or server-side rendering. SEO and accessibility features are minimal or absent, which may impact discoverability and user experience. Hosting provider details are not discernible from the HTML content. Technical debt appears low but the site would benefit from improved content structure, metadata, and compliance features to support scalability and user engagement.
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 azero.dev. 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 azero.dev.

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.