Static analysis only — dynamically loaded trackers may not be reflected
Limited scan: This analysis is based on initial page load (static HTML). Trackers loaded via JavaScript — which is how most modern tracking works — are not captured. Actual tracker count may be higher.
- This scan analyzes initial page load (static HTML) — trackers loaded via JavaScript are not captured
- 0 third-party trackers detected (global average: 1.4)
This analysis is based on static HTML only and does not execute JavaScript. liliome.com likely loads additional trackers dynamically that are not captured in this scan. A browser-based scan would provide a more complete picture.
liliome.com has been scanned 2 times between January 8, 2026 and February 7, 2026. It currently has a privacy score of 76 out of 100 and loads 0 detected third-party trackers. By privacy score, liliome.com ranks 34,070 out of 49,838 domains in the dataset. This report covers liliome.com's tracker usage, cookie behavior, privacy history, and how it compares to other sites.
How Many Trackers Does liliome.com Use?
0 third-party trackers were detected on liliome.com. No third-party trackers were found in the static HTML. However, this scan does not execute JavaScript — trackers loaded dynamically (common on modern sites) may not be reflected in these results.
liliome.com Cookie Analysis
liliome.com sets 0 cookies.
liliome.com Compared to Other Sites
liliome.com has a privacy score of 76 out of 100.
liliome.com Privacy History
liliome.com has been scanned 2 times. Its stability classification is PROVISIONAL, based on observed configuration changes across scans.
What liliome.com's Privacy Profile Means
liliome.com has a privacy score of 76 out of 100. The global average across 49,838 domains is 80.8. For details on scoring methodology, see our methodology page.
About This Report
This report is part of GeckoAdvisor's dataset covering 49,838 domains with 15,563,962 findings. GeckoAdvisor scans domains to detect third-party trackers, cookies, and privacy-relevant configuration changes. For details on scanning methodology and known limitations, see our methodology page.