Skip to main content

Security report for parsiq.net

PARSIQ · Technology · N/a

Medium risk. 5 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

67/100

Risk levelMedium

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

PARSIQ is a technology company specializing in high-speed Web3 data solutions and developer tools for blockchain applications. The company is transitioning its focus to the Reactive Network, a fully EVM-compatible execution layer designed to enable decentralized applications with reactive smart contracts. The website clearly communicates this evolution and provides information about a token migration from PRQ to REACT on a 1:1 basis, emphasizing fairness and transparency. The target audience is primarily blockchain developers and Web3 ecosystem participants. Technically, the website uses modern frameworks such as React.js, integrates Google Fonts, Google Tag Manager, and HubSpot analytics, and is hosted behind Cloudflare DNS. The site is mobile-optimized and presents a professional design with good SEO and accessibility basics. Security posture is solid with HTTPS enforced and cookie consent implemented, though security headers and explicit security policies are absent. No contact emails or phone numbers are listed, and no terms of service or vulnerability disclosure policies are found, indicating areas for improvement. Overall, the domain registration data aligns well with the business claims, supporting legitimacy and trustworthiness.

Scanned

NIS2 and GDPR posture

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

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

  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 SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching parsiq.net

This scan found 23 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
65
Security headers
15
Email security
75
DNS health
80
Network security
100
GDPR outside view
68
Average
67

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

PARSIQ positions itself as an innovator in the blockchain data and developer tools market, evolving into the Reactive Network platform to capture emerging opportunities in decentralized application execution. The business model revolves around providing developer-centric tools and blockchain infrastructure services, supported by token economics through PRQ and REACT tokens. The company targets Web3 developers and blockchain projects, leveraging partnerships such as the Reactive Network. The website content and domain age indicate a medium-sized, established technology company founded in 2019. The lack of explicit contact details and formal policies suggests a focus on developer community engagement rather than broad consumer outreach. Marketing and analytics tools indicate active user engagement tracking and growth orientation.

Security posture

The website enforces HTTPS and uses reputable DNS providers, contributing to a secure baseline. Cookie consent mechanisms demonstrate privacy awareness and GDPR compliance efforts. However, the absence of key security headers (e.g., Content Security Policy, HSTS) and lack of published security policies or incident response contacts represent gaps in security maturity. No vulnerabilities or exposed sensitive data were detected in the HTML content. The site does not provide a vulnerability disclosure or security.txt file, limiting transparency for security researchers. Overall, the security posture is moderate but could be enhanced by adopting best practices and formalizing security governance documentation.

Recommendations

  1. Implement and enforce security headers such as Content Security Policy, HSTS, X-Frame-Options, and X-Content-Type-Options to strengthen browser security.
  2. Publish a dedicated security policy page and provide clear incident response contact information to improve transparency and trust.
  3. Add a terms of service page to clarify user rights and obligations, enhancing legal compliance.
  4. Establish a vulnerability disclosure policy and consider hosting a security.txt file to facilitate responsible reporting of security issues.
  5. Enhance accessibility features and conduct audits to improve inclusivity and compliance with accessibility standards.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
PARSIQ
Description
High speed data solutions powering the backends of dApps & protocols. PARSIQ provides Web3 developers with user-friendly development tools and is evolving into the Reactive Network project, a fully EVM-compatible execution layer for decentralized applications.
Key services
Web3 data solutions, Developer tools for blockchain, Reactive Network execution layer, Token migration service (PRQ to REACT)
Content quality
good
Branding
consistent

Technology

Stack
React.js, Google Fonts, Google Tag Manager, HubSpot scripts, Cloudflare DNS
Frameworks
React
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism

Analytics and tracking

Services
Google Analytics, HubSpot Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
HubSpot Analytics
Marketing tools
HubSpot
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges
  2. Content is focused on blockchain developer tools and new Reactive Network platform
  3. Clear communication about token migration from PRQ to REACT
  4. Cookie consent banner present and functional
  5. No contact emails or phone numbers explicitly listed on homepage
  6. No terms of service page found
  7. Use of modern web technologies and analytics tools
  8. No explicit security policy or incident response information found
Technical notes

Notes

The website is built using React.js, leveraging Google Fonts for typography and integrating Google Tag Manager and HubSpot for analytics and marketing automation. The hosting environment uses Cloudflare DNS, providing performance and security benefits. The site loads with moderate speed and is mobile-optimized, offering a good user experience. SEO is supported by comprehensive meta tags and Open Graph data. No CMS was detected, indicating a custom or static site build. The technical stack is modern and appropriate for a technology-focused business, though opportunities exist to improve accessibility and security header implementation. No technical debt or deprecated libraries were identified in the provided HTML content.
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 parsiq.net. 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 parsiq.net.

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.