Does beacon333.com use cookies?

beacon333.com uses 5 cookies. No consent management platform was detected.

Does beacon333.com use a cookie banner (CMP)?

No consent management platform (cookie banner) was detected on beacon333.com. Since the site sets non-essential cookies or loads third-party trackers, it may not meet GDPR and ePrivacy prior-consent requirements.

Which third-party trackers does beacon333.com use?

beacon333.com loads 7 third-party requests from 4 vendors, including Google LLC, Automattic, Awes.me, Brightcove.

How many marketing and analytics cookies does beacon333.com set?

beacon333.com sets 0 marketing and 2 analytics cookies, alongside 0 strictly necessary cookies. Under GDPR and the ePrivacy Directive, non-essential cookies require prior consent.

beacon333.com

Item: beacon333.com
Rating: 47
Author: Passiro

https://beacon333.com

Last scanned August 11, 2026

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

Claim & unlock

Third-party

Trackers

Vendors

Consent banner

None detected

Scans

What this setup is missing

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

! 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

5 cookies detected: 0 necessary, 2 analytics, 0 marketing

Total

Necessary

Functional

Analytics

Marketing

Unknown

Filter by category

Name	Domain	Category	Provider	Expiry	Secure	HttpOnly	Party
_ga before consent	.beacon333.com	Analytics	Google Analytics	1.1 yr lifetime over 13 months	–	–	1st
_ga_RZMNCKSTGC before consent	.beacon333.com	Analytics	Google Analytics	1.1 yr lifetime over 13 months	–	–	1st
cookielawinfo-checkbox-necessary before consent	beacon333.com	Functional	Cookie Law Info	365 d	–	–	1st
cookielawinfo-checkbox-non-necessary before consent	beacon333.com	Functional	Cookie Law Info	365 d	–	–	1st
humans_21909 before consent	beacon333.com	Unknown	-	Session	–	–	1st

Browser storage set by the site

Name	Domain	Party
modernizr set by beacon333.com/modernizr.js	https://beacon333.com	1st	before consent
modernizr set by beacon333.com/modernizr.js	https://beacon333.com	1st	before consent
wpEmojiSettingsSupports set by beacon333.com/wp-emoji-loader.min.js:3:327	https://beacon333.com	1st	before consent

Third-Party Trackers

7 requests detected from 4 vendors: Google LLC, Automattic, Awes.me, Brightcove

Analytics

Marketing

Necessary

Functional

Other

Vendor	Category	Type	Domain
Google LLC before consent Google Tag Manager	Analytics	script	www.googletagmanager.com
Automattic Automattic tracker domain (source: Disconnect.me, category: Content)	Necessary	script	c0.wp.com
Awes.me Awes.me tracker domain (source: Disconnect.me, category: Content)	Necessary	script	live.staticflickr.com
Brightcove Brightcove tracker domain (source: Disconnect.me, category: Content)	Necessary	script	vjs.zencdn.net
Google LLC Google Fonts stylesheet	Necessary	script	fonts.googleapis.com
Google LLC Google Fonts files	Necessary	script	fonts.gstatic.com
Google LLC before consent Google tracker domain (source: Disconnect.me, category: FingerprintingGeneral)	Unknown	script	region1.google-analytics.com