# DE Website Compliance Check (Impressum, Cookies, TLS) (`datenfuchs/de-website-compliance-check`) Actor

Heuristic DE website check: Impressum/Privacy link presence (bool only), cookie-banner heuristic, tracker patterns on initial load, TLS. No PII. Not legal advice.

- **URL**: https://apify.com/datenfuchs/de-website-compliance-check.md
- **Developed by:** [Datenfuchs Labs](https://apify.com/datenfuchs) (community)
- **Categories:** Developer tools, Lead generation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 domain checkeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## DE Website Compliance Check – Impressum, Privacy, Cookies (Bulk)

By **Datenfuchs Labs**.

### Deutsch

Prüft Websites **heuristisch** auf technische Compliance-Signale, die für den DACH-Raum oft relevant sind:

| Signal | Was gespeichert wird |
|---|---|
| Impressum-Link | nur `true`/`false` (Linktext/URL-Muster) |
| Datenschutz-Link | nur `true`/`false` |
| Cookie-/Consent-Banner | Heuristik (bekannte CMP-Selektoren + fixed/sticky Text) |
| Tracker vor Consent | IDs bekannter Muster (GA, Meta-Pixel, Hotjar, …) aus **initialem** HTML/Netzwerk – ohne Interaktion |
| TLS / HTTPS-Redirect | `tlsOk`, `httpsRedirect` |
| Ampel | `riskFlag`: HIGH / MEDIUM / LOW |

**Datenschutz (hart):** Es werden **keine** Impressumsinhalte, E-Mails, Telefonnummern, Namen oder Seitentexte gespeichert – nur Booleans, Domain, URL, Tracker-IDs und Notizen.

**Wichtige Hinweise (ehrlich):**

- **Keine Rechtsberatung.** Kein Abmahn-Tool. Ampel und Flags sind grobe Heuristiken, kein Gutachten und keine Rechtsprüfung.
- Fehlende Links ≠ rechtwidrig in jedem Fall; vorhandene Links ≠ rechtskonform.
- Cookie-Banner und Tracker-Erkennung sind unvollständig (Shadow-DOM, späte Lazy-Loads, serverseitiges Consent-Gating).
- Manche Sites blockieren Rechenzentrums-IPs → optional Proxy.

### English

Bulk **heuristic** check for German/DACH website compliance signals: Impressum & privacy **link presence** (booleans only), cookie-banner heuristic, known tracker patterns on **initial** load, TLS / HTTPS redirect, and a HIGH/MEDIUM/LOW risk flag.

**Privacy:** No Impressum content, emails, phones, names or page text — only flags and non-PII technical signals.

**Honest limits:** Not legal advice. Not an Abmahnung tool. Heuristics only; presence ≠ compliance.

### Input

| Field | Default | |
|---|---|---|
| `startUrls` | – | one URL per site |
| `maxConcurrency` | 3 | 1–10 |
| `waitAfterLoadMs` | 2500 | wait for late scripts/banners |
| `proxyConfiguration` | off | optional |

### Output (dataset)

One `type: "domainCheck"` record per URL with the fields above plus `notes[]` and a fixed `disclaimer`.

### Pricing

Pay-per-event (when enabled on the Actor):

- `domain-checked`: **$0.01** per domain/URL checked
- Plus Apify’s tiny `apify-actor-start` platform fee

Until monetization is active in Console, runs are free (you still pay your own platform compute if any).

### Run locally

```
npm install && npx playwright install chromium
## put input in storage/key_value_stores/default/INPUT.json
npm start
```

# Actor input Schema

## `startUrls` (type: `array`):

One URL per website (homepage). Each URL is checked once (domain-level signals).

## `maxConcurrency` (type: `integer`):

Parallel browser pages (keep low on Free plan).

## `waitAfterLoadMs` (type: `integer`):

Extra wait so late scripts/banners can appear (heuristic).

## `proxyConfiguration` (type: `object`):

Optional. Default is direct (no paid proxy). Some sites block datacenter IPs.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://example.com"
    }
  ],
  "maxConcurrency": 3,
  "waitAfterLoadMs": 2500,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `overview` (type: `string`):

Domain check records (type=domainCheck).

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "startUrls": [
        {
            "url": "https://example.com"
        }
    ],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("datenfuchs/de-website-compliance-check").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "startUrls": [{ "url": "https://example.com" }],
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("datenfuchs/de-website-compliance-check").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "startUrls": [
    {
      "url": "https://example.com"
    }
  ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call datenfuchs/de-website-compliance-check --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,datenfuchs/de-website-compliance-check"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/bEj2aXEWvf8H3UKa5/builds/iIGQb2rFzVlc4e2J0/openapi.json