Domain Verification
Domain verification establishes your organization's authority over a domain (e.g., acme.com). Once verified, you can automatically add users with matching email domains and restrict access to verified domains only.
Domain verification is available on Business and Enterprise plans. You can upgrade from your billing settings or see options at https://agenta.ai/pricing.
Why Verify Domains?
Domain verification enables:
- Auto-join: Users with
@yourcompany.comemails can be automatically added to your organization - Domain restrictions: Only allow users from verified domains to access your organization
- SSO discovery: Automatically show SSO options for verified domain emails
How It Works
Domain verification uses DNS TXT records to prove you control a domain:
- You add a domain in Agenta
- Agenta generates a unique verification token
- You add a DNS TXT record with the token
- Agenta verifies the DNS record
- Domain is verified
Verification Steps
Step 1: Add Domain
- Navigate to Settings → Access & Security → Domains
- Click "Add Domain"
- Enter your domain (e.g.,
acme.com) - Click "Create"
Step 2: Get Verification Token
After adding the domain, you'll see:
Domain: acme.com
Status: Pending
DNS Record to Add:
_agenta-verification.acme.com TXT "agenta-verification=J8f2KmP9nQ4vR7sT"
Copy the full DNS record value.
Step 3: Add DNS TXT Record
Add the TXT record in your DNS provider:
Cloudflare
- Go to DNS → Records
- Click Add record
- Type:
TXT - Name:
_agenta-verification - Content:
agenta-verification=J8f2KmP9nQ4vR7sT - Click Save
AWS Route 53
- Go to Route 53 → Hosted zones
- Select your domain
- Click Create record
- Record name:
_agenta-verification - Record type:
TXT - Value:
"agenta-verification=J8f2KmP9nQ4vR7sT" - Click Create records
Google Domains / Squarespace
- Go to DNS → Custom records
- Host name:
_agenta-verification - Type:
TXT - Data:
agenta-verification=J8f2KmP9nQ4vR7sT - Click Save
Namecheap
- Go to Advanced DNS
- Add New Record
- Type:
TXT Record - Host:
_agenta-verification - Value:
agenta-verification=J8f2KmP9nQ4vR7sT - Click Save
Step 4: Verify Domain
- Wait for DNS propagation (usually 5-60 minutes)
- Return to Settings → Domains
- Click "Verify" on your domain
- If successful, status changes to "Verified" ✓
Using Verified Domains
Auto-Join
Enable auto-join to automatically add users with verified domain emails:
- Navigate to Settings → Access & Security
- Enable "Auto-join for verified domains"
- Save changes
How it works:
- User signs up with
[email protected] - Agenta sees
acme.comis verified for your organization - User is automatically added as a member
- No invitation needed
Domain-Only Access
Restrict organization access to verified domains only:
- Navigate to Settings → Access & Security
- Enable "Restrict to verified domains"
- Save changes
How it works:
- Only users with verified domain emails can access
- Users with other domains (e.g.,
@gmail.com) are denied - Even invited users must have a verified domain email
Enabling domain-only access may block existing members who don't have verified domain emails. Review your member list before enabling.
Multiple Domains
Organizations can verify multiple domains:
Verified Domains:
- acme.com
- acme.co.uk
- subsidiary.com
Use cases:
- Company with multiple TLDs
- Acquired subsidiaries
- Regional domains
Each domain:
- Has its own verification token
- Must be verified independently
- Enables auto-join for that domain
Domain Authority
One Domain, One Organization
A domain can only be verified by one organization globally.
Example:
- ACME Corp verifies
acme.com→ Success - Another organization tries to verify
acme.com→ Error: "Domain already verified"
This prevents conflicts and ensures clear domain ownership.
What Verification Grants
✓ Right to enable auto-join for the domain ✓ Right to enable domain-only restrictions ✓ Organizational authority over the domain
✗ Does NOT grant authentication (user accounts still prove identity) ✗ Does NOT automatically migrate existing users ✗ Does NOT affect other organizations
Troubleshooting
Verification Fails: "DNS record not found"
Common causes:
-
DNS not propagated yet
- Wait 5-60 minutes (can take up to 48 hours)
- Check propagation:
nslookup -type=TXT _agenta-verification.yourdomain.com
-
Wrong record name
- Should be:
_agenta-verification.yourdomain.com - NOT:
_agenta-verification(missing domain) - NOT:
agenta-verification(missing underscore)
- Should be:
-
Wrong record type
- Must be
TXTrecord - NOT
AorCNAME
- Must be
-
Wrong token value
- Copy exact token from Agenta
- Include quotes if required by DNS provider
"Domain already verified by another organization"
Cause: Another organization has already verified this domain
Solutions:
- Contact the other organization to release the domain
- If you're the rightful owner, contact support with proof of ownership
Token Expired
Solution:
- Go to Settings → Domains
- Click "Refresh Token" on your domain
- Update DNS record with new token
- Click "Verify" again
Best Practices
Security
- Verify all company domains - Prevent unauthorized claims
- Monitor DNS changes - Alert on unexpected modifications
- Use DNSSEC - Add DNS security if available
- Limit DNS access - Restrict who can modify DNS records
Administration
- Verify before enabling restrictions - Don't lock out existing members
- Document verified domains - Keep track of what's verified
- Plan for acquisitions - Verify subsidiary domains promptly
- Regular audits - Review verified domains periodically
FAQ
How long does DNS propagation take?
Usually 5-60 minutes, but can take up to 48 hours depending on TTL settings.
Can I verify subdomains?
Subdomain verification is not currently supported. Verify the parent domain instead (e.g., verify acme.com to cover all @acme.com emails). This will be available soon.
What if I delete a verified domain?
- Domain becomes unverified immediately
- Auto-join stops working for that domain
- Domain-only restrictions may block users
Do I need domain verification for SSO?
No, domain verification is optional for SSO. However, it enables:
- Automatic SSO discovery for verified domain users
- Domain-restricted access policies
Can I verify domains I don't own?
No, verification requires adding a DNS TXT record, which requires DNS access. You must own or control the domain.