Skip to main content

Security report for web357.com

Web357 · Technology · Cyprus

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

Security score

69/100

Risk levelMedium

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

Web357 is a specialized technology company delivering premium Joomla! extensions and WordPress plugins aimed at enhancing website functionality, security, and performance. Established since 2010 and based in Cyprus, the company targets developers, digital agencies, and web professionals seeking reliable and professional web development tools. Their market position is supported by a strong user base of over 10,000 satisfied customers and positive verified testimonials. The website reflects a mature digital presence with modern technologies such as React and Next.js, and integrates analytics and user feedback tools like Google Analytics and Hotjar. Security posture is generally good with HTTPS enforced and no visible vulnerabilities, though some improvements in security headers and incident response transparency are recommended. Privacy compliance is adequate with a comprehensive privacy policy, but lacks a cookie consent mechanism despite tracking scripts. Overall, Web357 presents a professional and trustworthy online presence with minor areas for enhancement in security and privacy practices.

Scanned

NIS2 and GDPR posture

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

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

This scan found 22 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
70
DNS health
80
Network security
100
GDPR outside view
58
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

Web357 operates a premium software business model focused on Joomla and WordPress ecosystems, offering extensions and plugins with ongoing support and maintenance. Their competitive advantage lies in clean, reliable code and premium customer support, appealing to a niche but sizable market segment of web developers and agencies. Revenue streams likely include direct sales and subscriptions for software bundles. The company maintains an active social media presence and uses third-party services for customer engagement and analytics. Growth indicators include a large user base and consistent product updates. Partnerships include payment processing via PayPal. Strategic observations suggest opportunities to enhance trust through improved transparency in security policies and domain registration details.

Security posture

Web357 demonstrates a moderate to high security maturity level with HTTPS enforced and no exposed sensitive data in the website content. However, the absence of key security headers such as Content-Security-Policy and lack of published incident response or vulnerability disclosure policies indicate room for improvement. The website uses secure forms for data collection but does not provide explicit security or incident contact channels. Compliance with GDPR is implied through a comprehensive privacy policy, but cookie consent mechanisms are missing despite tracking technologies in use. Overall, the security posture is solid but could be strengthened by adopting best practices in security headers, incident response transparency, and cookie consent management.

Recommendations

  1. Implement and enforce security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  2. Add a cookie consent banner/mechanism to comply with privacy regulations and inform users about tracking.
  3. Publish a clear security policy and incident response plan on the website to enhance transparency and trust.
  4. Consider adding a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  5. Investigate and resolve the missing WHOIS data issue to improve domain legitimacy and trustworthiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Web357
Description
Web357 delivers premium plugins and tailored solutions for Joomla! and WordPress websites. Since 2014, their experienced team focuses on improving performance, usability, and security of these platforms, empowering developers, digital agencies, and web professionals with expert support and ongoing maintenance.
Key services
Joomla! extensions, WordPress plugins, Support and maintenance
Content quality
excellent
Branding
consistent

Technology

Stack
React, Next.js, JavaScript, CSS, Google Tag Manager, Hotjar, HelpScout Beacon
Frameworks
Next.js, React
Platforms
Web
Performance
moderate
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Secure forms with email input

Analytics and tracking

Services
Google Analytics, Hotjar
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Hotjar
Marketing tools
HelpScout Beacon
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content and professional design.
  2. No WAF or blocking mechanisms detected.
  3. WHOIS data is missing, which is a concern for domain legitimacy verification.
  4. Strong presence of trust signals including testimonials and verified social media links.
  5. No explicit security policies or incident response info published.
  6. No cookie consent mechanism detected despite tracking scripts present.
  7. Privacy policy and terms of service pages are present and comprehensive.
  8. No phone numbers explicitly labeled as company contacts found.
  9. Email contact is provided and consistent with company domain.
Technical notes

Notes

The website is built on a modern tech stack leveraging React and Next.js frameworks, ensuring good performance and mobile responsiveness. Integration with Google Tag Manager, Hotjar, and HelpScout Beacon indicates a mature approach to analytics and customer support. The site uses optimized images and fonts with preload hints, contributing to performance. Accessibility and SEO optimizations are present with proper meta tags and structured data (JSON-LD). No CMS detected, suggesting a custom or headless approach. Hosting provider details are not disclosed. Overall, the technical infrastructure is robust with opportunities to enhance security headers and privacy compliance.
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 web357.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 web357.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.