Skip to main content

Security report for publicnode.com

PublicNode · Technology · N/a

Medium risk. 3 critical or high findings in SSL/TLS, Security headers and 1 other check.

Security score

64/100

Risk levelMedium

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

PublicNode is a technology company specializing in providing fast, free, and privacy-focused RPC endpoints for over 100 blockchain networks. Their platform targets developers and users in the Web3 and blockchain ecosystem, offering reliable connectivity to multiple blockchains. The website demonstrates a modern technical infrastructure built on Next.js and React, hosted likely via Cloudflare, ensuring good performance and mobile optimization. Security posture is solid with HTTPS enabled and domain transfer protections, though improvements are needed in DNS security and publishing formal privacy and cookie policies. The absence of contact information and security incident channels limits transparency and trust. Overall, PublicNode presents as a credible and technically mature service provider in the blockchain infrastructure space.

Scanned

NIS2 and GDPR posture

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

3 findings rated critical or high. Fix these first.

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

    • Critical

      Unable to retrieve SSL certificate

      Could not establish secure connection to retrieve certificate information

      What to do: Check if the server is accessible and SSL/TLS is properly configured

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

This scan found 15 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
0
Security headers
55
Email security
70
DNS health
85
Network security
100
GDPR outside view
73
Average
64

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention publicnode.com, from OffSeq Breach.

No leaked records found

Breach holds no records for publicnode.com right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

PublicNode occupies a niche in blockchain infrastructure by offering RPC endpoints and node snapshots, catering to a broad developer audience. Their business model likely involves tiered API access or usage-based monetization. The company has established a significant market presence since 2016, supporting a wide range of blockchains including Ethereum, Polygon, Solana, and others. The extensive list of supported chains and endpoints indicates strong operational capabilities and partnerships within the blockchain ecosystem. However, the lack of visible business contact details and formal policies may hinder enterprise adoption and compliance with regulatory frameworks.

Security posture

The website employs HTTPS and has domain transfer protections, indicating baseline security awareness. However, the lack of DNSSEC implementation and absence of security headers such as Content-Security-Policy or X-Frame-Options represent areas for enhancement. No vulnerability disclosure or incident response information is provided, which is a gap in security transparency. The site does not expose sensitive data or use vulnerable libraries based on the provided content. Overall, the security posture is moderate but could benefit from formalized policies and improved DNS security.

Recommendations

  1. Enable DNSSEC to enhance DNS security and prevent spoofing.
  2. Publish comprehensive privacy and cookie policies to improve compliance and user trust.
  3. Add security headers like Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Provide clear contact information including security incident response channels.
  5. Implement a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
PublicNode
Description
Fastest, free-est, and privacy first RPC endpoints for 102 blockchains. Connect reliably to Web3 with ease!
Key services
RPC Endpoints for multiple blockchains, Node Snapshots
Content quality
good
Branding
consistent

Technology

Stack
React, Next.js, Cloudflare DNS, Google Fonts
Frameworks
Next.js
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enabled
  • Domain status clientTransferProhibited

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 provides extensive RPC endpoint services for a large number of blockchains (102).
  2. No visible privacy, cookie, or terms of service policies found on the main page.
  3. No contact emails, phone numbers, or physical addresses found in the HTML content.
  4. Website uses modern web technologies including Next.js and React.
  5. DNS is managed via Cloudflare but DNSSEC is not enabled.
  6. No security.txt or vulnerability disclosure information found.
  7. No advertising or tracking scripts detected in the provided HTML.
  8. Website content is professional and targeted at blockchain developers and users.
  9. No signs of adult or questionable content.
  10. WHOIS data supports legitimacy and domain age is appropriate.
Technical notes

Notes

The website is built using modern web technologies including React and Next.js, ensuring good performance and mobile responsiveness. Hosting appears to be via Cloudflare, providing reliable DNS and CDN services. The site uses Google Fonts for typography and loads multiple JavaScript chunks for functionality. SEO is supported by proper meta tags and Open Graph data. No CMS is detected, suggesting a custom or framework-based site. The technical implementation is robust with fast loading times and good accessibility, though some security best practices could be improved.
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 publicnode.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 publicnode.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.