Skip to main content

Security report for hagerty.com

Hagerty · Transportation · United States

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

Security score

78/100

Risk levelLow

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

Hagerty is a prominent provider of classic car insurance and automotive lifestyle services, including a marketplace for buying and selling vehicles, valuation tools, and a Drivers Club membership offering roadside assistance. The company targets classic car enthusiasts and collectors, positioning itself as a trusted leader in the niche automotive insurance market. The website is professionally designed with clear navigation and comprehensive content, reflecting a mature digital presence. Technically, the site leverages modern frameworks such as Next.js and React, employs HTTPS with strong security headers, and integrates third-party services like Tealium for tag management and Google reCAPTCHA for form security. Privacy and cookie policies are comprehensive and GDPR compliant, with consent mechanisms in place. However, explicit security policies and incident response information are not publicly available, and WHOIS data is missing or unavailable, which slightly impacts trust but is mitigated by the professional site and business indicators. Overall, the site demonstrates a strong security posture and digital maturity with minor areas for improvement in transparency and security disclosures.

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

4 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. 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 hagerty.com

This scan found 18 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
82
Security headers
70
Email security
80
DNS health
80
Network security
100
GDPR outside view
53
Average
78

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

Hagerty operates in the transportation and finance sectors, focusing on classic and collector vehicle insurance. Its business model combines insurance services with a digital marketplace and membership club, creating multiple revenue streams and customer engagement channels. The company benefits from a strong brand presence and consistent messaging targeting automotive enthusiasts. The marketplace and valuation tools enhance customer value and stickiness. While WHOIS data is unavailable, the site’s professional quality and comprehensive policies suggest a legitimate and established business. The absence of explicit security and incident response policies indicates an opportunity to strengthen trust and compliance. Hagerty’s integration of marketing and analytics tools like Tealium supports data-driven growth and customer insights.

Security posture

The website enforces HTTPS with excellent SSL configuration and implements key security headers such as Content-Security-Policy, Strict-Transport-Security, and X-Frame-Options, indicating a robust baseline security posture. Use of Google reCAPTCHA protects forms from automated abuse. No exposed sensitive data or vulnerable libraries were detected in the HTML content. However, the lack of publicly available security policies, incident response contacts, and vulnerability disclosure mechanisms represents a gap in transparency and readiness. The site would benefit from publishing a security policy and a security.txt file to facilitate responsible vulnerability reporting. Overall, the security posture is strong but could be enhanced with improved communication and formalized incident response information.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and compliance.
  2. Implement and publish a vulnerability disclosure policy or security.txt file.
  3. Provide clear incident response contact channels for security issues.
  4. Enhance accessibility features to improve inclusivity and compliance.
  5. Regularly audit third-party scripts and dependencies for vulnerabilities and update accordingly.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Hagerty
Description
Hagerty provides insurance for classic cars, boats, motorcycles, and more, protecting collectibles as if they were their own.
Key services
Classic car insurance, Boat insurance, Motorcycle insurance, Marketplace for auctions and classifieds, Drivers Club membership and roadside services, Valuation tools
Content quality
excellent
Branding
consistent

Technology

Stack
React, Next.js, JavaScript, CSS, Imgix (image CDN), Google reCAPTCHA, Tealium (tag management)
Frameworks
Next.js
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Use of reCAPTCHA for forms
  • No exposed sensitive data in HTML
  • Security headers present

Analytics and tracking

Services
Tealium
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Tealium
Marketing tools
Tealium
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 rich content and navigation.
  2. No WAF or blocking mechanisms detected.
  3. WHOIS data is missing or unavailable, which is unusual but not necessarily suspicious given the professional site.
  4. Strong privacy and cookie policies with consent mechanisms present.
  5. No explicit security policy or incident response info found.
  6. No vulnerability disclosure or security.txt found.
  7. Multiple external scripts and tag management tools used, mainly Tealium.
  8. No exposed emails or phone numbers in the main HTML; contact via forms and roadside service phone number found.
  9. No suspicious or malicious domains linked.
  10. Content is safe and targeted at general automotive enthusiasts.
Technical notes

Notes

The website is built using modern web technologies including React and Next.js, enabling server-side rendering and optimized performance. It uses Imgix for image delivery, improving load times and responsiveness. Tag management and analytics are handled via Tealium, and Google reCAPTCHA is integrated for form security. The site demonstrates fast loading times, excellent mobile optimization, and good SEO practices with proper meta tags and Open Graph data. No CMS was explicitly detected, suggesting a custom or headless architecture. Hosting provider details are not evident from the HTML. The technical implementation reflects a mature and well-maintained digital infrastructure with opportunities to improve transparency around security and data retention.
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 hagerty.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 hagerty.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.