Skip to main content

Security report for oreillyauto.com

Other · N/a

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

Security score

65/100

Risk levelMedium

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

The website www.oreillyauto.com is currently inaccessible due to an access denied error, indicating a security or firewall block preventing content retrieval. The WHOIS lookup failed to return any registration data, suggesting the domain may not be properly registered or is under privacy protection. Due to the lack of accessible content, no metadata, business information, or technical details could be extracted. This severely limits the ability to assess the company's digital maturity or security posture. The absence of privacy policies, contact information, or security headers further complicates trust evaluation. Overall, the site appears to be either misconfigured or protected by a restrictive security mechanism, resulting in a very low confidence in legitimacy and security.

Scanned

NIS2 and GDPR posture

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

8 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 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 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 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 oreillyauto.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
57
Security headers
15
Email security
85
DNS health
85
Network security
100
GDPR outside view
50
Average
65

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

Total records
54,005
Employees
25
Customers
53,802
Third parties
178
Weak passwords
7%

Latest record dated 2026-06-12 · 88 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 oreillyauto.com.

Select it in the checkout above.

Masked preview

  • –supplyline-stage.oreillyauto.com2026-06-12
  • –lc2222.oreillyauto.com2026-05-25
  • –lc2021.oreillyauto.com2026-05-15
  • –lc2021.oreillyauto.com2026-05-15
  • –teamcluster.oreillyauto.com2026-05-08

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

No business intelligence could be gathered from the website due to the access denial. The domain WHOIS data is missing, preventing verification of company registration or ownership. Without content or metadata, no insights into market positioning, business model, or partnerships are available. The lack of accessible contact or corporate information suggests either a staging environment, a domain parking state, or a misconfigured security setting.

Security posture

The security posture cannot be properly evaluated as the website content is blocked by an access denied page. No security headers or HTTPS status could be verified. The WHOIS data absence raises concerns about domain registration legitimacy. No incident response or vulnerability disclosure information is available. The site is effectively inaccessible, which may be intentional for security or operational reasons but limits transparency and trust.

Recommendations

  1. Resolve the access denial issue to allow legitimate users and security tools to access the website content.
  2. Ensure proper domain registration information is published and accessible via WHOIS.
  3. Implement and verify HTTPS with strong SSL/TLS configuration and security headers.
  4. Publish clear privacy, cookie, and terms of service policies to improve compliance and trust.
  5. Provide visible contact and incident response information to enhance security posture and customer confidence.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Access Denied page detected with minimal HTML content and no access to website data. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Analytics and tracking

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is completely blocked by access denial.
  2. No metadata, scripts, or external links available for analysis.
  3. WHOIS data is unavailable or domain is not registered properly.
  4. No privacy, cookie, or terms of service policies found.
  5. No contact or business information is accessible.
  6. Security posture cannot be assessed due to lack of access.
  7. Content safety is rated safe due to absence of content.
  8. Overall analysis is incomplete due to WAF/security blocking.
Technical notes

Notes

Due to the access denied response, no technical stack, CMS, or hosting provider information could be detected. No scripts, meta tags, or structured data are present in the minimal HTML content. The domain's DNS and SSL configuration cannot be assessed. The site appears to be protected by a generic WAF or security mechanism blocking all access, which prevents any meaningful technical analysis.
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 oreillyauto.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 oreillyauto.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.