Skip to main content

Security report for vee24.com

Vee24 · Technology · N/a

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

Security score

71/100

Risk levelMedium

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

Vee24 operates as an enterprise-focused technology company specializing in video chat and virtual consultation platforms designed to enhance digital customer experiences. Their services target luxury retail, beauty, home furnishing, automotive, and financial services sectors, positioning them as a key player in video commerce and virtual appointments. The website reflects a mature digital presence with professional branding, clear messaging, and a focus on increasing sales and customer satisfaction through innovative digital engagement tools. Technically, the website leverages modern web technologies including React, JSON-LD structured data, and custom scripts hosted on dedicated CDNs. The site is mobile-optimized, accessible, and SEO-friendly, with fast loading times and a clean user interface. Privacy and cookie compliance are well implemented, with clear policies and consent mechanisms in place. From a security perspective, the site uses HTTPS and secure form inputs but lacks explicit security headers and published security policies or incident response contacts. No vulnerabilities or malicious content were detected, and trust is bolstered by certifications such as AICPA SOC and reputable client logos. The absence of WHOIS data is a minor concern but does not significantly detract from the overall trustworthiness. Overall, Vee24 presents a low-risk profile with strong business credibility and technical maturity. Strategic improvements in security transparency and header implementation would further enhance their security posture and trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
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

5 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

    • 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

  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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching vee24.com

This scan found 22 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
30
Email security
85
DNS health
85
Network security
100
GDPR outside view
53
Average
71

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 vee24.com, from OffSeq Breach.

Total records
115
Employees
37
Customers
56
Third parties
22
Weak passwords
0%

Latest record dated 2026-06-08 · 19 subdomains 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 vee24.com.

Select it in the checkout above.

Masked preview

  • –agent-dev.vee24.com2026-06-08
  • –admin.vee24.com2026-06-07
  • –agent-us.vee24.com2026-06-07
  • –agent.vee24.com2026-06-07
  • –agent-dev.vee24.com2026-06-07

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

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Vee24 is positioned as a B2B SaaS provider delivering enterprise video chat and virtual consultation solutions primarily to luxury and retail sectors. Their competitive advantage lies in specialized digital engagement tools that integrate scheduling and video commerce to boost customer loyalty and sales. The company targets medium to large enterprises seeking to modernize customer interactions online. Revenue streams likely include subscription-based licensing and service fees. The presence of high-profile clients and certifications indicates a stable partnership ecosystem and a focus on compliance. Growth indicators include active content marketing and a strong social media presence. No parent or subsidiary companies were identified, suggesting an independent operation focused on niche market leadership.

Security posture

The website demonstrates a moderate to strong security posture with HTTPS enforced and secure form handling. However, the absence of key security headers such as Content-Security-Policy and Strict-Transport-Security reduces defense-in-depth. No published security or incident response policies limit transparency and preparedness visibility. GDPR compliance is indicated through privacy and cookie policies, but no dedicated data protection officer contact was found. No vulnerabilities or exposed sensitive data were detected in the analysis. Overall, the security maturity is adequate for the business type but could be improved by formalizing security governance and enhancing technical controls.

Recommendations

  1. Implement and publish comprehensive security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  2. Create and publish a formal security policy and incident response contact information to improve transparency and readiness.
  3. Establish a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  4. Regularly audit third-party scripts and dependencies to mitigate supply chain risks.
  5. Enhance visibility of data protection officer or privacy contact to strengthen GDPR compliance signals.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Vee24
Description
Enterprise video chat and virtual consultation platform that transforms digital customer experience by enabling seamless scheduling, video consultations, and appointment booking to increase sales and customer satisfaction.
Key services
Enterprise video chat, Virtual consultations, Appointment scheduling, Digital customer experience enhancement
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, React (implied by react-helmet meta tags), JSON-LD structured data, Custom Vee24 scripts, CDN usage (cdn.vee24.com)
Frameworks
React
Platforms
Web
Performance
moderate
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced (implied by canonical URL and script sources)
  • Secure form inputs with proper attributes
  • Cookie consent mechanism implemented

Analytics and tracking

Tracking level
minimal
Privacy practices
good

Advertising

Marketing tools
Vee24 live engagement scripts
Transparency
basic

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is fully accessible with rich content and professional design.
  2. No WAF or blocking mechanisms detected.
  3. WHOIS data unavailable, which is unusual but not uncommon for privacy reasons.
  4. Strong branding and trust signals including certifications and client logos.
  5. Good privacy and cookie compliance with clear policies and consent mechanisms.
  6. No explicit security policy or incident response information published.
  7. No suspicious or malicious content detected.
  8. Use of modern web technologies and structured data for SEO and rich snippets.
Technical notes

Notes

The website is built on a modern JavaScript framework (likely React) with structured data implemented via JSON-LD for SEO and rich snippets. It uses custom scripts hosted on dedicated CDNs, ensuring performance and scalability. The site is mobile-optimized with responsive design and accessibility considerations. No CMS was detected, suggesting a custom or headless architecture. Performance is moderate with potential for optimization. Technical debt appears low, but security header implementation is lacking. Opportunities exist to improve technical SEO and security hardening to reduce risk and improve user trust.
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 vee24.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 vee24.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.