HostingChecker
Legal

Cookie policy

Last updated: 15 May 2026

Overview

We take a conservative approach to client-side storage. The lookup tool itself sets no tracking cookies. The only client-side item we always set is a single strictly-necessary local-storage flag that remembers your consent choice. Optional analytics are only loaded after you click Accept on the consent banner.

Strictly necessary: the consent flag

We use one local-storage item named cookie-consent, with the value accepted or rejected, to remember whether you have responded to the cookie banner. This is technically not a cookie — it is a value stored in your browser's localStorage — and under the ePrivacy Directive it does not require consent because it is strictly necessary to provide the service you have requested (remembering your consent decision).

Before you click "Accept"

We do not set any cookies until you click Accept on the consent banner. No third-party scripts are loaded prior to consent.

After you click "Accept"

Once you accept, we may load Google Tag Manager and Google Analytics 4 for aggregated usage statistics. IP anonymization is enabled. These services are measurement-only — they are not used for advertising or retargeting on this site.

Name Provider Purpose Duration Type
cookie-consent HostingChecker Remembers your consent choice (localStorage, not a cookie). Persistent (until cleared) Strictly necessary
_ga Google Distinguishes users. 2 years Analytics
_ga_* Google Maintains session state. 2 years Analytics

Google's handling of this data is governed by the Google Privacy Policy.

How to revoke consent

To revoke consent at any time, clear your browser's site data for this domain. The cookie banner will reappear on your next visit, and you can click Reject. Rejecting will prevent any analytics cookies from being set on subsequent visits.

A note on the lookup tool

Running a lookup does not set any cookies of its own. The only items the lookup flow may touch in your browser are the cookie-consent flag described above and, if you sign in (a planned future feature), a standard Symfony session cookie used solely to keep you logged in.