Skip to main content
lindseyfuneral.com

lindseyfuneral.com

https://lindseyfuneral.com

Last scanned October 19, 2026

A cookie scan of lindseyfuneral.com performed on October 19, 2026 found 10 cookies and 15 third-party tracking requests. The assessment covered 9 pages across 9 unique page templates. The site uses Osano as its consent management platform. Neither IAB TCF v2.3 nor Google Consent Mode v2 was observed on our check. 15 third-party requests were detected from 8 vendors.

Cookies

10

Third-party

0

Trackers

15

Vendors

8

Consent banner

Osano

Scans

1

What this setup is missing

  • Google tags were observed, but Google Consent Mode v2 was not detected.

Compliance by audience

European Union

✗ Not met

GDPR + ePrivacy · Prior consent (opt-in)

United Kingdom

✗ Not met

UK GDPR + PECR · Consent-based

United States

✓ Meets this model

CCPA/CPRA + state laws · Notice & opt-out

Canada

! Needs attention

PIPEDA + Québec Law 25 · Consent-based

Brazil

! Needs attention

LGPD · Consent-based

Scanned from the EU; sites may serve different banners or tracking to other regions. Verdicts reflect observed behaviour measured against each audience's rules.

Connection security

HTTPS supported

✓

Redirects HTTP to HTTPS

✓

HSTS

✗

Content Security Policy

✗

Cookies

10 cookies detected: 0 necessary, 3 analytics, 1 marketing

Total

10

Necessary

0

Functional

3

Analytics

3

Marketing

1

Unknown

3

Filter by category
Name Domain Category Provider Expiry Secure HttpOnly Party
_ga before consent .lindseyfuneral.com Analytics Google Analytics 1.1 yr lifetime over 13 months – – 1st
_ga_DD8BLHH1BP before consent .lindseyfuneral.com Analytics Google Analytics 1.1 yr lifetime over 13 months – – 1st
_ga_R30E4QH7G5 before consent .lindseyfuneral.com Analytics Google Analytics 1.1 yr lifetime over 13 months – – 1st
AWSALB before consent www.lindseyfuneral.com Functional Amazon Web Services 7 d – – 1st
AWSALBCORS before consent www.lindseyfuneral.com Functional Amazon Web Services 7 d ✓ – 1st
__RequestVerificationToken before consent www.lindseyfuneral.com Functional Microsoft Session ✓ ✓ 1st
_fbp before consent .lindseyfuneral.com Marketing Facebook 90 d – – 1st
fullthrottlelims_t2 before consent www.lindseyfuneral.com Unknown - 1.1 yr lifetime over 13 months – – 1st
r before consent www.lindseyfuneral.com Unknown - Expired – – 1st
tcouuid before consent www.lindseyfuneral.com Unknown - Expired – – 1st

Browser storage set by the site

Name Domain Party
_1792367372161 set by cmp.osano.com/osano.js https://www.lindseyfuneral.com 1st before consent
osano_consentmanager_tattles set by cmp.osano.com/osano.js https://www.lindseyfuneral.com 1st before consent
uw-uid set by cmp.osano.com/osano.js https://www.lindseyfuneral.com 1st before consent
uw-tunings set by cmp.osano.com/osano.js https://www.lindseyfuneral.com 1st before consent
uw-tunings-checksum set by cmp.osano.com/osano.js https://www.lindseyfuneral.com 1st before consent
uw-icon-locales set by cmp.osano.com/osano.js https://www.lindseyfuneral.com 1st before consent
lastExternalReferrer set by cmp.osano.com/osano.js https://www.lindseyfuneral.com 1st before consent
lastExternalReferrerTime set by cmp.osano.com/osano.js https://www.lindseyfuneral.com 1st before consent
_1792367377320 set by cmp.osano.com/osano.js https://www.lindseyfuneral.com 1st before consent
_1792367377545 set by cmp.osano.com/osano.js https://www.lindseyfuneral.com 1st before consent
_1792367377691 set by cmp.osano.com/osano.js https://www.lindseyfuneral.com 1st before consent
_1792367386073 set by cmp.osano.com/osano.js https://www.lindseyfuneral.com 1st before consent
_1792367386514 set by cmp.osano.com/osano.js https://www.lindseyfuneral.com 1st before consent
_1792367386670 set by cmp.osano.com/osano.js https://www.lindseyfuneral.com 1st before consent
_1792367389094 set by cmp.osano.com/osano.js https://www.lindseyfuneral.com 1st before consent
_1792367389502 set by cmp.osano.com/osano.js https://www.lindseyfuneral.com 1st before consent
_1792367390043 set by cmp.osano.com/osano.js https://www.lindseyfuneral.com 1st before consent

Third-Party Trackers

15 requests detected from 8 vendors: convertexperiments.com, ftlaunchpad.ai, Google LLC, Adobe Fonts, Meta Platforms, Inc....

Analytics

4

Marketing

2

Necessary

6

Functional

1

Other

2

Vendor Category Type Domain
convertexperiments.com before consent convertexperiments.com tracker domain (source: Disconnect.me, category: Analytics) Analytics script cdn-4.convertexperiments.com
ftlaunchpad.ai before consent Analytics script ftlaunchpad.ai
Google LLC before consent Google Tag Manager Analytics script www.googletagmanager.com
Google LLC before consent Google tracker domain (source: Disconnect.me, category: Analytics) Analytics script region1.analytics.google.com
Adobe Fonts before consent Adobe Fonts (Typekit): web font delivery Functional script use.typekit.net
Meta Platforms, Inc. before consent Facebook SDK / Pixel Marketing script connect.facebook.net
Meta Platforms, Inc. before consent Facebook tracking pixel Marketing pixel www.facebook.com
Amazon Amazon tracker domain (source: Disconnect.me, category: Content) Necessary script d2zeeo94hsmapq.cloudfront.net
Amazon Amazon tracker domain (source: Disconnect.me, category: Content) Necessary script s3.amazonaws.com
Cloudflare Inc. Cloudflare CDNJS Necessary script cdnjs.cloudflare.com
Google LLC Google Fonts stylesheet Necessary script fonts.googleapis.com
Google LLC Google tracker domain (source: Disconnect.me, category: Content) Necessary script www.google.dk
Google LLC Google Fonts files Necessary script fonts.gstatic.com
Google LLC before consent Google tracker domain (source: Disconnect.me, category: FingerprintingGeneral) Unknown script stats.g.doubleclick.net
Osano Osano tracker domain (source: Disconnect.me, category: ConsentManagers) Unknown script cmp.osano.com

Scan history

One completed scan: cookies and trackers from the scan on October 19, 2026.

Recent scans

October 19, 2026 10 15

Is lindseyfuneral.com your website?

Claim it to monitor your cookies and trackers, set up a consent banner with automatic script blocking, and keep your cookie policy up to date.