From domain control to explainable comparisons
1. Establish control with a TXT record
Publish the exact record shown in the dashboard for that domain. This demonstrates technical control at that time; the scope requires your authorization. It does not automatically authorize subdomains or discovered names. Keep the record published for subsequent checks.
2. Observe permitted sources
Query published email DNS policies and bounded lookalike candidates as configured. If a fresh control check fails or becomes unknown, runs are paused and the last known evidence retains its timestamp.
3. Compare compatible evidence
The first observation establishes a baseline without change alerts. Later observations compare only fields with compatible scope and coverage. An error, truncated window or partial response does not establish that an asset disappeared.
Current service configuration
An enabled capability describes service configuration; it grants no account access and does not guarantee a source will respond. The dashboard checks project access, domain control, validity and budgets before each run.
Domain control through TXT
Checking…Email policies published in DNS
Checking…Bounded local lookalike generation
Checking…DNS observations for lookalike candidates
Checking…Manual runs
Checking…Scheduled runs
Checking…Compatible observation comparisons
Checking…ViciousByte evidence signature
Checking…Signed webhooks
Checking…Certificate Transparency observations
Provider authorization pending
What each observation means
DNS and email: reports describe SPF, DMARC and the DKIM selectors queried. A key absent from that set does not establish that the domain lacks DKIM; no email is sent and impersonation is not tested.
Lookalikes: a similar name that resolves is a candidate for review, not confirmed impersonation. Local generation and permitted DNS queries do not visit, capture or scan those sites.
Coverage: every source retains its timestamp, state and limits. No web crawling, port scanning or probing of the site or mail server takes place. An empty result does not establish absence of exposure.
A ViciousByte evidence signature, when configured, attests to the application report. It does not certify the provider, legal domain ownership or domain security.
Scope, scheduling and budgets
The dashboard shows applicable balance and usage before operation. Started attempts may consume credits even if a provider fails or cancellation is requested; requested cancellation remains pending until confirmed.
The published limits could not be confirmed. Review dashboard configuration; no available quotas, schedules or retention are assumed.
Privacy and retention
Projects belong to one account. Normalized observations and private comparisons are retained; website bodies and email inboxes are not archived. Queried public records may include published names and contacts.
DNS queries send queried names to the configured external resolver. That provider applies its own logging and data policies; absence of external logs is not promised. Review resolver privacy
Expiry or deletion blocks access and queues purging of observations, evidence and associated payloads. Physical purging is asynchronous; minimal quota and idempotency receipts follow separate retention.
Current investigation plans may apply when confirmed by the server. Effective access is checked per project. A pilot request records interest pending review; it activates no permissions and starts no automatic charge.
Request pilot access
Register a Digital surface monitoring request for your account. This does not create a subscription, activate permissions or execute a payment.