What is Do Not Track Verifier?
Do Not Track Verifier is operated by the Electronic Frontier Foundation to test whether websites properly implement Do Not Track (DNT) browser signals. The bot checks if sites honor user privacy preferences by respecting DNT headers sent by web browsers. You can set up Agent Analytics to see when Do Not Track Verifier visits your website.
Category
| Example User Agent | Electronic Frontier Foundation's Do Not Track Verifier (for questions or concerns email dnt-policy@eff.org) |
| Operated By | Electronic Frontier Foundation |
| Triggered By | Scheduled or manual configuration |
| Used for AI Model Training | Not expected |
| Affects AI Chat & Search Visibility | Not directly |
| Expected To Follow Robots.txt | No |
Why Is Do Not Track Verifier Visiting My Website?
Someone, most likely on your own team, configured Do Not Track Verifier to check your site. Uptime monitors, performance testers, and audit tools visit only the sites or endpoints they are told to watch.
Should I Block Do Not Track Verifier?
Only if no one on your team relies on it. Do Not Track Verifier may support uptime monitoring, performance tests, or audits. Blocking it without checking first can silently disrupt those workflows. For context, 7% of the top websites we track currently have robots.txt rules for Do Not Track Verifier.
Insights for Do Not Track Verifier
As of October 30, 2026, this data reflects agent visits measured across thousands of websites using Agent Analytics, combined with daily scans of the top 1000 websites and their robots.txt files.
Robots.txt Compliance
Country of Origin
Robots.txt Blocked Percentage
Do Not Track Verifier Traffic
Frequently Asked Questions
What Traffic Patterns Should I Expect From Do Not Track Verifier?
Do Not Track Verifier's traffic often follows fixed intervals like a cron job. Activity may consist of short recurring checks or occasional intensive bursts, but it usually remains limited to a specific set of pages or endpoints.
Does Do Not Track Verifier Follow Robots.txt Rules?
No. Do Not Track Verifier is not expected to follow robots.txt rules, so a disallow rule only communicates your preference. Enforce the block with firewall or server rules, then use Agent Analytics to verify that its requests stop.
Is Do Not Track Verifier Used for AI Model Training?
Not ordinarily. Do Not Track Verifier is not categorized as an AI training scraper or data provider, so AI model training is not its expected purpose.
Does Blocking Do Not Track Verifier Affect AI Search or Citations?
Not directly. Do Not Track Verifier's expected purpose is not to supply an AI search index or retrieve pages for AI-generated answers.
Does Do Not Track Verifier Access Private Content?
Only when configured with access. A team may grant Do Not Track Verifier credentials to monitor staging sites or private health endpoints. Without those credentials, it sees only public pages.
How Can I Verify a Request From Do Not Track Verifier?
Agent Analytics tracks Do Not Track Verifier visits in real time. You can also check your server logs for requests whose user-agent string contains "Do Not Track Verifier". Look for repeated checks of the same pages or endpoints at regular intervals. Because Do Not Track Verifier does not publish a verification method, any client can claim its identity and a log match is only a clue.