Verifying Domains
Overview
After adding a domain to your workspace, you must verify ownership using a DNS TXT record — or, if you can’t edit the domain’s DNS, by serving the verification token over HTTP. This verification proves you control the domain and authorizes Pensar to perform security testing.
The verification dialog opens automatically after creating a domain, showing your unique TXT record and verification instructions.
Why Domain Verification?
Domain verification is a critical security measure that:
- Proves Ownership: Ensures you control the domain before testing begins
- Prevents Abuse: Protects others from unauthorized security testing
- Legal Protection: Provides evidence of authorization for penetration testing
- Compliance: Demonstrates due diligence for security assessments
Verification Process
When you create a domain, a verification dialog automatically opens with your unique DNS TXT record.
View Your TXT Record
The verification dialog displays:
- Your unique verification record (format:
pensar=<token>) - A copy button for easy copying
- Instructions for adding the record
- A verify button to check verification status
Copy the Record
Click the Copy icon next to the TXT record to copy it to your clipboard. This ensures you don’t make any typos when adding it to your DNS.
Add to Your DNS Provider
Log in to your DNS provider and add a new TXT record:
- Type: TXT
- Name:
_pensar.<your-domain>— the full name shown in the dialog - Value: Paste the copied record (format:
pensar=<token>) - TTL: 3600 seconds (or your provider’s default)
Name fields differ by provider: some take the full name, others append
the hosted zone to what you type. Check what the field shows — if it
displays the zone beside or below the input, enter only the part before
it. In the example.com zone that makes _pensar.app.example.com into
_pensar.app, and _pensar.example.com into _pensar. Entering the
full name in a field that appends the zone publishes the record at
_pensar.app.example.com.example.com — the wrong name, where
verification won’t look for it.
Wait for DNS Propagation
DNS changes take time to propagate globally:
- Fast providers (Cloudflare, Vercel): 1-5 minutes
- Most providers: 10-30 minutes
- Maximum: Up to 48 hours (rare)
HTTP File Verification (No DNS Access)
If you can’t add DNS records — common for apps hosted on platform subdomains like myapp.onrender.com or myapp.herokuapp.com — serve the verification token over HTTP instead. Both methods use the same token, and clicking Verify checks both automatically.
Serve It at the Well-Known Path
Make your app respond with the record as plain text at:
The response body must be exactly the record value (surrounding whitespace is ignored), served with a 200 status over HTTPS. For example, in Express:
Or simply place a static file named pensar-verification containing the record in your app’s .well-known public directory.
Keep the route or file in place permanently — just like the DNS TXT record, it allows instant re-verification later and poses no security risk.
DNS TXT Record Format
Your verification TXT record follows this specific format:
Examples by Domain Type
Subdomain
Root Domain
With Port
Domain: app.example.com
If the name field appends the hosted zone, enter only the part before it.
In the example.com zone that is _pensar.app, not _pensar:
DNS Provider Guides
Step-by-step instructions for popular DNS providers:
Cloudflare
Adding TXT Record in Cloudflare:
- Log in to your Cloudflare dashboard
- Select the domain you’re verifying
- Click DNS in the sidebar, then Records
- Click Add record
- Configure the record:
- Type: TXT
- Name:
_pensarfor the targetexample.com,_pensar.appforapp.example.com— Cloudflare appends the zone, and shows the resulting full name under the field - Content: Paste your full record value (e.g.,
pensar=abc123...) - TTL: Auto (or 3600)
- Proxy status: DNS only (gray cloud)
- Click Save
- Wait 1-5 minutes for propagation
- Return to Pensar Console and click Verify
Cloudflare typically propagates DNS changes within 1-2 minutes, making it one of the fastest providers for verification.
AWS Route 53
Adding TXT Record in Route 53:
- Open the Route 53 console
- Click Hosted zones in the sidebar
- Select the hosted zone for your domain
- Click Create record
- Configure the record:
- Record name: the part before the hosted zone name shown beside the field —
_pensarfor the targetexample.com,_pensar.appforapp.example.com(field reference) - Record type: TXT
- Value:
"pensar=<token>"(enclose in double quotes) - TTL (seconds): 300 or 3600
- Routing policy: Simple routing
- Record name: the part before the hosted zone name shown beside the field —
- Click Create records
- Wait 5-10 minutes for propagation
- Return to Pensar Console and click Verify
Route 53 requires:
- TXT values enclosed in double quotes:
"pensar=token", notpensar=token - The record name relative to the hosted zone — the console shows the zone suffix beside the field and appends it to what you type
Google Cloud DNS
Adding TXT Record in Google Cloud DNS:
- Open the Cloud DNS console
- Click on your DNS zone
- Click Add record set at the top
- Configure the record:
- DNS name: the full name with a trailing dot —
_pensar.example.com.for the targetexample.com,_pensar.app.example.com.forapp.example.com. Google Cloud DNS does not append the zone - Resource record type: TXT
- TTL: 3600 seconds
- TXT data:
pensar=<token>(no quotes needed)
- DNS name: the full name with a trailing dot —
- Click Create
- Wait 5-10 minutes for propagation
- Return to Pensar Console and click Verify
Google Cloud DNS requires the trailing dot in the DNS name but doesn’t require quotes around the value.
GoDaddy
Adding TXT Record in GoDaddy:
- Log in to your GoDaddy account
- Navigate to My Products > All Products and Services
- Find your domain and click DNS
- Scroll to the Records section
- Click Add and select TXT
- Configure the record:
- Name: the name minus the zone, which is appended for you —
_pensarfor the targetexample.com,_pensar.appforapp.example.com - Value: Paste your full record value
- TTL: 3600 seconds (or 1 hour)
- Name: the name minus the zone, which is appended for you —
- Click Save
- Wait 10-30 minutes for propagation (GoDaddy can be slower)
- Return to Pensar Console and click Verify
GoDaddy DNS propagation can take 10-30 minutes or longer. If verification fails, wait a bit longer and try again.
Namecheap
Adding TXT Record in Namecheap:
- Log in to your Namecheap account
- Navigate to Domain List
- Click Manage next to your domain
- Go to the Advanced DNS tab
- Click Add New Record in the Host Records section
- Configure the record:
- Type: TXT Record
- Host: the name minus the zone, which is appended for you —
_pensarfor the targetexample.com,_pensar.appforapp.example.com - Value: Paste your full record value
- TTL: Automatic (or select a specific value)
- Click the checkmark to save
- Wait 10-30 minutes for propagation
- Return to Pensar Console and click Verify
DigitalOcean
Adding TXT Record in DigitalOcean:
- Log in to your DigitalOcean account
- Navigate to Networking > Domains
- Click on your domain
- Scroll to the Add a record section
- Configure the record:
- Type: TXT
- Hostname: the name minus the zone, which is appended for you —
_pensarfor the targetexample.com,_pensar.appforapp.example.com - Value: Paste your full record value
- TTL (seconds): 3600
- Click Create Record
- Wait 5-10 minutes for propagation
- Return to Pensar Console and click Verify
Vercel
Adding TXT Record in Vercel:
- Log in to your Vercel dashboard
- Navigate to your project
- Go to Settings > Domains
- Click on your domain
- Scroll to DNS Records
- Click Add and select TXT
- Configure the record:
- Name: the name minus the zone, which is appended for you —
_pensarfor the targetexample.com,_pensar.appforapp.example.com - Value: Paste your full record value
- TTL: Default (automatic)
- Name: the name minus the zone, which is appended for you —
- Click Save
- Wait 1-5 minutes for propagation (Vercel is very fast)
- Return to Pensar Console and click Verify
Netlify
Adding TXT Record in Netlify:
- Log in to your Netlify dashboard
- Navigate to Domains
- Select your domain
- Click DNS settings
- Scroll to DNS records
- Click Add new record
- Configure the record:
- Record type: TXT
- Name: the name minus the zone, which is appended for you —
_pensarfor the targetexample.com,_pensar.appforapp.example.com - Value: Paste your full record value
- TTL: 3600
- Click Save
- Wait 5-10 minutes for propagation
- Return to Pensar Console and click Verify
Checking DNS Propagation
Before clicking verify, you can check if your TXT record has propagated:
Online DNS Checker Tools
Command Line Tools
You can also check from your terminal:
dig
nslookup
host
Using dig (Linux/Mac):
Expected output:
Troubleshooting Verification
If verification fails, follow these troubleshooting steps:
TXT Record Not Found
Problem: The DNS lookup can’t find your TXT record.
Solutions:
- Wait longer: DNS propagation can take 10-30 minutes (sometimes longer)
- Check the record exists: Log back into your DNS provider and verify the record is saved
- Check the name: query the full name —
dig _pensar.<your-domain> TXT. A record on the bare domain still verifies, but a record on the wrong name does not - Check the zone wasn’t appended twice: if the name field appends the hosted zone,
_pensar.app.example.comtyped into it lands at_pensar.app.example.com.example.com. Enter_pensar.appinstead - Check DNS propagation: Use online tools to see if the record is visible globally
If your DNS provider’s interface shows the record but verification fails, it usually means the record hasn’t propagated yet. Wait 5-10 more minutes and try again.
Record Format Issues
Problem: The record exists but doesn’t match the expected format.
Common mistakes:
- ❌ Missing
_pensarprefix in the name - ❌ The hosted zone appended twice (
_pensar.app.example.com.example.com) - ❌ Missing
pensar=in the value (just the token) - ❌ Extra quotes added when they shouldn’t be
- ❌ Spaces or line breaks in the value
- ❌ Wrong label (e.g.,
_verifyinstead of_pensar)
Correct format, for the target app.example.com:
Action: Delete the record and re-add it, carefully copying the value from the Pensar verification dialog using the Copy button.
DNS Provider Specific Issues
Problem: Different DNS providers have different formatting requirements.
Provider-specific tips:
Route 53 (AWS):
- Requires double quotes:
"pensar=token" - Appends the zone shown beside the field — enter
_pensar.app, not_pensar.app.example.com
Google Cloud DNS:
- Takes the full name with a trailing dot:
_pensar.app.example.com. - No quotes needed
Cloudflare:
- Appends the zone — enter the name without it (
_pensar.appin theexample.comzone) - No trailing dot needed
- No quotes needed
GoDaddy/Namecheap:
- Append the zone — enter the name without it (
_pensar.appin theexample.comzone) - No quotes needed
Check your provider’s documentation for TXT record formatting requirements.
Multiple TXT Records
Problem: Your domain already has other TXT records and there may be conflicts.
Solution:
- Multiple TXT records for the same host are allowed
- DNS returns all TXT records for a host
- The Pensar verification looks specifically for the
pensar=prefix - Having other TXT records (like SPF, DKIM, etc.) won’t interfere
If you have issues:
- Ensure your new record is actually saved and visible
- Check that the
pensar=value is correct - Try querying the DNS to see all TXT records returned
Propagation Taking Too Long
Problem: It’s been over 30 minutes and the record still isn’t visible.
Possible causes:
- DNS provider is slow: Some providers take longer (GoDaddy, some regional providers)
- Caching: Your local DNS may be caching old results
- DNS not saved: The record might not have been saved properly
Actions to take:
- Clear your local DNS cache:
- Mac:
sudo dscacheutil -flushcache - Windows:
ipconfig /flushdns - Linux:
sudo systemd-resolve --flush-caches
- Mac:
- Check from a different network or device
- Use an online DNS checker to see global propagation
- Verify the record is actually saved in your DNS provider’s interface
- If it’s been over 2 hours, contact your DNS provider’s support
Verification Error Messages
Common error messages and solutions:
“Verification token not found. Add a TXT record with name … and value …”
- Neither the DNS lookup nor the well-known file produced a matching token
- The message names the exact name and value to publish — compare both against your provider
- Common causes: propagation not finished, a typo, or the record at the wrong name
“A Pensar TXT record resolved for this domain, but no published value matches.”
- A
pensar=record was found, but none of the published values is this domain’s - The value may be stale, mistyped, or issued for a different domain or workspace. Publish the value from this domain’s dialog
“No verification record found. Please create one first.”
- The domain has no token yet. Reopen the verification dialog to issue one
Re-Verifying Domains
You can re-verify a domain at any time:
The verification token for a domain doesn’t change, so you only need to add the DNS TXT record once. You can verify multiple times using the same record.
After Successful Verification
Once your domain is verified:
Status Updates
In the Domains list:
- Verified column shows a green checkmark ✓
- Last Analyzed shows when reconnaissance started
- An animated radar icon appears while reconnaissance is running
Best Practices
Leave TXT Records in Place
Recommendation: Keep your verification TXT record in your DNS permanently.
Why:
- No security risk - the token is public and only proves ownership
- Allows easy re-verification if needed
- Doesn’t interfere with other DNS records
- Takes up minimal DNS resources
- Makes future verification instant
When to remove:
- You permanently stop using Pensar
- You delete the domain from your workspace
- Your organization requires cleanup of unused records
Verify Before Production Testing
Recommendation: Verify and test staging/development domains before production.
Benefits:
- Familiarize yourself with the process
- Ensure verification works smoothly
- Test the security testing process in a safe environment
- Validate that test credentials work
- Confirm penetration testing doesn’t disrupt services
Document Your DNS Records
Recommendation: Keep a record of all DNS TXT records you add for services.
Why:
- Know what each record is for
- Makes cleanup easier later
- Helps when troubleshooting DNS issues
- Useful for team knowledge sharing
- Required for some compliance frameworks
What to document:
- Service name (Pensar)
- Purpose (Domain verification)
- Record host (
_pensar.example.com) - Date added
- Who added it
Test DNS Propagation First
Recommendation: Check DNS propagation before clicking Verify in Pensar.
How:
- Use online DNS checker tools
- Run command-line queries
- Check from multiple locations
- Wait until you see the record globally
Benefits:
- Avoid failed verification attempts
- Know the record is working before testing
- Understand propagation time for your DNS provider
- Catch formatting errors early
Security Considerations
The DNS TXT record verification token is public information and is safe to share. It only proves domain ownership and cannot be used to access your systems or data.
Is the Verification Token Secret?
No. The verification token:
- ✅ Proves you can add DNS records to the domain
- ✅ Is publicly queryable by anyone via DNS lookup
- ✅ Only authorizes Pensar to test that specific domain
- ❌ Does NOT provide access to your application
- ❌ Does NOT contain sensitive information
- ❌ Cannot be used to compromise security
Can Someone Use My Token?
No. Even if someone copies your verification token:
- They can’t add it to their DNS for your domain (they don’t control your DNS)
- They can’t use it to verify their own domain (tokens are domain-specific)
- They can’t gain access to your Pensar workspace
- They can’t trigger tests on your domain without Pensar workspace access
Removing Verification Records
You can safely remove TXT records if:
- You’re no longer using Pensar
- You’ve deleted the domain from your workspace
- You need to clean up DNS records
To remove:
- Log in to your DNS provider
- Find the TXT record with host
_pensar.yourdomain.com - Delete the record
- Wait for DNS propagation (changes take effect in 5-30 minutes)
If you remove the verification record, you’ll need to add it back if you ever want to re-verify the domain in the future. However, the token value remains the same.