Skip to main content

Security report for jellyfish.co.za

Jellyfish sa · Marketing and advertising · South africa

Partial score · DNS & email only

64/100

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

Scanned

4 of 7 checks could not complete. The site may be unreachable or blocking automated scans, so the results below cover only what could be checked. Try a rescan later.

NIS2 and GDPR posture

GDPR outside view
68/ 100 · Medium
Checks completed
3of 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

2 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 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 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 jellyfish.co.za

This scan found 7 issues across 2 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

Security headers
60
GDPR outside view
68
Average
64

Not counted

  • SSL/TLS: did not complete in this scan.
  • Email security: did not complete in this scan.
  • DNS health: did not complete in this scan.
  • Network security: did not complete in this scan.
  • 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

Jellyfish operates in the technology and media sectors, offering digital marketing services enhanced by generative AI. The company targets brands and enterprises seeking advanced marketing solutions. Its business model focuses on service delivery through a global network of offices, enabling localized client engagement. The company’s competitive advantage lies in its integration of AI with traditional marketing disciplines, positioning it well in a competitive digital landscape. The website content and structured data indicate a well-established enterprise with a founding date of 2005, supporting a mature market presence. Partnerships and social media presence further reinforce its market positioning. However, the lack of visible certifications or security accreditations on the site suggests potential areas for trust enhancement.

Security posture

The website employs HTTPS with strong SSL configuration and includes key security headers such as Content-Security-Policy and Strict-Transport-Security, indicating good baseline security practices. No exposed sensitive data or vulnerable libraries were detected in the HTML content. Forms appear secure with standard input fields, though no explicit mention of security frameworks or incident response policies was found. The absence of a published vulnerability disclosure policy or security.txt file limits transparency in security management. GDPR compliance is indicated through privacy and cookie policies, but no dedicated data protection officer contact was identified. Overall, the security posture is solid but could benefit from enhanced transparency and formalized security documentation.

Recommendations

  1. Publish a dedicated security policy and incident response plan on the website to improve transparency and trust.
  2. Implement and publicly disclose a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  3. Provide clear contact information for a Data Protection Officer or security contact to comply with GDPR and enhance accountability.
  4. Regularly review and audit third-party scripts and integrations to mitigate potential security risks.
  5. Consider obtaining and displaying relevant security certifications (e.g., ISO 27001) to strengthen credibility.

Contact details published on the site

Addresses
Legal name
Jellyfishc
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Jellyfish Digital
Description
We are a global digital marketing business that combines media, creative, and data with the power of Generative AI, helping brands move faster and smarter in today's competitive digital landscape.
Key services
Media, Creative, Data, Generative AI-powered marketing
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, Vimeo Player, Google Tag Manager, HubSpot styled components, Nuxt.js
Frameworks
Vue.js, Nuxt.js
Platforms
Vimeo
Performance
moderate
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of security headers
  • No exposed sensitive data in HTML
  • Secure forms with proper input fields

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Marketing tools
HubSpot
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 or domain not found, which is unusual for an established business.
  4. Strong global presence with multiple office locations listed in structured data.
  5. Use of modern web technologies and SEO best practices.
  6. Privacy and cookie policies are present and indicate GDPR compliance.
  7. No explicit security or incident response policies found on the site.
  8. Contact information is comprehensive and includes emails, phones, and addresses.
  9. No suspicious or malicious content detected.
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 jellyfish.co.za. 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 jellyfish.co.za.

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.