Skip to main content

Security report for algorand.com

Other · N/a

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

Security score

65/100

Risk levelMedium

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

Algorand Technologies appears to be a newly established technology-focused website, likely related to blockchain or cryptocurrency given the domain name and tags. The site is built using modern web technologies such as React and Gatsby and is hosted behind Cloudflare DNS services. However, the content is minimal and lacks critical business and compliance information such as privacy policies, cookie consent, and contact details. The domain is very recent, created in late September 2023, which aligns with a startup or new project phase. Security posture is basic with HTTPS enabled but lacking DNSSEC and security headers, indicating room for improvement in hardening the site. Overall, the website presents a basic digital presence with limited trust and compliance signals, suggesting it is in early development or pre-launch stage.

Scanned

NIS2 and GDPR posture

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

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

    • High

      No SPF record found

      SPF helps prevent email spoofing

      What to do: Add SPF record: "v=spf1 include:_spf.yourmailprovider.com ~all"

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

Keep watching algorand.com

This scan found 21 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
75
Security headers
35
Email security
50
DNS health
70
Network security
100
GDPR outside view
58
Average
65

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

The business behind algorandtechnologies.com is not clearly identified on the website. There is no visible company name, contact information, or detailed description of services. The domain age and technical stack suggest a technology startup or project possibly targeting blockchain or cryptocurrency sectors. No partnerships or subsidiaries are indicated. The lack of business transparency and minimal content limits the ability to assess market positioning or revenue streams. The site does not currently leverage analytics or marketing tools, indicating an early stage or low digital marketing maturity.

Security posture

The website uses HTTPS, which is a fundamental security requirement. However, it lacks DNSSEC, which could protect against DNS spoofing attacks. No security headers such as Content-Security-Policy, X-Frame-Options, or X-Content-Type-Options were detected, which are important for mitigating common web vulnerabilities. There is no published security policy or incident response information, and no vulnerability disclosure or security.txt file was found. The absence of privacy and cookie policies also indicates non-compliance with GDPR and other privacy regulations. Overall, the security posture is basic and requires enhancements to meet industry best practices and regulatory compliance.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security.
  2. Implement essential HTTP security headers to protect against common web attacks.
  3. Publish comprehensive privacy and cookie policies with GDPR compliance details.
  4. Add clear contact information including emails and phone numbers for business and security incident reporting.
  5. Consider adding a security policy and vulnerability disclosure program to build trust and transparency.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
basic
Branding
moderate

Technology

Stack
React, Gatsby, Google Fonts, Cloudflare DNS
Frameworks
React, Gatsby
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
45/100
Good practices seen
  • HTTPS enabled

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
low

Key observations

  1. Website is accessible with no blocking or WAF challenges.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails, phone numbers, or physical addresses detected.
  4. No security or incident response policies published.
  5. Website uses modern React and Gatsby frameworks but content is minimal and basic.
  6. No analytics or tracking scripts detected.
  7. No social media or external business partner links found.
  8. Domain is very new (created less than 1 month ago).
  9. No DNSSEC enabled, which is a security improvement opportunity.
  10. No security headers detected in HTTP response (based on available data).
Technical notes

Notes

The website is built using React and Gatsby frameworks, indicating a modern frontend technology stack optimized for performance and SEO. Hosting is managed via Cloudflare DNS, providing some level of security and performance benefits. The site loads with moderate speed and is mobile optimized with responsive design. However, accessibility features are basic and SEO optimization is minimal due to lack of meta descriptions and structured data. No CMS or backend platform was detected, suggesting a static site or JAMstack architecture. There is no evidence of analytics or tracking scripts, which limits marketing insights. Overall, the technical implementation is modern but basic, suitable for a new or small-scale project.
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 algorand.com. 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 algorand.com.

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.