Skip to main content

Security report for ortozes.lv

Other · N/a

Medium risk. 9 critical or high findings in GDPR outside view, Email security and 2 other checks.

Security score

59/100

Risk levelMedium

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

The website www.ortozes.lv is built on the Wix platform, indicating a small to medium-sized business presence. The site appears to be related to orthopedics or healthcare products, suggested by the domain name and typical Wix business usage, although no explicit business description or metadata was found in the provided content. The technical infrastructure relies on Wix's standard scripts and hosting, providing moderate performance and good mobile optimization. However, the lack of privacy, cookie, and terms of service policies, as well as absence of contact information, limits the site's compliance and business credibility. Security posture is moderate with HTTPS implied but missing explicit security headers and policies. The WHOIS data could not be retrieved due to query limits, which restricts domain legitimacy verification and reduces trust confidence. Overall, the site is accessible without WAF or blocking mechanisms but lacks comprehensive business and compliance information.

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. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  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 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 ortozes.lv

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

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 content and absence of structured business data, detailed business intelligence is constrained. The site likely targets customers in the healthcare or orthopedic sector, possibly retail or service provision. The business model appears to be direct-to-consumer or informational. No partnerships, certifications, or market positioning details are evident. The use of Wix suggests a small business or startup stage. No revenue streams or growth indicators are visible. The lack of contact and policy information may impact customer trust and regulatory compliance.

Security posture

The security maturity level is basic to moderate. HTTPS is used, but no explicit security headers were detected in the provided content. There is no evidence of vulnerability disclosures, incident response contacts, or security policies. Cookie handling scripts show some security awareness but lack consent mechanisms or GDPR compliance indicators. The absence of WHOIS data limits domain trust verification. No vulnerable libraries or exposed sensitive data were identified in the visible scripts. Overall, the site would benefit from enhanced security headers, privacy policies, and incident response readiness to improve its security posture.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie consent mechanism to comply with GDPR and enhance user trust.
  2. Add clear contact information including company emails and phone numbers to improve business credibility and customer support.
  3. Enhance security by adding HTTP security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Establish an incident response policy and provide security contact channels (e.g., security@ or abuse@ emails).
  5. Regularly monitor and update third-party scripts and dependencies to mitigate potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
basic
Branding
moderate

Technology

Stack
Wix, core-js, focus-within-polyfill
Platforms
Wix.com Website Builder
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • HTTPS enforced (implied by https URL)
  • Cookie handling with some security restrictions

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is built on Wix platform with standard Wix scripts and assets.
  2. No WHOIS data available due to query limit error.
  3. No privacy, cookie, or terms of service policies detected in the HTML content.
  4. No contact emails, phone numbers, or social media links found in the provided content.
  5. No security or incident response policies found.
  6. No certifications or compliance indicators present.
  7. Content is minimal and mostly technical scripts and styles; no visible business descriptive content extracted.
  8. No forms detected in the provided HTML snippet.
  9. No SEO or Open Graph metadata found in the provided content.
  10. No analytics or tracking scripts detected beyond Wix platform scripts.
Technical notes

Notes

The website uses Wix CMS and hosting, leveraging Wix's standard JavaScript libraries and polyfills for compatibility. The site includes performance polyfills and cookie handling scripts but lacks advanced SEO metadata and structured data. Mobile optimization is good, but accessibility features are basic. The site does not appear to use external analytics or marketing tools beyond Wix's platform. Performance is moderate, with no evident critical technical debt but opportunities exist for SEO and accessibility improvements. The absence of WHOIS data and security headers are technical risks that should be addressed.
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 ortozes.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 ortozes.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.