Dots

A dot visits a page because a task its user set led there. Dots work on goals over time, so a visit doesn’t need a live chat.

• Goal-driven work: Dots keep working between conversations on goals the user sets.
• Its own browser and sessions: A dot’s cloud browser has its own sessions and doesn’t inherit logins from the user’s personal browser.
• Possible human control: The user can take over the browser at any point, so mixed human and agent activity is possible.
• Not a crawler: OpenAI describes dots as personal agents and doesn’t list them among its crawlers. Its crawlers each have their own entry on its crawler page.
• No published schedule or rate: OpenAI doesn’t document how often or how heavily a dot visits a site.

1. Check OpenAI’s documentation first. Start with OpenAI’s crawler page. If dots gets an entry later, use its user-agent and IP list. Recheck the page from time to time, since OpenAI offers an RSS feed for updates.
2. Don’t borrow other OpenAI lists. OpenAI publishes IP files for OAI-SearchBot, OAI-AdsBot, GPTBot, and ChatGPT-User. A match against one of them doesn’t verify dots.
3. Look at behavior. Review requested paths, request rates, session length, and sign-in activity. Dots can sign in to sites with credentials the user provides, so logged-in sessions are possible. In DataDome’s testing, Dots reached forms, login, cart, and payment steps of a shopping journey.
4. Compare against your bot signals. Check how your bot management classifies the traffic today. Treat it as an automated browser unless you have a reason to think otherwise.
5. Expect mixed activity. A user can take over the browser, so one session may include both agent and human actions.
6. Check robots.txt behavior in your logs. OpenAI says robots.txt rules may not apply to ChatGPT-User because a user starts the action. OpenAI doesn’t say how dots treats robots.txt, so confirm in your logs whether it requests the file.

It depends on your content policies, security needs, and how you want to treat people who use AI agents to browse for them. A dot acts for a real user, so blocking it can also block that user’s task.

There’s no documented robots.txt token for dots, so a block has to happen on your side, through your server or bot management. Without a published identity, it also means blocking by behavior rather than by name.

Consider restricting automated browser traffic when:

• Requests fail your verification or behavior checks
• Your content is subscription-based, licensed, or restricted for automated access
• Paths such as account, checkout, or admin areas shouldn’t be open to agents
• Request volume affects performance or infrastructure costs
• Your policy doesn’t allow agent-driven access to your content

If you want agents working for your customers to reach your site, allow them and focus on protecting sensitive paths and accounts. You can also set policy by endpoint, such as allowing catalog browsing while applying intent checks on login and checkout, or allow, block, rate-limit, or monetize agent traffic outright. You can set separate preferences for OpenAI’s crawlers through their own tokens.

OpenAI doesn’t document a robots.txt token for dots, so there’s no rule to add that you can count on. Robots.txt also relies on the visitor to comply, and, for ChatGPT-User, OpenAI says rules may not apply to actions a user starts. Use controls you run yourself.

• Protect restricted resources: use authentication and authorization for private content, accounts, and checkout. Don’t count on robots.txt alone.
• Use bot management: set policies for automated browser traffic based on behavior, not on a user-agent name.
• Set rate limits with care: rate limiting can control excess traffic. Base thresholds on observed behavior, and don’t assume a low limit will never affect legitimate visitors.
• Treat sign-ins like any other: Dots can sign in with credentials the user provides and a verification step the user completes. Apply your usual login protections.
• Keep OpenAI’s crawler rules separate: use the documented tokens for OAI-SearchBot, GPTBot, and ChatGPT-User where you want them. They don’t cover dots.
• Monitor and recheck: review server, CDN, and bot management data. Check OpenAI’s crawler page again as the product develops.

OpenAI dots is a new personal agent that browses from its own cloud browser. OpenAI documents no user-agent, IP list, or robots.txt token for it, so there’s no official identity to check. In DataDome’s testing, Dots runs a real Chrome-based browser on a cloud virtual machine and can complete purchases.

Our recommendation is to treat dots traffic as unverified, not as malicious: let it in and let intent decide on each request, since a session can mix agent and human activity and a single check at the first request isn’t enough. You can also set policy by endpoint, or allow, block, rate-limit or monetize it outright, based on your content policy. 

This is where we can help. With DataDome Bot Protect, you can detect dots traffic and see and control it with intent-based detection. Our Agent Trust capability scores each agent in real time and keeps checking its behavior across the session. You choose which agents reach which parts of your site, and you can set different rules for agents and for OpenAI’s crawlers.

Whatever you decide, recheck OpenAI’s documentation as dots evolve, and protect sensitive paths with authentication and authorization.