Skip to main content

Security report for wild.as

wild GmbH · Technology · N/a

High risk. 6 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

38/100

Risk levelHigh

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

wild GmbH is a technology and design company specializing in creating award-winning digital products such as websites, apps, and digital content for modern brands, startups, and enterprises. The company positions itself as an innovative partner combining design, technology, and business strategy. Their website reflects a professional and consistent brand image with extensive project showcases and active social media presence. Technically, the website uses modern JavaScript libraries and image CDN services but suffers from slow load times and lacks a valid SSL certificate, which critically impacts security. The absence of HTTPS and security headers exposes the site to potential risks. Privacy compliance is partially addressed with a cookie consent banner and privacy policy, though GDPR compliance is not clearly demonstrated. No direct contact information is provided on the site, which may affect user trust. WHOIS data confirms the domain is active and registered without privacy protection, consistent with the business profile. Overall, the site is content-rich and professionally designed but requires urgent security improvements to meet modern standards.

Scanned

NIS2 and GDPR posture

GDPR outside view
18/ 100 · Critical
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. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • 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

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

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. 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 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';…

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

Keep watching wild.as

This scan found 18 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
0
Security headers
60
Email security
50
DNS health
60
Network security
40
GDPR outside view
18
Average
38

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

wild GmbH operates in the technology sector, focusing on digital product design and development. Their market positioning is strong within creative and digital agency spaces, leveraging award nominations and partnerships such as residence.co to enhance credibility. The business model revolves around service delivery to brands and enterprises, with a target audience of modern and innovative companies. The company maintains a medium-sized profile with a well-curated portfolio and active engagement on multiple social platforms. Growth indicators include recent project launches and media coverage. The partnership ecosystem includes residence.co and various digital platforms. Strategic observations suggest the company should enhance its security posture and provide clearer contact channels to improve client trust and compliance.

Security posture

The current security posture of wild GmbH's website is weak due to the lack of a valid SSL certificate and absence of HTTPS support, which is a critical vulnerability. No security headers such as Content-Security-Policy or HSTS are implemented, increasing exposure to common web attacks. Email security is also lacking with no DMARC or DNSSEC records configured. The cookie consent mechanism is present but GDPR compliance is not fully evident. Incident response and security policy information are not found, indicating limited transparency in security governance. The domain lacks protection locks, which could pose risks of unauthorized changes. Overall, the security maturity is low, and immediate remediation is recommended to protect user data and maintain trust.

Recommendations

  1. Obtain and install a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  3. Configure essential security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Set up DNSSEC and DMARC records to enhance DNS and email security.
  5. Enhance privacy policy to explicitly address GDPR compliance and data protection measures.
  6. Provide clear and verified contact information including company emails and phone numbers.
  7. Enable domain protection locks to prevent unauthorized domain modifications.
  8. Optimize website performance to reduce load times and improve user experience.
  9. Conduct regular security audits and establish an incident response plan.
  10. Increase transparency by publishing security policies and vulnerability disclosure information.
Technical notes

Notes

The website is built using modern JavaScript frameworks and libraries such as Swiper.js for sliders and cookieconsent.js for cookie management. Images are served via imgix CDN for optimized delivery. Hosting is provided by DigitalOcean as indicated by the IP address. The site has a slow load time of approximately 7.5 seconds with 65 resources loaded, which could be improved. The HTML and CSS are valid and the site is mobile optimized with responsive design. SEO is supported by proper meta tags and Open Graph data. However, the lack of HTTPS and security headers represents a significant technical risk. No CMS or backend platform is explicitly detected. Overall, the technical infrastructure is modern but requires security and performance enhancements to reduce technical debt and operational risks.
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 wild.as. 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 wild.as.

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.