commit ce9b4c402d0fdc1bbcd211921fee97c116773f4e
Author: Gerd <hagezi@outlook.de>
Date:   Tue Feb 6 12:15:35 2024 +0100

    Initial Home page

diff --git a/FAQ.md b/FAQ.md
new file mode 100644
index 0000000..c3b20f1
--- /dev/null
+++ b/FAQ.md
@@ -0,0 +1,8 @@
+# FAQ
+
+## Why are CMPs (Consent Management Platform/Provider) used for cookie consent solutions not blocked in the lists?
+
+Network-wide blocking of CMPs (Consent Management Plattform/Provider) used for cookie consent solutions breaks a lot of things and takes away the user's freedom to decide what he wants to allow and what not - blocking usually allows everything ([#1979](https://github.com/hagezi/dns-blocklists/issues/1979#issuecomment-1870498567)).
+
+Blocking is reserved for content blockers with corresponding filter lists. These can be used to decide which sites are excluded from blocking CMP domains and which are not. You only have to look at the exclusions in the known cookie filter lists to see why network wide blocking via DNS is not a good idea.
+