Skip to main content

Security report for siriustoken.io

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

Siriustoken.io operates as a niche decentralized finance (DeFi) platform offering a liquidity pool token called Sirius ($SIRS) on the Tezos blockchain. The token simplifies participation in Liquidity Baking, allowing users to earn rewards by purchasing the token instead of performing complex multi-step transactions. The website targets cryptocurrency investors and Tezos users interested in liquidity pool participation. The business model revolves around token issuance and DeFi liquidity provision, positioning itself as a specialized player within the Tezos ecosystem. Technically, the website employs modern web technologies including HTML5, CSS3, JavaScript, and the Swiper.js library for interactive content. Hosting appears to be on Amazon AWS infrastructure, inferred from DNS servers. The site is moderately optimized for performance and mobile devices, with basic accessibility and SEO features. However, no CMS or advanced frameworks are detected, indicating a relatively simple but functional technical setup. From a security perspective, the site lacks visible security headers and DNSSEC is not enabled, which are areas for improvement. The domain uses privacy protection for WHOIS data, common in crypto projects, but no contact or incident response information is provided. No privacy or cookie policies are present, indicating low privacy compliance. The overall security posture is moderate but could be enhanced by implementing standard security best practices and transparency measures. Overall, the website is professional and relevant to its niche but lacks critical compliance and security documentation. Strategic recommendations include adding privacy and cookie policies, enabling DNSSEC, implementing security headers, and providing clear contact and incident response information to improve trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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 siriustoken.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
77
Security headers
15
Email security
60
DNS health
70
Network security
100
GDPR outside view
35
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

Sirius token targets a specialized market segment within the Tezos blockchain ecosystem, focusing on liquidity baking participation. Its competitive advantage lies in simplifying the user experience for liquidity providers by tokenizing the participation process. Revenue streams likely derive from token sales and liquidity incentives. The target customers are crypto investors and DeFi participants on Tezos. The project is relatively new, founded in 2022, and operates independently without visible parent or subsidiary companies. The partnership ecosystem is minimal with no explicit partners listed. Growth indicators are limited due to lack of public business information. The website content and branding are consistent, supporting a focused market presence.

Security posture

The current security maturity level is basic. Key vulnerabilities include absence of DNSSEC, lack of security headers, and no published security or incident response policies. The domain uses privacy protection which is justified but reduces transparency. There are no visible compliance indicators for GDPR or other regulations. Data protection practices are unclear due to missing privacy documentation. Incident response readiness cannot be assessed. The security culture appears minimal based on available information. Business impact of these gaps includes potential trust issues and exposure to DNS spoofing or web-based attacks. Enhancing security posture is critical for credibility in the crypto space.

Recommendations

  1. Enable DNSSEC to secure DNS queries and prevent spoofing.
  2. Implement HTTPS with strong TLS configuration and enforce HTTPS redirects.
  3. Add standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Publish comprehensive privacy and cookie policies to improve GDPR compliance.
  5. Provide clear contact information including security incident response contacts.
  6. Consider adding a vulnerability disclosure policy or security.txt file.
  7. Improve accessibility features and SEO optimization for better user experience and discoverability.
  8. Regularly audit third-party scripts and dependencies for vulnerabilities.
  9. Increase transparency around business and regulatory compliance to build trust.
  10. Establish a formal incident response plan and communicate it publicly.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Sirius ($SIRS) is a token that enables automatic participation in Liquidity Baking, a decentralized liquidity pool between tez and tzBTC on the Tezos blockchain. It simplifies the process of earning liquidity baking rewards by allowing users to purchase Sirius tokens instead of conducting multi-step transactions.
Key services
Liquidity pool token issuance, Simplified liquidity baking participation, Reward earning via tez token distribution
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, Swiper.js, Google Fonts
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
50/100
Good practices seen
  • Domain uses clientTransferProhibited and clientUpdateProhibited status to prevent unauthorized transfers and updates

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is accessible with full content and no blocking detected
  2. No privacy, cookie, or terms of service policies found
  3. No contact emails, phone numbers, or physical addresses provided
  4. No social media links or business certifications displayed
  5. Technical implementation uses modern libraries like Swiper.js and Google Fonts
  6. No analytics or tracking scripts detected
  7. No security headers or explicit security policies found
  8. Domain WHOIS is privacy protected but domain age and registrar are legitimate
  9. Content is focused on a niche DeFi token on Tezos blockchain
  10. No advertising or affiliate marketing detected
Technical notes

Notes

The website is built using standard web technologies with a focus on simplicity and user experience. It uses Swiper.js for interactive sliders and Google Fonts for typography. Hosting is likely on AWS infrastructure, providing reliable performance. The site is mobile optimized and has a clean design. However, there is no CMS detected, which may limit content management flexibility. Performance is moderate with room for improvement in SEO and accessibility. The absence of advanced frameworks or analytics tools suggests a lightweight but basic technical implementation. Technical risks include lack of DNSSEC and missing security headers which could impact site integrity 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 siriustoken.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 siriustoken.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.