Frequently Asked Questions
Everything you need to know about website monitoring, security checks, alerts, plans and your data.
Getting started
What is Viglar?
Who is Viglar for?
How do I add a website?
Why do I need to verify domain ownership?
How often does Viglar scan my website?
Can I pause monitoring?
Monitoring & security
What does Viglar monitor?
What does the DNS check include?
What are SPF, DKIM and DMARC?
What does SSL monitoring check?
What are security headers?
What does port monitoring do?
What is IP reputation monitoring?
How does content monitoring work?
Does Viglar scan my website for malware?
What are DMARC Reports, and how do they help me?
Why is my Viglar badge not displaying?
If your Viglar badge does not appear, your website's Content Security Policy (CSP) may be blocking images loaded from https://viglar.com.
Apache: If you configure CSP in Apache, find your existing Header always set Content-Security-Policy directive and add https://viglar.com to its img-src directive.
For example, a minimal policy could look like this:
Header always set Content-Security-Policy "default-src 'self'; img-src 'self' data: https://viglar.com; object-src 'none';"
This is only an example, not a complete replacement for your existing security policy. Keep your other CSP directives and existing image sources, and add https://viglar.com to the existing img-src directive.
If CSP is configured elsewhere, such as in a hosting control panel, CDN, or application, update it there instead. Avoid adding a second CSP header: multiple policies are enforced together and may still block the badge.
If the badge still does not display, check your browser's developer console for CSP errors.