Does historydb.date use cookies?

historydb.date uses 6 cookies. No consent management platform was detected.

Does historydb.date use a cookie banner (CMP)?

No consent management platform (cookie banner) was detected on historydb.date. 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 historydb.date use?

historydb.date loads 6 third-party requests from 3 vendors, including Microsoft, Yahoo!, consentmanager GmbH.

How many marketing and analytics cookies does historydb.date set?

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

historydb.date

Item: historydb.date
Author: Passiro

https://historydb.date

Last scanned Jul 7, 2026

A cookie scan of historydb.date completed on July 7, 2026 found 6 cookies and 6 third-party tracking requests. No consent management platform was detected. Our check observed 6 third-party requests from 3 vendors, which require prior consent under GDPR and the ePrivacy Directive.

Claim & unlock

Third-party

Trackers

Vendors

Consent banner

None detected

Scans

Cookies

6 cookies detected: 0 necessary, 0 analytics, 0 marketing

Total

Necessary

Functional

Analytics

Marketing

Unknown

Filter by category

Name	Domain	Category	Provider	Expiry	Secure	HttpOnly	Party
_cq_duid	.historydb.date	Unknown	-	88 d	✓	–	1st
_cq_s	.historydb.date	Unknown	-	4 d	✓	–	1st
_cq_session	.historydb.date	Unknown	-	1.1 yr	✓	–	1st
_cq_suid	.historydb.date	Unknown	-	Session	✓	–	1st
__cmpcccx85356	.historydb.date	Unknown	-	11 d	✓	–	1st
__cmpconsentx85356	.historydb.date	Unknown	-	11 d	✓	–	1st