Skip to main content
iamtaylorstone.com

iamtaylorstone.com

https://iamtaylorstone.com

Last scanned October 1, 2026

A cookie scan of iamtaylorstone.com performed on October 1, 2026 found 21 cookies and 5 third-party tracking requests. The assessment covered 10 pages across 10 unique page templates. No consent management platform was detected. Our check observed 5 third-party requests from 4 vendors; non-essential tracking of this kind requires prior consent under the ePrivacy Directive.

Cookies

21

Third-party

0

Trackers

5

Vendors

4

Consent banner

None detected

Scans

1

What this setup is missing

  • No consent management platform was 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

! Needs attention

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

21 cookies detected: 2 necessary, 1 analytics, 0 marketing

Total

21

Necessary

2

Functional

7

Analytics

1

Marketing

0

Unknown

11

Filter by category
Name Domain Category Provider Expiry Secure HttpOnly Party
_scc_session before consent .iamtaylorstone.com Analytics Marfeel Expired ✓ – 1st
cookielawinfo-checkbox-advertisement before consent iamtaylorstone.com Functional Cookie Law Info 362 d – – 1st
cookielawinfo-checkbox-analytics before consent iamtaylorstone.com Functional Cookie Law Info 362 d – – 1st
cookielawinfo-checkbox-functional before consent iamtaylorstone.com Functional Cookie Law Info 362 d – – 1st
cookielawinfo-checkbox-necessary before consent iamtaylorstone.com Functional Cookie Law Info 362 d – – 1st
cookielawinfo-checkbox-others before consent iamtaylorstone.com Functional Cookie Law Info 362 d – – 1st
cookielawinfo-checkbox-performance before consent iamtaylorstone.com Functional Cookie Law Info 362 d – – 1st
wordpress_test_cookie before consent iamtaylorstone.com Functional Wordpress Session ✓ ✓ 1st
PHPSESSID iamtaylorstone.com Necessary PHP Session ✓ ✓ 1st
__cf_bm .iamtaylorstone.com Necessary Cloudflare Expired ✓ ✓ 1st
cp_challenge before consent iamtaylorstone.com Unknown - Session – – 1st
last_pysTrafficSource before consent .iamtaylorstone.com Unknown - 4 d – – 1st
last_pys_landing_page before consent .iamtaylorstone.com Unknown - 4 d – – 1st
pysTrafficSource before consent .iamtaylorstone.com Unknown - 4 d – – 1st
pys_cd before consent .iamtaylorstone.com Unknown - 362 d – – 1st
pys_first_visit before consent .iamtaylorstone.com Unknown - 4 d – – 1st
pys_landing_page before consent .iamtaylorstone.com Unknown - 4 d – – 1st
pys_session_limit before consent .iamtaylorstone.com Unknown - Expired – – 1st
pys_start_session before consent .iamtaylorstone.com Unknown - Session – – 1st
_tccl_visit before consent .iamtaylorstone.com Unknown - Expired ✓ – 1st
_tccl_visitor before consent .iamtaylorstone.com Unknown - 362 d ✓ – 1st

Third-Party Trackers

5 requests detected from 4 vendors: csp.secureserver.net, img1.wsimg.com, Go Daddy, Google LLC

Analytics

2

Marketing

0

Necessary

3

Functional

0

Other

0

Vendor Category Type Domain
csp.secureserver.net before consent Analytics fetch csp.secureserver.net
img1.wsimg.com before consent Analytics script img1.wsimg.com
Go Daddy Go Daddy tracker domain (source: Disconnect.me, category: Content) Necessary script captcha.wpsecurity.godaddy.com
Google LLC Google Fonts stylesheet Necessary script fonts.googleapis.com
Google LLC Google Fonts files Necessary script fonts.gstatic.com

Scan history

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

Recent scans

October 1, 2026 21 5

Is iamtaylorstone.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.