Skip to main content

Security report for tagion.org

Other · N/a

Low risk. 4 critical or high findings in Security headers and GDPR outside view.

Security score

77/100

Risk levelLow

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

The website www.tagion.org appears to be a technology-focused site, likely related to blockchain or decentralized technologies, as indicated by the use of Gatsby and thematic hints in the CSS classes and partial content. However, the actual content is minimal or placeholder, with no visible business descriptions, contact information, or legal policies. The WHOIS data is unavailable due to a malformed query response, which limits trust and transparency. Technically, the site uses modern static site generation technology but lacks visible security headers or SSL configuration details in the provided data. No analytics or tracking scripts were detected, suggesting minimal data collection. Overall, the security posture is weak due to missing policies and lack of contact or incident response information. The site is accessible without WAF or blocking mechanisms, but the lack of WHOIS and business information reduces credibility and trustworthiness.

Scanned

NIS2 and GDPR posture

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

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

  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

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

Keep watching tagion.org

This scan found 18 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. See sample alerts.

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
95
Security headers
30
Email security
85
DNS health
85
Network security
100
GDPR outside view
65
Average
77

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

Due to the absence of explicit business information, the market positioning and business model cannot be confidently determined. The site likely targets technology or blockchain enthusiasts or developers, but no clear services or products are described. There are no visible partnerships or subsidiaries. The lack of contact details and legal policies suggests the site may be in early development or not fully operational. No revenue streams or growth indicators are evident from the content. The branding is moderately consistent but lacks depth and trust signals.

Security posture

The security maturity level is low, with no detected HTTPS or security headers in the provided data. No privacy or cookie policies are present, and no incident response or vulnerability disclosure mechanisms are found. The absence of WHOIS data further reduces trust. There is no evidence of exposed sensitive data or vulnerable libraries, but the lack of security best practices is a concern. Compliance with GDPR or other regulations is not demonstrated. The site would benefit from implementing standard security headers, HTTPS, privacy policies, and incident response contacts to improve its security posture.

Recommendations

  1. Implement HTTPS with a valid SSL certificate and configure strong TLS settings.
  2. Add comprehensive privacy and cookie policies to comply with GDPR and inform users.
  3. Publish clear contact information including support and incident response emails.
  4. Deploy security headers such as Content-Security-Policy, X-Frame-Options, and X-XSS-Protection.
  5. Establish a vulnerability disclosure policy and security.txt file to enhance transparency and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor
Branding
moderate

Technology

Stack
Gatsby
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website content is minimal and mostly placeholder or coming soon
  2. No visible contact information or legal policies
  3. No security or privacy policies detected
  4. No WHOIS data available, indicating possible privacy protection or misconfiguration
  5. No external links or social media links found in the provided HTML
  6. Website uses Gatsby static site generator
  7. No analytics or tracking scripts detected
  8. No forms detected in the truncated HTML content
  9. No security headers or SSL configuration details available
Technical notes

Notes

The website is built using Gatsby, a modern React-based static site generator, indicating a modern technical stack. The site appears to be mobile optimized with responsive design elements. However, the content is minimal and lacks SEO optimization and accessibility features. No CMS or hosting provider information is available. Performance is likely moderate given the static nature but cannot be fully assessed. There is technical debt in the form of missing legal and security content and lack of WHOIS transparency. Modernization opportunities include adding structured data, improving SEO, and enhancing accessibility.
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 tagion.org. 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 tagion.org.

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.