Two ways to prove control
A DNS TXT challenge requires access to the domain’s DNS configuration. An HTTPS file challenge requires control of a prescribed path on the website. Guardian checks the challenge asynchronously and creates monitors only after successful verification.
- Add your exact domain after signing in.
- Choose DNS TXT or HTTPS file verification.
- Place the challenge exactly where instructed and wait for the verification result.
What the proof means
A successful challenge proves technical control at that moment. It does not prove legal ownership of the business or domain, and it does not authorize changing third-party systems. Guardian may pause monitoring if a later control check fails.
Why this matters
Verification limits monitoring to domains the customer can demonstrate control over. It also keeps the setup clear: one domain, one proof, then the relevant public checks. No software needs to be installed on the website for the basic monitoring flow.
Example: an agency managing a client site
An agency can type its client’s domain into the workspace, but monitoring does not start just because the agency knows the name. Someone with authorized DNS or website access places the challenge, and the system checks it. The proof establishes technical control of that domain; the agency and client should still agree separately on who is allowed to receive alerts, change configuration, and respond to incidents.