Content Security Policy (CSP) errors
Your site sends a Content Security Policy, and the browser console reports that it blocked something from SilentShield. This page lists the directives the widget needs and explains each message.
Directives the widget needs
Add these directives to your policy. List every host, even if your key uses only one: the widget falls back to another host if the first one fails, and switching endpoints later would otherwise lock you out.
script-src 'self' https://api-us.silentshield.io https://api-eu.silentshield.io https://api.silentshield.io;
connect-src 'self' https://api-us.silentshield.io https://api-eu.silentshield.io https://api.silentshield.io;
worker-src 'self' blob:;Messages in the console
client.js does not load (script-src)
Console: “Refused to load the script …/client.js”. script-src does not allow the SilentShield hosts, so the widget does not load at all. Add the hosts to script-src as shown above.
Measurements are not sent (connect-src)
Console: “Refused to connect to …”. The widget loads but cannot send its measurements or ask for a verdict, so the check on your server finds no behaviour data for the submission. Add the hosts to connect-src.
The worker does not start (worker-src)
Console: “Refused to create a worker from 'blob:…'”. The widget runs its invisible computation in a worker started from a blob: URL. Without it this step fails, and visitors may be shown a visible task instead. Add worker-src 'self' blob:.
Badge or task without styling (style-src)
Console: “Refused to apply inline style …”. The widget adds its own style elements for the badge and the task; a style-src without 'unsafe-inline' blocks them, and both appear unstyled. Allow 'unsafe-inline' in style-src. This applies to styles only, not to scripts.
The message remains after the change
A page can receive several policies: from the web server, from a meta tag, from a plugin or from a CDN. The browser applies all of them. In the Network tab of the developer tools, open the request for the page itself and check every Content-Security-Policy header. A Content-Security-Policy-Report-Only header only reports and blocks nothing.
If the widget still does not appear, continue with the checklist: Widget Not Loading