Check extension health
Diagnostics can help confirm whether protection is active, rulesets are loaded, dynamic rules exist, remote update counts are available and advanced modules are enabled.
Support report export
Shieldly can export a local support report for troubleshooting. The report is intended to help diagnose extension state and does not include a license key.
Local troubleshooting
Diagnostics are built to support users without requiring browsing history uploads. Extension version, active rules, WebRTC policy state, current site mode and filter state can be reviewed locally.
Run a check with a specific question
Open Diagnostics when you need to understand rule activity, privacy state or extension health. Decide what you are investigating before collecting a report: an unavailable module, a broken page or an unexpected setting. Record the browser and Shieldly versions and run the check in the profile where the problem occurs. A healthy overall result does not prove that every individual website is compatible.
Write steps another person can repeat
Describe the page, the action and what happened instead of the expected result. For example, explain that starting a player after a consent choice leaves an empty area, rather than saying only that video is broken. Note the protection mode and whether a site-specific compatibility change helped. Make one change at a time so the report can connect the result to a specific setting.
Review a report before sharing it
The export is intended for local troubleshooting, and choosing to share it is a separate action. Read the generated text for domain names, account information or other details you do not want to disclose. Remove sensitive information from accompanying URLs and screenshots as well. Keep enough nonprivate context to reproduce the problem. Never attach a license key, session cookie or password simply because it appears near a diagnostic control.
Frequently asked questions
Does exporting automatically open a support ticket?
The local export workflow is not itself a submitted ticket. Use the support contact path separately when you decide to share a reviewed report.
Why is some request information missing?
Available browser request history can be incomplete. An absent entry is not proof that a request never happened or that a module is inactive.
Related pages
Read support, data deletion and permissions explained.