Skip to main content

Security report for wearecreate.lv

Other · N/a

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

Security score

60/100

Risk levelMedium

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

The website wearecreate.lv is currently inaccessible beyond a security CAPTCHA challenge page implemented by BitNinja. This page is designed to block automated or suspicious visitors and requires CAPTCHA validation to proceed. Due to this, no business or service information is available on the site. The presence of outdated CMS meta tags (Joomla 1.5, WordPress 2.5, Drupal) suggests legacy technology usage, which may pose security risks if the actual site is running these versions. The technical infrastructure includes Google Analytics and Google Tag Manager for tracking, and Google reCAPTCHA v2 for bot mitigation. The security posture is limited to the CAPTCHA challenge with no visible security headers or HTTPS verification in the provided data. WHOIS data is unavailable due to query limits, preventing verification of domain registration details. Overall, the site is currently blocked for analysis, limiting insights into business operations or compliance.

Scanned

NIS2 and GDPR posture

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

9 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

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

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

Keep watching wearecreate.lv

This scan found 24 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
72
Security headers
20
Email security
85
DNS health
75
Network security
100
GDPR outside view
10
Average
60

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

No business intelligence data is available from the site content due to the blocking security page. No contact information, privacy policies, or company details are present. The site appears to be protected by BitNinja security services, indicating a focus on security but limiting transparency. No partnerships or related domains are identified. The business sector and model cannot be determined from the available data.

Security posture

The security posture is primarily based on the BitNinja CAPTCHA challenge to prevent automated access. While this is a positive security control, the lack of visible HTTPS confirmation, security headers, or privacy compliance documentation reduces the overall security maturity. The use of outdated CMS versions indicated in meta tags may represent a risk if still in use. No incident response or vulnerability disclosure information is found. The WHOIS data is inaccessible, which limits trust verification. Overall, the site demonstrates basic bot mitigation but lacks comprehensive security best practices.

Recommendations

  1. Implement and enforce HTTPS with a valid SSL/TLS certificate and verify configuration.
  2. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish clear privacy, cookie, and terms of service policies to improve compliance and transparency.
  4. Update or replace legacy CMS platforms to supported, secure versions to reduce vulnerabilities.
  5. Make WHOIS domain registration data accessible and consistent with business identity to improve trust.
Site observations

Automated reading of the public site. Ratings are indicative.

BitNinja detected. The website content is a BitNinja security CAPTCHA challenge page blocking access until CAPTCHA is solved. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Description
This page is a security CAPTCHA challenge page designed to block automated or suspicious visitors. It does not provide business or service information.
Content quality
basic
Branding
moderate

Technology

Stack
Joomla 1.5, WordPress 2.5, Drupal, Google Analytics, Google Tag Manager, reCAPTCHA v2
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
30/100
Good practices seen
  • Use of Google reCAPTCHA v2 for bot mitigation
  • Security challenge page to block suspicious IPs

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is currently blocked by a BitNinja security CAPTCHA challenge.
  2. No business or contact information is available on the page.
  3. WHOIS data is inaccessible due to query limit error.
  4. Website uses outdated CMS versions (Joomla 1.5, WordPress 2.5) indicated in meta tags, which may pose security risks.
  5. Google Analytics and Google Tag Manager are used for tracking.
  6. No privacy, cookie, or terms of service policies found.
  7. No contact emails, phone numbers, or social media links found.
  8. Page content is minimal and focused solely on bot mitigation.
Technical notes

Notes

The site uses legacy CMS platforms indicated by meta tags (Joomla 1.5, WordPress 2.5, Drupal), which are outdated and potentially vulnerable. Google Analytics and Google Tag Manager are integrated for user tracking. The site employs Google reCAPTCHA v2 for bot mitigation. The page content is minimal and focused on security challenge functionality. No advanced frameworks or modern platforms are detected. Performance is moderate but limited by the security challenge. Mobile optimization and accessibility are basic. SEO optimization is poor due to minimal metadata and no visible content beyond the CAPTCHA page.
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 wearecreate.lv. 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 wearecreate.lv.

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.