Cookie Policy

Cookie Policy

This Cookie Policy explains how CheckDomainHealth may use cookies, local storage and similar technologies.

Last updated: 27 August 2026 · Version 2.1 · Effective from 23 August 2026 (Law no. 195/2024)

Site operation

Some technologies are needed for security, abuse prevention and basic site functionality.

Preferences

CheckDomainHealth may remember settings such as light or dark theme in your browser.

Optional analytics

Analytics cookies are used if enabled and, where required, after consent. In some regions they may run by default, with Cookie Preferences still available.

Your choices

You can manage cookies in your browser and through cookie preferences when offered.

1. What cookies are

Cookies are small text files stored on your device by a website. They can help a site remember settings, support security, understand site usage or enable certain features.

2. How CheckDomainHealth uses cookies

CheckDomainHealth may use cookies, local storage or similar technologies to operate the website, protect against abuse, remember preferences and understand how the site is used.

The exact cookies used may depend on which features, analytics tools or integrations are enabled.

3. Strictly necessary cookies

Some cookies or storage technologies are required for the website to work correctly, maintain security, prevent abuse, remember basic preferences or process form interactions.

These are generally required for the service and cannot always be disabled through the website.

4. Analytics and performance cookies

When a Google Analytics 4 Measurement ID is configured, CheckDomainHealth may load Google Analytics 4 for usage measurement. First-party analytics (pageviews / events) uses the same Analytics category.

Whether the cookie banner is shown depends on your approximate location. In the EU/EEA, United Kingdom, Switzerland, Moldova and Brazil, analytics stays off until you accept. In other regions, analytics may run by default. If we cannot determine your location, we treat the visit as requiring consent and show the banner.

Reject optional or withdrawing consent stops further events and clears first-party analytics identifiers (cdh_aid, cdh_visitor_id, cdh_sid) where technically possible. You can change this later from Cookie Preferences.

The following items are used by CheckDomainHealth based on the current codebase. Exact Google Analytics cookie names and durations depend on Google’s implementation when measurement is enabled.

Name	Type	Provider	Category	Purpose	Duration	Party	Legal basis	Default
`cdh_cookie_consent_v1`	localStorage	CheckDomainHealth	Necessary	Store cookie choices (necessary / analytics / marketing), timestamp, and whether the choice was made by you or applied as a location-based default	Until cleared	First-party	Legitimate interest / legal obligation to record consent	Set when you save preferences or when a location-based default is applied
`cdh_analytics`	cookie	CheckDomainHealth	Analytics signal	Signals analytics consent to first-party analytics API (`cdh_analytics=1`)	Up to 1 year	First-party	Consent	Off until you accept, or until a location-based default is applied
`cdh_aid`	cookie	CheckDomainHealth	Analytics	Anonymous visitor ID for first-party analytics	Up to 1 year	First-party	Consent	Off until consent; deleted on Reject / withdrawal
`cdh_sid`	cookie	CheckDomainHealth	Analytics	Short analytics session identifier	~30 minutes	First-party	Consent	Off until consent
`cdh_visitor_id`	localStorage	CheckDomainHealth	Analytics	Mirror of visitor ID for client-side analytics	Until cleared	First-party	Consent	Off until consent; deleted on Reject / withdrawal
`cdh-theme`	localStorage	CheckDomainHealth	Necessary	Light / dark theme preference	Until cleared	First-party	Legitimate interest (UI preference)	On when you change theme
Session cookie (`cdh.sid`)	cookie	CheckDomainHealth	Necessary	Authenticated dashboard session	Up to 30 days (application default)	First-party	Contract (account)	On login
`_ga`, `_ga_*`, `_gid`	cookie	Google Analytics 4	Analytics	Measurement when GA Measurement ID is configured	Per Google defaults (often up to 2 years / 24 hours)	Third-party / set by gtag	Consent	Off until you accept or a location-based default applies; loaded only when a Measurement ID is configured

International transfers for Google Analytics may involve processing outside Moldova / the EEA when measurement is enabled.

5. Marketing and tracking cookies

CheckDomainHealth does not currently use advertising, remarketing or tracking cookies unless they are intentionally added in the future.

If marketing or tracking cookies are added later, they will be disclosed here and controlled through cookie preferences where required.

6. Local storage and similar technologies

The website may use local storage or similar browser technologies to remember preferences, improve user experience or support technical functionality.

For example, your theme preference (light or dark mode) may be stored in local storage so the setting persists between visits.

7. Managing cookie preferences

You can control cookies through your browser settings. Cookie Preferences in the footer lets you accept, reject or change optional analytics regardless of whether the banner was shown for your location.

8. Changes to this Cookie Policy

We may update this Cookie Policy from time to time. When changes are made, the “Last updated” date on this page will be updated.

9. Contact us

For questions about cookies or privacy, contact us through the Contact page.