Managed service providers
Monitor client domains for TLS, email-authentication, DNSSEC and web-security drift without revisiting separate tools manually.
DomainGuard Monitor · Buyer and workflow guide
From one-time checks to continuous client awareness.
DomainGuard Monitor is built for organizations that manage more domains than they want to check manually. It saves a baseline, rescans automatically, records history, detects meaningful drift, and can push change events into existing workflows.
Best-fit customer
The strongest buyer manages a portfolio, not one website.
The product becomes valuable when a technician, consultant or software platform would otherwise repeat the same public configuration checks across dozens or hundreds of domains.
Security consultants
Keep an external configuration baseline between assessments and generate a portfolio report before a client review.
Website agencies
Baseline domains after launches or migrations and notice when a later infrastructure change removes a security control.
SaaS teams
Use the API to evaluate customer or custom domains during onboarding and keep watching them after the initial connection.
Multi-brand organizations
Track product, campaign and legacy domains from one workspace rather than relying on tribal knowledge or spreadsheets.
Automation platforms
Receive signed HTTPS webhook events when monitored configuration changes and route those events into a ticketing or orchestration workflow.
Example MSP workflow
Add the client once. Work the exception.
An MSP does not need a technician to re-check every domain every morning. Monitor is designed to stay quiet when the baseline is stable and produce an event when something materially changes.
- Enroll the client's public domain
- Establish the initial posture baseline
- Rescan according to the plan schedule
- Detect failures, recoveries and configuration drift
- Send a webhook into the MSP's workflow
- Include the domain in a white-label client report
Client added
↓
Baseline: 91 / A
↓
Automatic rescans
↓
DMARC policy disappears
↓
Posture: 76 / C
↓
HIGH change event
↓
Webhook / ticket / reportWhat counts as drift
Alert on changes that can alter the operational picture.
The change engine compares each new scan with the previous full result. Stable failures do not create a new event every cycle; alerts are intended to represent a new state transition or a meaningful threshold.
Control failure
A previously passing control—such as DMARC, TLS, HSTS or DNSSEC—fails.
Control recovery
A previously failing control returns to a passing state.
Configuration change
SPF, DMARC, MX, DNSSEC, MTA-STS or TLS-reporting details change even if the pass/fail state does not.
Certificate threshold
A certificate crosses monitored lifetime thresholds such as 30, 14, 7, 3 or 1 day remaining.
Posture deterioration
A meaningful score change is recorded when no more-specific control transition explains it.
Repeated scan failure
Monitor records scan errors and escalates repeated failures instead of silently treating missing data as healthy.
MSP reporting
The same data can become a client-facing deliverable.
MSP and Scale workspaces include account-level report branding; every workspace includes portfolio scoring, common failed-control summaries, domain-level findings, recent events and CSV export. The dashboard can open a printable report that an MSP can save as PDF or use as the basis for a client review.
The report is an automated external posture summary, not a penetration test, compliance attestation, or certification.
API and integration
Built to fit into other software.
Customer workspaces use a dedicated Monitor API key. The API supports domain enrollment, status/history, events, reports, CSV export, branding and signed HTTPS webhooks. Webhook receivers can verify HMAC-SHA256 signatures using a per-account verification secret. One-time invitation links can claim a workspace without sending a raw API key through email or chat.
Domain portfolios