Skip to main content

Domain Verification

Before launching a scan, VAAST requires proof that you own or are authorized to test the target endpoint. Domain verification prevents unauthorized scanning and establishes a legal authorization trail.

Why Verification Exists​

VAAST fires adversarial payloads designed to exploit prompt injection, tool-call hijacking, RAG poisoning, and other LLM attack surfaces. To ensure these tests are only run against systems you control or have explicit authorization to test, VAAST enforces domain ownership verification at the application layer.

Without verification, no scans can be launched. The enforcement gate runs server-side — you cannot bypass it by modifying the client.


Verification Methods​

VAAST supports three verification methods. Choose the one that fits your infrastructure and access level.

DNS TXT Record​

Add a TXT record to your domain containing the challenge token. This is the most common method for domain-level verification.

Example:

Type: TXT
Name: @ (or yourdomain.com)
Value: vaast-verify=a1b2c3d4-e5f6-7890-abcd-ef1234567890

Propagation time:

  • Cloudflare: Typically instant
  • Other providers: Up to 48 hours (check with dig TXT yourdomain.com)

Best for: Production domains where you control DNS.


Well-Known File​

Host a plain-text file at /.well-known/vaast-verify.txt containing only the challenge token.

Example file location:

https://api.acme.com/.well-known/vaast-verify.txt

File contents:

vaast-verify=a1b2c3d4-e5f6-7890-abcd-ef1234567890

For static hosts (Vercel, Netlify): Add the file to /public/.well-known/ in your project repo.

Requirements:

  • Must return HTTP 200
  • No redirects
  • Body contains the exact token string

Best for: Apps deployed on static hosting or platforms where DNS control is restricted.


API Key​

For endpoints where you can supply a valid API key proving access, VAAST accepts the key as proof of authorization.

Example: If you're testing your company's internal API that requires a Bearer token, providing that token serves as verification.

Note: This method does NOT perform live validation of the API key — it's accepted on trust. Only use this for endpoints you genuinely control.

Best for: Internal or partner APIs where you have credentials but not DNS access.


Verification Lifecycle​

Challenge Tokens​

When you register a target in VAAST, the backend issues a challenge token:

vaast-verify={uuid}

Challenge tokens expire in 48 hours. If you don't complete verification within that window, you'll need to initiate a new challenge by registering the target again.

Verified Status​

Once verification succeeds, your target's status is set to verified and remains valid indefinitely. However:

  • VAAST re-checks authorization every 30 days by querying the same DNS TXT record or well-known file you originally created.
  • If the re-check fails (TXT record removed, file deleted, endpoint unreachable), status moves to failed and you'll receive an email.
  • Scans are blocked until you re-verify.

Re-Verification Emails​

You'll receive email notifications for:

  1. Domain verified: Confirmation when verification succeeds
  2. Verification lost: Action required when the 30-day re-check fails

Keep your verification record in place to avoid interruptions.


Blocklisted Domains​

VAAST tests LLM-integrated applications, not the underlying model provider APIs directly. The following provider base domains are blocklisted and cannot be registered as targets:

  • api.openai.com (OpenAI / ChatGPT)
  • api.anthropic.com (Anthropic / Claude)
  • generativelanguage.googleapis.com (Google / Gemini)
  • x.ai, api.x.ai (xAI / Grok)
  • huggingface.co, api-inference.huggingface.co (Hugging Face)
  • api.mistral.ai (Mistral)
  • api.cohere.com (Cohere)
  • api.together.xyz (Together AI)
  • api.groq.com (Groq)
  • openrouter.ai (OpenRouter)

Why? These are the inference engines, not the applications built on top of them. To test your app, deploy it to a domain you control and verify that domain.


Localhost Exception​

Endpoints on localhost, 127.0.0.1, or ::1 are automatically verified without requiring DNS or well-known file setup.

Use cases:

  • Testing against local Ollama installations
  • Development builds of your application
  • Local inference servers (vLLM, text-generation-inference, etc.)

Localhost targets are immediately marked as verified and skip the 30-day re-check cycle.


Edge Cases​

Subdomains​

Each subdomain requires independent verification:

  • api.example.com ✅
  • chat.example.com ✅

These are treated as separate domains — verifying one does not grant access to the other.

Multiple Users​

Multiple users can independently verify the same domain. VAAST enforces per-user authorization, not global uniqueness.

Deleted Targets​

Deleting a target soft-deletes it (status → revoked, deleted_at set). The same domain can be re-registered by initiating a new challenge.


API Flow​

The domain verification system exposes the following endpoints at https://api.xtrinel.com/v1:

Register a Target​

POST /v1/targets
Authorization: Bearer {id_token}
Content-Type: application/json

{
"endpoint": "https://api.acme.com/v1/chat",
"method": "dns_txt"
}

Response:

{
"id": "550e8400-e29b-41d4-a716-446655440000",
"domain": "api.acme.com",
"method": "dns_txt",
"status": "pending",
"challenge_token": "vaast-verify=a1b2c3d4-...",
"instructions": "Add a TXT record to api.acme.com with value: vaast-verify=..."
}

Verify a Target​

After adding the DNS record or hosting the well-known file:

POST /v1/targets/{id}/verify
Authorization: Bearer {id_token}

Response (success):

{
"id": "550e8400-e29b-41d4-a716-446655440000",
"domain": "api.acme.com",
"status": "verified",
"verified_at": "2024-04-24T19:45:00Z",
"message": "DNS TXT record verified for api.acme.com"
}

Response (failure - HTTP 422):

{
"detail": "DNS TXT record not found. Add a TXT record with value: vaast-verify=..."
}

Check Target Status​

Before launching a scan, check if the target is scannable:

GET /v1/targets/{id}/status
Authorization: Bearer {id_token}

Response:

{
"scannable": true,
"status": "verified",
"domain": "api.acme.com"
}

If scannable is false, scans are blocked.


List Targets​

GET /v1/targets
Authorization: Bearer {id_token}

Response:

[
{
"id": "550e8400-e29b-41d4-a716-446655440000",
"endpoint": "https://api.acme.com/v1/chat",
"domain": "api.acme.com",
"method": "dns_txt",
"status": "verified",
"verified_at": "2024-04-24T19:45:00Z",
"last_checked_at": "2024-04-24T19:45:00Z",
"created_at": "2024-04-24T19:40:00Z"
}
]

Delete a Target​

DELETE /v1/targets/{id}
Authorization: Bearer {id_token}

Response: HTTP 204 (no content)


Next Steps​

After verifying a domain:

  1. Open VAAST desktop app
  2. Navigate to the Targets screen
  3. Confirm your target shows status = verified
  4. Select the target in the Scan screen dropdown
  5. Launch your scan

For more on running scans, see the Scanner documentation.