Skip to main content

Security report for petrovisor.com

Weatherford · Energy · United States

High risk. 7 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

47/100

Risk levelHigh

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

Weatherford's PetroVisor website presents a mature and comprehensive SaaS platform focused on unifying data and analytics for the energy sector, specifically oil and gas production optimization. The platform integrates AI/ML capabilities and offers multiple modules addressing production, artificial lift, completion optimization, ESG, and enhanced oil recovery. The website is professionally designed, content-rich, and targets enterprise-level energy industry professionals. Technically, the site uses a modern tech stack including Kentico CMS, jQuery, and various analytics and marketing tools. However, a critical security gap exists as the site lacks a valid SSL certificate and does not serve content over HTTPS, exposing users to potential risks. Privacy and cookie policies are present and indicate GDPR compliance, but no explicit security incident response or vulnerability disclosure information is found. Overall, the domain registration data supports the legitimacy and maturity of the business. Strategic security improvements are necessary to enhance trust and protect user data.

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

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • 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. 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

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  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 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 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 petrovisor.com

This scan found 17 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
0
Security headers
35
Email security
50
DNS health
80
Network security
100
GDPR outside view
15
Average
47

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

The website positions Weatherford as an established enterprise in the energy sector with a focus on digital transformation through its PetroVisor platform. The business model is B2B SaaS, targeting oil and gas operators seeking integrated data solutions for operational efficiency and sustainability. The product suite covers a broad range of E&P lifecycle needs, leveraging AI and machine learning to deliver actionable insights. The presence of investor relations, newsroom, and detailed product tours indicates a well-structured marketing and communication strategy. The domain age and DNS setup reflect a stable and consistent online presence. The company leverages partnerships and integrations with cloud and CDN providers to deliver content globally. However, the lack of HTTPS may impact customer trust and compliance with industry standards.

Security posture

The website demonstrates some security best practices such as setting X-Frame-Options to SAMEORIGIN, using HttpOnly and SameSite cookie attributes, and implementing Google reCAPTCHA on forms to prevent automated abuse. However, the absence of a valid SSL certificate and lack of HTTPS support is a critical vulnerability that severely undermines the security posture. No HSTS header is present to enforce secure connections. TLS protocols and cipher suites are not supported, indicating no encrypted transport layer. There is no evidence of OCSP stapling or session resumption mechanisms. The site does not provide explicit security policies or incident response contacts, which limits transparency and preparedness. Overall, the security posture is weak and requires urgent remediation to protect user data and maintain compliance.

Recommendations

  1. Implement a valid SSL/TLS certificate and enforce HTTPS site-wide to secure data in transit.
  2. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  3. Upgrade server configuration to support modern TLS protocols (TLS 1.2 and TLS 1.3) and strong cipher suites.
  4. Publish a clear security policy and incident response contact information to improve transparency and trust.
  5. Regularly audit and update security headers and cookie attributes to align with best practices.
  6. Enhance accessibility and SEO features to improve user experience and search engine ranking.
  7. Maintain and promote privacy compliance with clear GDPR statements and cookie consent mechanisms.
Technical notes

Notes

The website is built on the Kentico CMS platform and uses a variety of modern JavaScript libraries including jQuery, jQuery UI, Slick Carousel, FancyBox, Mustache.js, and GSAP TweenMax for UI and animations. It integrates Google Tag Manager and Bizible for analytics and marketing tracking, and Wistia for video content delivery. Hosting and DNS are managed via Microsoft Azure DNS and Akamai CDN, indicating a robust global delivery infrastructure. The site is mobile responsive with adaptive images and media queries. However, performance metrics are not available, and the lack of HTTPS is a significant technical risk. The site uses Google reCAPTCHA to protect forms from spam. Overall, the technical infrastructure is modern and well-structured but requires security enhancements.
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 petrovisor.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 petrovisor.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.