First, prove control of the exact domain

The signed-in customer adds one domain and receives a short-lived challenge. They place it in DNS as a TXT record or serve it at a specified HTTPS path. A separate worker verifies the proof before monitors are created. This proves technical control at that time, not legal ownership of a company or permission to change another provider’s settings.

  • Add the domain in your workspace.
  • Choose DNS TXT or HTTPS file verification.
  • Place the challenge and wait for the verification result.

Then, scheduled checks observe public signals

The current monitor set covers HTTPS availability, the public TLS certificate, HTTP security headers, selected DNS records, and public email security posture. Checks are scheduled rather than a promise that every second is observed. Guardian does not install software on your website, read page bodies, inspect private mailboxes, or test arbitrary application flows.

A change is evaluated before it becomes an incident

Different signals require different confirmation rules. A planned DNS migration can look unusual without being hostile; a single failed HTTPS request may be transient. Guardian keeps observations and shows an issue when the applicable rule has enough evidence. A customer can review an authorized change while preserving the earlier evidence. An unresolved problem is not labelled healthy merely because the dashboard is open.

Recovery must be observed too

A response task helps the responsible person investigate or apply a fix at the relevant provider. Guardian can recheck the public signal and retain the recovery observation. Completing a task by hand does not rewrite the original observation. If monitoring is delayed or verification lapses, the workspace should show that limit instead of guessing that the domain is safe.

  • Review the evidence and affected signal.
  • Fix the configuration with the provider or your team.
  • Check for a later public observation that confirms recovery.

What this service does not guarantee

Public monitoring cannot prove that every page, customer transaction, device, employee account, or private network is secure. It cannot prevent every outage or attack. Guardian is useful when you need a clear record of supported external signals and a response path; deeper application and internal security require additional controls.