Skip to main content

Security report for polyswarm.network

Swarm Technologies Inc · Technology · United States

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

Security score

69/100

Risk levelMedium

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

PolySwarm.network is a cybersecurity platform specializing in crowdsourced threat detection, offering services such as scanning, searching, hunting, and sandboxing malware and threats. The company, Swarm Technologies Inc, founded in 2018 and based in the US, positions itself as a niche technology provider in the cybersecurity industry. The website is professionally designed with consistent branding and clear navigation, targeting cybersecurity professionals and enterprises seeking advanced threat detection solutions. Technically, the site leverages modern JavaScript frameworks like React, is hosted on Cloudflare Pages, and integrates marketing and analytics tools such as HubSpot, Leadfeeder, and Google Tag Manager. Performance and mobile optimization are good, though accessibility and SEO are basic. Security posture is solid with HTTPS enforced and domain security flags set, but lacks DNSSEC and explicit security headers. Privacy compliance is partial with a basic privacy policy and no cookie consent mechanism. Contact information and incident response details are not explicitly provided on the site, which could impact user trust and compliance. Overall, the site is functional and professional but could improve in privacy and security transparency.

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

6 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. 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 polyswarm.network

This scan found 19 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
75
Security headers
30
Email security
50
DNS health
90
Network security
100
GDPR outside view
68
Average
69

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

PolySwarm operates a crowdsourced cybersecurity threat detection marketplace, leveraging a community-driven approach to identify and analyze threats. Its business model focuses on providing scanning, hunting, and sandboxing services to cybersecurity professionals and enterprises. The company maintains a consistent brand presence and partners with related domains for documentation and status monitoring. Revenue likely stems from service subscriptions or marketplace transactions. The target audience includes security researchers and organizations requiring advanced threat intelligence. The company demonstrates moderate size and maturity with a domain age consistent with its founding year. Strategic partnerships and integrations with marketing and analytics platforms indicate a focus on growth and customer engagement.

Security posture

The website exhibits a good security posture with HTTPS enabled and domain status flags that prevent unauthorized transfers or deletions. However, the absence of DNSSEC reduces DNS security. No explicit security headers such as Content-Security-Policy or X-Frame-Options were detected, which are recommended to mitigate common web vulnerabilities. There is no visible security policy or incident response contact information, nor a vulnerability disclosure or security.txt file, which limits transparency and responsiveness to security issues. The site uses third-party analytics and marketing scripts, which may introduce privacy considerations. Overall, the security maturity is moderate but could be enhanced by implementing recommended headers, DNSSEC, and public security policies.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement standard security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Add a cookie consent banner and detailed cookie policy to improve privacy compliance and user transparency.
  4. Publish explicit security and incident response policies, including contact channels for reporting vulnerabilities or incidents.
  5. Create and host a security.txt file or vulnerability disclosure page to facilitate responsible vulnerability reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Swarm Technologies Inc
Description
PolySwarm is a platform focused on crowdsourced threat detection, providing services such as scanning, searching, hunting, and sandboxing for cybersecurity threats.
Key services
Threat scanning, Threat search, Threat hunting, Sandbox analysis
Content quality
good
Branding
consistent

Technology

Stack
React, JavaScript, Cloudflare, HubSpot, Leadfeeder, Google Tag Manager
Frameworks
React
Platforms
Cloudflare Pages
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Domain status clientDeleteProhibited and clientTransferProhibited

Analytics and tracking

Services
HubSpot Analytics, Leadfeeder, Google Analytics via GTM, Cloudflare Pages Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
HubSpot, Leadfeeder, Cloudflare Insights
Marketing tools
HubSpot, Leadfeeder
Transparency
basic

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 professional and focused on cybersecurity threat detection services.
  3. No explicit contact emails or phone numbers found on the main page.
  4. Privacy and terms pages are present but privacy policy is basic and lacks explicit GDPR compliance statements.
  5. No cookie consent banner or explicit cookie policy detected.
  6. Use of modern JavaScript frameworks and third-party marketing/analytics tools.
  7. No visible security.txt or vulnerability disclosure page.
  8. DNSSEC not enabled, which is a recommended security improvement.
  9. No explicit security or incident response contact information found.
Technical notes

Notes

The website is built using React and modern JavaScript, hosted on Cloudflare Pages, ensuring good performance and scalability. Integration with HubSpot, Leadfeeder, and Google Tag Manager supports marketing and analytics efforts. The site is mobile optimized and has a clear navigation structure. However, accessibility features are basic and SEO optimization could be improved with more comprehensive meta tags and structured data. No CMS is detected, indicating a custom or static site approach. The technical infrastructure is modern and adequate for the business needs but could benefit from enhanced accessibility and SEO practices.
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 polyswarm.network. 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 polyswarm.network.

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.