Before creating a proxy service, you need to prove you own the domain your API runs on. This prevents unauthorized proxying of third-party APIs.
Why verification is required#
Domain verification ensures that only you can create a proxy service pointing to your API. Without it, anyone could proxy traffic to your endpoints and charge for access.When you verify a domain, you gain authorization for:The exact domain (e.g., api.example.com)
All subdomains (e.g., v2.api.example.com)
Verification methods#
DNS TXT record (recommended)#
Best for apex domains and subdomains where you control DNS settings.1.
Go to Proxy > Domains in the Kobaru Console
2.
Click Add Domain and enter your domain
3.
Select DNS TXT as the verification method
4.
Add the following DNS record at your DNS provider:
Record Type: TXT
Hostname: _kobaru-verify.yourdomain.com
Value: kobaru-verify=abc123def456...
TTL: 3600 (or auto)
5.
Click Verify Now in the Console
You should see the kobaru-verify=... value in the response.
HTTP file verification#
Best when you don't have DNS access but can upload files to your web server.1.
Go to Proxy > Domains in the Kobaru Console
2.
Click Add Domain and enter your domain
3.
Select HTTP File as the verification method
4.
Create the verification file on your server:
5.
Make sure the file is accessible at:
https://yourdomain.com/.well-known/kobaru-verify.txt
6.
Click Verify Now in the Console
Verification token lifecycle#
Generated as a cryptographically secure random token (256 bits)
Expires 7 days after you add the domain. If the domain isn't verified by then, its status changes to Expired
Stored as a hash in the database (never in plaintext)
Renewable by adding the domain again. The Console replaces the expired entry with a new token, so you don't need to delete it first
IMPORTANT: Do NOT remove the DNS record or verification file after successful verification. We continuously monitor domain ownership, and removing the verification will cause your proxy service to go down.
Managing domains#
The domain management page at Proxy > Domains shows:| Column | Description |
|---|
| Domain | The domain name |
| Coverage | Shows the *.domain.com wildcard pattern |
| Method | DNS TXT or HTTP File |
| Status | Pending, Verified, Failed, or Expired |
| Verified at | Timestamp of successful verification |
View verification instructions for pending domains
Retry verification if the first attempt failed
Delete domains you no longer need
Common issues#
DNS verification keeps failing#
1.
Check DNS propagation: dig TXT _kobaru-verify.yourdomain.com
2.
Make sure there are no trailing dots in the hostname
3.
Wait for your DNS TTL to expire (use a lower TTL like 300 during setup)
4.
Verify the value matches exactly (some DNS providers add quotes automatically)
5.
For apex domains, some providers require @ as the hostname
HTTP file verification fails#
1.
Ensure the file is accessible: curl https://yourdomain.com/.well-known/kobaru-verify.txt
2.
Confirm HTTPS is enabled (HTTP will fail)
3.
Check there are no redirects (301/302 can cause issues)
4.
Verify file permissions (should be readable)
5.
Make sure no authentication is required for the .well-known path
Token expired#
Verification tokens expire 7 days after you add the domain. When you verify an expired domain, the Console shows "Token expired. Add this domain again to get a new token."1.
Go to Proxy > Domains and add the same domain again. The expired entry is replaced automatically.
2.
Update your DNS TXT record or verification file with the new token.
If you add a domain that is still pending and not yet expired, the Console rejects it as already registered. Verify the existing entry instead, or delete it and add it again.
Next steps#
Modified at 2026-10-21 21:01:02