What is EFF DNT policy checker?

EFF DNT policy checker is operated by the Electronic Frontier Foundation to verify whether websites properly implement Do Not Track policies. The bot checks sites for compliance with DNT headers and privacy commitments. Agent Analytics can track when it visits your website.

Category

Developer Helper
Assists with testing, debugging, and ensuring website functionality

Expected Behavior

EFF DNT policy checker's traffic is as regular as a cron job, because it usually is one. Uptime monitors hit the same endpoint every few minutes, while performance and audit tools run deeper scans on demand. Expect narrow, repetitive access to specific pages rather than crawling.

Overview

Operated By Electronic Frontier
Expected To Follow Robots.txt No
Insights Last Updated July 6, 2026

Robots.txt Blocked Percentage

0%
0% of top websites are blocking EFF DNT policy checker
Learn How →

Country of Origin

United States
EFF DNT policy checker normally visits From the United States

Robots.txt Blocking Trend

As of July 6, 2026, 0% of top websites block EFF DNT policy checker in their robots.txt files.

Overall Developer Helper Traffic

As of July 6, 2026, 0.6% of all web traffic came from developer helpers.

Top Visited Website Categories

Games
People and Society
Computers and Electronics
Internet and Telecom
Reference
Track Developer Helpers Visiting Your Website
Use Agent Analytics to get realtime visibility into visits from every crawler, scraper, and AI agent.

This data reflects agent visits measured across thousands of websites using Agent Analytics, combined with daily scans of the world's top 1000 websites and their robots.txt files.

EFF DNT policy checker's User Agent

User Agent Mozilla/5.0 (compatible; EFF DNT policy checker +https://www.eff.org/dnt-policy) for questions or concerns email dnt-policy at eff.org

Access other known user agents and IP addresses using the Enterprise API.

How To Block EFF DNT policy checker

Add this rule to your robots.txt file to request that EFF DNT policy checker not access your website. You can customize which pages are blocked by swapping out / for a different path.

User-agent: EFF DNT policy checker # https://knownagents.com/agents/eff-dnt-policy-checker
Disallow: /
Block Every Developer Helper
⚠️ Manually adding individual robots.txt rules is not scalable. Instead, use Automatic Robots.txt.

Frequently Asked Questions

Should I Block EFF DNT policy checker?

Only if nobody you work with uses it. EFF DNT policy checker is the kind of tool a team points at its own site for uptime checks, performance tests, and audits. If someone on your team relies on it, blocking it silently breaks their monitoring. Almost none of the top websites we track have robots.txt rules for EFF DNT policy checker right now.

Does EFF DNT policy checker Respect Robots.txt?

No. EFF DNT policy checker is not expected to honor robots.txt, so a disallow rule only states your preference. Enforce the block with firewall or server rules, then confirm in Agent Analytics that its requests actually stop.

Does EFF DNT policy checker Access Private Content?

Only if its owner sets that up. Monitoring tools check whatever they are configured to check, which can include staging sites and private health endpoints when a team grants access. Uninvited, EFF DNT policy checker sees only public pages.

Why Is EFF DNT policy checker Visiting My Website?

Someone pointed EFF DNT policy checker at your site, most likely your own team. Uptime monitors, performance testers, and audit tools only visit the sites they are configured to watch.

How Can I Tell if EFF DNT policy checker Is Visiting My Website?

Agent Analytics tracks EFF DNT policy checker visits in real time alongside every other known AI agent, crawler, and scraper. You can also check your server logs for requests whose user agent string contains "EFF DNT policy checker". Look for regular checks of the same pages or endpoints, often minutes apart. Keep in mind that EFF DNT policy checker doesn't publish a verification method, so any client can claim its user agent string and a log match is a hint rather than proof.

References