Skip to main content

Security report for kit-react.de

Other · N/a

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

Security score

66/100

Risk levelMedium

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

The website at kit-react.de is currently inaccessible, returning a 403 Forbidden error page with no visible content. This prevents extraction of any meaningful business, technical, or security information from the site itself. The domain is registered with GoDaddy nameservers, but no registrant or organizational details are available to verify legitimacy or business claims. Due to the lack of accessible content, no privacy, cookie, or security policies are found, and no contact information is available. The site appears to be either restricted or misconfigured, resulting in a poor user experience and lack of trust signals. Technical infrastructure details are minimal, and no modern technologies or frameworks can be identified from the provided HTML.

Scanned

NIS2 and GDPR posture

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

7 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

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

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

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

Keep watching kit-react.de

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. 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
52
Security headers
65
Email security
95
DNS health
70
Network security
100
GDPR outside view
15
Average
66

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 kit-react.de, from OffSeq Breach.

Total records
122
Employees
0
Customers
122
Third parties
0
Weak passwords
8%

1 subdomain affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for kit-react.de.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)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

Due to the absence of accessible website content, no business intelligence can be derived. There is no information on market positioning, services, target customers, or partnerships. The domain registration data is minimal and does not provide insights into company structure or operations. The lack of visible content and contact details suggests the site is either under development, restricted, or abandoned.

Security posture

The security posture cannot be fully assessed due to blocked content and lack of accessible headers or scripts. No HTTPS or security headers information is available. The 403 error indicates some form of access control but does not clarify if a WAF or other security mechanism is in place. No incident response or vulnerability disclosure information is found. Overall, the security posture appears weak or unknown, with no evidence of best practices or compliance.

Recommendations

  1. Resolve the 403 Forbidden error to allow public access to the website content.
  2. Implement HTTPS with a valid SSL certificate to secure communications.
  3. Add comprehensive privacy and cookie policies to comply with GDPR and other regulations.
  4. Publish clear contact information and security incident response channels.
  5. Enhance website content quality and technical implementation to improve user experience and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Website returns a 403 Forbidden error with minimal HTML content indicating access is blocked or restricted. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Analytics and tracking

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is inaccessible due to 403 Forbidden error.
  2. No metadata, scripts, forms, or external links found in HTML content.
  3. No privacy, cookie, or terms of service policies detected.
  4. No contact information or security policies available.
  5. WHOIS data is minimal but indicates domain is registered and active with GoDaddy nameservers.
  6. No evidence of WAF from major providers like Cloudflare; blocking appears generic or server-side.
  7. No business or branding information available from the site content.
  8. Analysis incomplete due to blocked content.
Technical notes

Notes

The website currently serves only a minimal HTML page with a 403 Forbidden status, indicating restricted access. No metadata, scripts, or frameworks are detectable. The domain uses GoDaddy nameservers, suggesting hosting or DNS management via GoDaddy, but no further hosting details are available. Performance, SEO, accessibility, and mobile optimization cannot be evaluated. The lack of content and technical signals indicates a need for significant modernization and configuration improvements.
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 kit-react.de. 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 kit-react.de.

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.