Skip to main content

Security report for mobil.ca

Mobil · Energy · United States

Low risk. 3 critical or high findings in Security headers, Email security and 1 other check.

Security score

80/100

Risk levelLow

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

Mobil is a globally recognized brand specializing in fuels, lubricants, and advanced technology services, operating under the ExxonMobil corporate umbrella. The website reflects a mature enterprise digital presence with a focus on business and consumer audiences interested in energy products. The site is well-branded, professionally designed, and provides comprehensive information about Mobil's products and services. Technically, the site leverages modern web technologies including AWS hosting, Sitecore CMS, and integrates multiple marketing and analytics tools with a strong emphasis on privacy compliance via OneTrust. Security posture is robust with HTTPS enforcement, Content Security Policy, and other security headers, though explicit incident response and vulnerability disclosure information are not publicly available. Overall, the site demonstrates a high level of digital maturity and trustworthiness appropriate for a large energy sector enterprise.

Scanned

NIS2 and GDPR posture

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

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

    • High

      No SPF record found

      SPF helps prevent email spoofing

      What to do: Add SPF record: "v=spf1 include:_spf.yourmailprovider.com ~all"

  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 mobil.ca

This scan found 14 issues across 5 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
70
Email security
52
DNS health
85
Network security
100
GDPR outside view
100
Average
80

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

Mobil's market positioning as a leading energy and lubricants brand is supported by its integration within ExxonMobil's global operations. The business model targets both B2B and B2C segments, offering fuels, lubricants, and related technology services. The website's linkage to multiple regional Mobil domains and ExxonMobil corporate sites indicates a broad geographic footprint and a complex partnership ecosystem. The use of advanced analytics and marketing tools suggests a data-driven approach to customer engagement and market growth. The absence of direct contact information on the main site may indicate a preference for controlled communication channels or regional contact points.

Security posture

The website exhibits a strong security posture with enforced HTTPS, comprehensive Content Security Policy, and multiple security headers. The integration of cookie consent mechanisms and privacy policies aligns with GDPR compliance requirements. No exposed sensitive data or vulnerable libraries were detected in the provided content. However, the lack of publicly available incident response contacts or security.txt files represents a gap in transparency for vulnerability reporting. The use of multiple third-party scripts necessitates ongoing security audits to mitigate supply chain risks. Overall, the security maturity is high but could be enhanced by publishing explicit security policies and contact channels.

Recommendations

  1. Publish a security.txt file and vulnerability disclosure policy to facilitate responsible reporting.
  2. Add clear incident response contact information to improve transparency and trust.
  3. Regularly review and audit third-party scripts and libraries for vulnerabilities.
  4. Enhance accessibility features with ARIA roles and landmarks for improved compliance.
  5. Maintain and update privacy and cookie policies to reflect evolving regulations.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Mobil
Description
Known for performance and innovation, and recognized for our advanced technology in fuels, lubricants and services.
Key services
fuels, lubricants, technology services
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, AWS, Google Tag Manager, OneTrust, Coveo Search, Slick Carousel
Frameworks
Bootstrap
Platforms
AWS Cloud
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Content Security Policy implemented
  • Cookie consent banner
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics, AppDynamics, Foresee, Pardot
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
DoubleClick, Google Ads, Taboola, Outbrain
Tracking pixels
AppDynamics, Brightcove, BazaarVoice, PriceSpider, LeadForensics, Spotify Pixels
Marketing tools
Pardot, Foresee, OneTrust
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenge.
  2. Strong corporate branding consistent with ExxonMobil ownership.
  3. Comprehensive privacy and cookie policies with consent management.
  4. No direct contact emails or phone numbers found on main page.
  5. Use of multiple third-party marketing and analytics tools with consent.
  6. Good security posture with CSP and HTTPS enforced.
  7. No evidence of vulnerabilities or exposed sensitive data.
  8. No adult or questionable content detected.
  9. WHOIS data is privacy protected or unavailable, typical for large brands.
Technical notes

Notes

Mobil.com is hosted on AWS and built using the Sitecore CMS platform, leveraging modern JavaScript libraries and frameworks such as Bootstrap and Slick Carousel. The site implements advanced content delivery and analytics integrations including Google Tag Manager, OneTrust for consent management, and Coveo for search functionality. Performance is moderate with good mobile optimization and accessibility features. The technical infrastructure supports a scalable and secure enterprise-grade website, though continuous monitoring and optimization are recommended to maintain performance and security standards.
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 mobil.ca. 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 mobil.ca.

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.