Changelog

You can now schedule maintenance windows for your monitored domains in Viglar.

Plan upcoming maintenance, upgrades or other planned downtime in advance. Viglar suppresses notifications covered by maintenance-window handling during the scheduled period, while monitoring and event recording continue.

When the window ends, normal notification handling resumes, helping you distinguish planned maintenance from unexpected website issues.

Viglar can now collect and process DMARC aggregate reports, giving you a clearer picture of how email is sent on behalf of your domain.

See reporting sources and email authentication results in one place to better understand which senders are using your domain and how they pass DMARC checks.

Combined with Viglar's SPF, DKIM and DMARC configuration tools, DMARC Reports help you move from publishing authentication records to understanding how they work in practice.

Viglar is moving from open beta to a full public release.

Over the past weeks, the platform has grown from website monitoring into a broader set of tools for website security, email authentication and client reporting. Recent additions include Viglar Events, DMARC Reports and Client Security Reports with PDF export and public sharing.

This is an important milestone, but development continues. We'll keep improving existing features and building new tools to make website monitoring and security easier to manage.

You can now create Client Security Reports in Viglar and share them through a public link or as a PDF.

Each report brings together a domain's current security score, uptime statistics for the selected period, latest scan results and event history - including unresolved problems, detected changes and recoveries.

It gives you a clear overview of a website's security and a practical way to share findings with clients without walking them through the monitoring dashboard.

Viglar Events is here.

We've built a unified timeline for monitoring events and incidents, so you can see what happened to a domain, what changed, and when it recovered - all in one place.

Problems, detected changes and recoveries are linked together, making it easier to follow an incident from the first warning to resolution. The timeline also keeps useful details, such as previous and new DNS record values, without filling the history with duplicate events.

We also redesigned the client interface to make monitoring results clearer, more informative and easier to work with.

The goal is simple: when something happens to a website, you shouldn't have to piece the story together yourself.

Added a free SPF, DKIM and DMARC generator to Viglar.

Enter your domain, generate the records, check the result, and save the configuration if you want to keep it. Saved configurations include history, so you can see what changed over time.

The generator is also connected to the Viglar Knowledge Base and monitoring, so you can go from generating the records to learning more or monitoring the domain.

It works without a Viglar account - no registration required.

The idea is simple: fixing email authentication should not require digging through five different DNS guides.

Viglar can now import domains from CSV files, with smart handling of existing domains and import results.

We also added RDAP scanning for more reliable domain registration data, including registrar and registration details where available.

Added:
- Smart CSV domain import
- RDAP domain scanning
- Better handling of existing and imported domains

Alert routing is now much more flexible. Each client folder can have its own notification destinations, with multiple destinations supported per folder.

You can now route alerts for different clients to the channels that make sense for them — including Telegram, Slack, Discord, webhooks and email.

This builds on the previous alert system and gives folders their own independent notification setup.

Improved:
- Folder-based alert routing
- Multiple destinations per folder
- Email alerts

Agencies and teams can now organize monitored domains into client folders, add notes to domains, and route alerts based on those folders.

This makes it easier to keep client domains separated and send each client's alerts to the right notification channel — for example, Telegram for one client and Slack for another.

Added:
- Domain notes
- Client folders
- Folder-based alert routing

Improved Viglar’s own email authentication setup, including SPF, DKIM, DMARC and BIMI.

BIMI is now configured using a hosted brand logo, without requiring a paid certificate.

DNS monitoring now looks at the full record set instead of simply reporting that “DNS changed”.

Viglar also tracks DKIM selectors individually and validates their public keys. Changes or invalid DKIM configurations can now be identified and reported more precisely.

Improved the public domain check and its transition into Viglar monitoring.

The result now gives visitors a clearer next step when they want to move from a quick check to continuous monitoring.

Viglar now supports self-service account deletion.

If you have an active Stripe subscription, Viglar will ask you to cancel it first. The deletion flow also includes a short exit survey to help us understand why people leave and what we could improve.

You can now pause monitoring for a domain or disable individual checks and alert types.

This makes it easier to keep a domain in Viglar without receiving alerts for checks you do not currently need.

Added lightweight, self-hosted visitor analytics without third-party tracking or advertising platforms.

Visitor identifiers are hashed, and old analytics and operational logs are automatically cleaned up according to their retention periods.

Spent a few days working on the technical SEO foundation for Viglar.

Added proper canonical URLs, language alternates, structured data, sitemap and search-engine discovery improvements. Public pages are now structured to be easier for both search engines and people to find.

Viglar now has real subscription billing through Stripe. On September 20, we opened the product to the public as an open beta.

This is the point where Viglar moved from a private development project to a publicly available service.