Domain Verification
Secure your analytics with domain verification
🔒 Domain Verification
Domain verification ensures that only authorized domains can send analytics data to your Databuddy project. This prevents unauthorized usage and protects your analytics data from spam or malicious traffic.
Required First Step: You must verify your domain before you can create projects and track analytics data.
🛡️ Why Domain Verification?
Security Benefits
- Prevent Unauthorized Usage - Only verified domains can send data
- Protect Against Spam - Block fake traffic from unverified sources
- Data Integrity - Ensure analytics come from legitimate sources
- Cost Control - Prevent unexpected usage charges
How It Works
- Add a domain to your Databuddy project
- Databuddy generates a unique verification token
- Add a DNS TXT record with the token
- Databuddy verifies the DNS record
- Domain is authorized for analytics tracking
🚀 Domain Verification Process
Access Domain Management
- Go to your Databuddy Dashboard
- Navigate to Settings → Domains
- Click Add Domain
If you don't have an account yet, sign up for free first.
Enter Your Domain
Enter your domain name without the protocol or paths:
✅ Correct examples:
example.com
www.example.com
app.example.com
blog.example.com
subdomain.example.com❌ Avoid these formats:
https://example.com (don't include protocol)
http://example.com (don't include protocol)
example.com/path (don't include paths)
example.com:8080 (don't include ports)
www.example.com/ (don't include trailing slash)Get DNS Instructions
After adding your domain, you'll receive:
- DNS Record Name:
_databuddy.yourdomain.com - DNS Record Value:
databuddy_abc123...(unique verification token) - TTL: 300 seconds (recommended)
Important: Keep this token secure and don't share it publicly. Generate a new one if it's compromised.
Configure DNS Record
Add a TXT record to your domain's DNS settings:
Type: TXT
Name: _databuddy
Value: databuddy_abc123def456... (your unique token)
TTL: 300For the root domain example.com:
_databuddy.example.com TXT "databuddy_abc123def456..."For subdomain app.example.com:
_databuddy.app.example.com TXT "databuddy_abc123def456..."Verify Your Domain
- Wait for DNS propagation (15-30 minutes typical)
- Return to your Databuddy dashboard
- Click "Verify" next to your domain
- Check status - should change from "Pending" to "Verified"
Once verified, you can create projects and start tracking analytics for this domain!
🌐 DNS Provider Instructions
Choose your DNS provider for specific setup instructions:
🔍 Verification Status
Understanding Statuses
🟡 Pending
Domain is added but not yet verified. DNS record needs to be configured.
🟢 Verified
Domain is verified and ready to track analytics. You can create projects for this domain.
🔴 Failed
Verification failed. Check DNS configuration and try again.
🔄 Auto-Verified
Domain was automatically verified (company email match or whitelist).
Automatic Verification
Some domains are automatically verified:
Auto-verification criteria:
- Your registered email domain matches the domain you're verifying
- You're part of a pre-approved organization
- Domain is whitelisted for testing purposes
🔧 Troubleshooting
Common Verification Issues
DNS Propagation Tools
Check if your DNS record is visible globally:
DNS Checker
Check DNS propagation from multiple locations worldwide
WhatsMyDNS
Global DNS propagation checker with visual map
DNS Lookup
Google's DNS lookup tool for technical analysis
Manual DNS Check
You can also check DNS records manually:
# Check TXT record (Linux/Mac)
dig TXT _databuddy.example.com
# Alternative command
nslookup -type=TXT _databuddy.example.com
# Expected output should show your verification token# Check TXT record (Windows)
Resolve-DnsName -Name "_databuddy.example.com" -Type TXT
# Alternative command
nslookup -type=TXT _databuddy.example.com
# Expected output should show your verification token📚 Advanced Configuration
Multiple Domains
You can verify multiple domains for a single project:
Use cases for multiple domains:
- Different environments:
staging.example.com,app.example.com - Multiple brands under one organization
- International domains:
example.com,example.co.uk
Each domain needs its own verification:
- Add each domain separately
- Get unique verification token for each
- Configure DNS record for each domain
- Verify each domain individually
Subdomain Considerations
Root domain vs subdomain verification:
- Root domain (
example.com): Coverswww.example.comautomatically - Subdomain (
app.example.com): Only covers that specific subdomain - Wildcard: Not currently supported
Important: If you use subdomains, verify each one separately. Verifying example.com does NOT automatically verify app.example.com.
Security Best Practices
Token Security
- Don't share verification tokens publicly
- Regenerate tokens if compromised
- Store tokens securely if needed for automation
DNS Security
- Use DNSSEC if your provider supports it
- Monitor DNS records for unauthorized changes
- Keep DNS provider account secure with 2FA
❓ Still Having Issues?
If you're still having trouble with domain verification:
Discord Community
Get real-time help from our community and team
Email Support
Contact our support team directly
Documentation
Continue with the getting started guide once verified
Next Steps: Once your domain is verified, you can create your first project and start tracking analytics!