Skip to main content

Security report for vod309.com

Veeva Systems Inc. · Healthcare · United States

High risk. 7 critical or high findings in SSL/TLS, Security headers and 1 other check.

Security score

48/100

Risk levelHigh

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

Veeva Systems Inc. is a well-established enterprise software company specializing in cloud-based solutions for the global life sciences industry. The company offers a broad portfolio of products and services including clinical, regulatory, safety, quality, medical, commercial, data, and AI solutions. Their market position is strong, supported by a large customer base and comprehensive service offerings tailored to pharmaceutical, biotech, and related sectors. The website reflects a mature digital presence with professional design, clear navigation, and extensive content that supports their business objectives. Technically, the website is built on WordPress with modern frameworks like Bootstrap and uses several third-party analytics and marketing tools such as New Relic, Matomo, and Marketo. The site is hosted on AWS infrastructure, ensuring scalability and reliability. Performance is moderate with good mobile optimization and accessibility features, although some improvements could be made in loading speed and technical SEO. From a security perspective, the site lacks a valid SSL/TLS certificate and does not support modern TLS protocols, which is a critical vulnerability that undermines user trust and data protection. While some security headers and email authentication mechanisms like SPF and DMARC are in place, the absence of HTTPS and weak SSL configuration significantly lowers the security posture. Privacy compliance is well addressed with clear privacy and cookie policies and consent mechanisms, aligning with GDPR requirements. Overall, the website demonstrates high business credibility and professionalism but requires urgent security enhancements to protect user data and maintain trust. Addressing SSL/TLS issues and strengthening security configurations should be prioritized to improve the overall risk profile and user confidence.

Scanned

NIS2 and GDPR posture

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

    • Critical

      Unable to retrieve SSL certificate

      Could not establish secure connection to retrieve certificate information

      What to do: Check if the server is accessible and SSL/TLS is properly configured

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

  3. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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

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

Keep watching vod309.com

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
0
Security headers
25
Email security
60
DNS health
80
Network security
100
GDPR outside view
25
Average
48

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

Total records
6
Employees
0
Customers
6
Third parties
0
Weak passwords
0%

3 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 vod309.com.

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

Veeva Systems operates as a leading provider of cloud-based software solutions tailored for the life sciences sector, including pharmaceuticals, biotech, medical devices, and consumer health. Their business model focuses on delivering integrated software platforms that streamline clinical trials, regulatory compliance, safety monitoring, quality management, medical affairs, commercial operations, and data analytics. The company leverages strategic partnerships and a broad ecosystem to enhance its offerings, including education services, consulting, and AI-driven tools. Their market positioning is strong, supported by a mature domain and consistent branding. The extensive product catalog and customer testimonials indicate a well-established revenue stream and a focus on enterprise clients. The presence of multiple regional sites and language options suggests a global reach. The company invests in marketing and analytics technologies to optimize customer engagement and operational efficiency.

Security posture

The current security posture of the website is moderate but with critical deficiencies. The lack of a valid SSL/TLS certificate and disabled TLS protocols expose the site to significant risks including data interception and loss of user trust. While SPF and DMARC records are properly configured, DNSSEC is not enabled, which could improve domain integrity. Security headers are present but incomplete, and advanced features like OCSP stapling and session resumption are missing. The site does not display any dedicated security or incident response policies, nor does it provide vulnerability disclosure information. Privacy policies and cookie consent mechanisms are well implemented, indicating compliance with data protection regulations. Overall, the site requires immediate remediation of SSL/TLS issues and enhancement of security configurations to meet industry best practices and protect sensitive data.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable and configure modern TLS protocols (TLS 1.2 and TLS 1.3) and disable legacy protocols.
  3. Implement full HSTS policy with includeSubDomains and preload directives.
  4. Enable OCSP stapling and session resumption to improve security and performance.
  5. Consider enabling DNSSEC to enhance domain security.
  6. Publish a dedicated security policy and incident response page to improve transparency.
  7. Establish a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  8. Regularly audit third-party scripts and libraries to avoid vulnerabilities.
  9. Improve website performance and loading speed for better user experience.
  10. Maintain and update privacy and cookie policies to ensure ongoing compliance.

Contact details published on the site

Addresses
Legal name
Veeva Systems Inc.
Technical notes

Notes

The website is built on WordPress CMS with Bootstrap 5 framework and uses jQuery and Font Awesome for UI components. It integrates third-party services including New Relic for performance monitoring, Matomo for analytics, and Marketo for marketing automation. The hosting infrastructure is Amazon AWS, indicated by DNS records and nameservers. The site is mobile optimized with responsive design and accessibility features. SEO is well addressed with meta tags, Open Graph, and JSON-LD structured data. However, the site lacks a valid SSL certificate and modern TLS support, which is a critical technical flaw. Performance metrics are not provided but inferred as moderate. The site uses multiple external domains for content delivery and analytics. Overall, the technical stack is modern and robust but requires urgent security upgrades.
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 vod309.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 vod309.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.