Skip to main content

Security report for bounceexchange.com

Other · N/a

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

Security score

73/100

Risk levelMedium

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

The website www.wunderkind.co is accessible without any WAF or security challenge blocking content. However, the WHOIS data for the domain is fully redacted, providing no registrar, creation date, or registrant information, which limits the ability to fully verify domain legitimacy and trustworthiness. The website content appears basic with moderate branding consistency but lacks visible privacy, cookie, or terms of service policies, which are critical for compliance and user trust. No contact information or social media links are explicitly found, reducing business credibility. Technically, the site shows moderate performance and mobile optimization but lacks advanced security headers and comprehensive privacy compliance indicators. Overall, the security posture is basic with room for improvement in SSL configuration and security best practices.

Scanned

This is an earlier scan of bounceexchange.com. View the latest report

NIS2 and GDPR posture

GDPR outside view
85/ 100 · Low
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

4 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

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

This scan found 21 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
75
Network security
100
GDPR outside view
85
Average
73

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

Due to limited visible business information and absence of structured data or metadata, the business intelligence is minimal. The domain appears to represent a small-sized entity in an unspecified industry sector. No clear business model, market position, or key services are discernible from the content provided. The lack of contact details and trust indicators such as certifications or testimonials further limits insights into the company's operations or market presence.

Security posture

The security posture of the website is basic. HTTPS is presumably enabled but no detailed SSL configuration data is available. No security headers such as Content-Security-Policy or Strict-Transport-Security are detected. There are no visible vulnerabilities or exposed sensitive data in the provided content. The absence of privacy and cookie policies and lack of incident response contacts indicate compliance gaps. The domain's WHOIS data is fully redacted, which while common, reduces transparency. Overall, the site would benefit from enhanced security practices and compliance documentation.

Recommendations

  1. Implement and publish comprehensive privacy and cookie policies to improve compliance and user trust.
  2. Add security headers including Content-Security-Policy, X-Content-Type-Options, and Strict-Transport-Security to enhance security posture.
  3. Provide clear and accessible contact information including security incident response contacts.
  4. Review and improve SSL/TLS configuration to ensure robust encryption and trust.
  5. Consider publishing vulnerability disclosure and data protection officer information to demonstrate security maturity.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
basic
Branding
moderate

Technology

Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
55/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
basic
User experience
basic
Content relevance
basic
Navigation
basic
Professionalism
basic
Trustworthiness
moderate

Key observations

  1. Website content is accessible and not blocked by WAF or security challenges.
  2. WHOIS data is fully redacted, limiting domain trust assessment.
  3. No explicit privacy, cookie, or terms of service policies found in the provided HTML content.
  4. No contact emails, phone numbers, or physical addresses explicitly found.
  5. No social media links or external partner domains detected in the HTML content.
  6. No security headers or advanced security configurations detected from available data.
  7. Website design is basic with moderate branding consistency.
  8. No visible analytics or advertising/tracking technologies detected.
  9. Forms present but no detailed field extraction possible due to HTML truncation.
  10. No structured data (JSON-LD) or Open Graph metadata detected in the provided content.
Technical notes

Notes

The website uses modern CSS and responsive design techniques, indicating a moderate level of technical implementation. However, no specific CMS or hosting provider information is detected. The site lacks visible analytics or marketing technologies, suggesting minimal tracking. Performance is moderate with good mobile optimization but basic accessibility and SEO features. The absence of structured data and meta tags limits search engine optimization potential. Technical debt appears low but opportunities exist to modernize security and compliance features.
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

Earlier scans of this domain

  1. 74/100 +1Medium27 findingsView report
  2. 73/100Medium29 findingsView report
Reviews of this site

Share your experience with bounceexchange.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 bounceexchange.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.