Server Log Analysis Reveals How Major AI Crawlers Actually Behave on Websites
A detailed review of server access logs shows that most AI vendors operate several distinct bots rather than a single crawler. Each bot serves a different function, and treating them identically in configuration files leads to unintended consequences.
GPTBot performs scheduled crawls for model training, respects robots.txt, and systematically follows sitemaps. OAI-SearchBot builds the search index used for answers that include citations. ChatGPT-User makes on-demand requests triggered by an individual user query. The same separation exists at other providers: Perplexity runs PerplexityBot for indexing and a separate user agent for live queries, while Anthropic maintains ClaudeBot alongside its own user-triggered agents.
Log analysis reveals three consistent request patterns. Index bots traverse site maps and internal links at regular intervals without correlation to traffic spikes. User agents issue single, targeted requests for specific URLs, often carrying a referrer from the AI service. All bots request robots.txt regularly, request sitemap.xml less frequently, and almost never request llms.txt. Over 515 million recorded AI-bot events, only 408 requests targeted llms.txt.
User-Agent strings are easily forged, so verification relies on reverse DNS or, preferably, comparison against IP ranges published by each vendor. A simple script that extracts IPs from logs and checks them against known OpenAI ranges quickly identifies spoofed traffic from unrelated scrapers.
Because llms.txt receives negligible attention from actual crawlers, site owners achieve better results by ensuring content remains in static HTML, pages load quickly, and robots.txt selectively permits user-agent traffic while blocking training bots. Structured headings and self-contained sections also improve the quality of excerpts returned to users.
Related articles
Agent-Ops 0.4.0 Released: Methodology for Secure Human-AI Collaboration in IT Operations
Sergey Zhitinsky, founder of Git in Sky, has published the public normative candidate for Agent-Ops 0.4.0, an open industry methodology governing how engineers and AI agents jointly handle IT infrastructure tasks. The framework keeps humans firmly in the decision-making loop while using deterministic programs for data collection and approved changes. It addresses risks such as prompt injection through processed data, unverified model outputs, and unclear accountability when AI recommendations lead to incidents. The methodology divides work across eight explicit steps and three separate planes: data, governance, and independent verification performed by a Guardian role. Two additional companies have joined as maintainers following agreements at the IT Elements 2026 conference, turning the project into a multi-organization effort. Contributors are invited to help refine contracts, schemas, and operational scenarios through GitHub and GitVerse.
ProxyKey MCP: Securing API Access for AI Agents Without Exposing Credentials
ProxyKey has released an MCP server that allows AI coding agents such as Claude Code and Cursor to manage API credentials without ever reading the actual secret values. The solution addresses the risk that any key visible to an agent becomes compromised through logging, tracing, or prompt injection. Real provider keys are stored encrypted with AES-256-GCM and never returned by any API endpoint after initial entry. Agents instead receive limited virtual passes that support IP binding, rate limits, TTL, and detailed request logging. A pending-secret workflow lets agents prepare services before the real token exists, with the human entering the secret only through a web panel. The approach deliberately restricts the MCP tool contract so no operation can read or return secret values.
Shadow AI in CI/CD: Why AI Agents Must Be Modeled as Security Threats
A new analysis from the CNCF highlights the growing risks of Shadow AI within continuous integration and continuous deployment pipelines. The report argues that AI agents should be treated as potential threats rather than simple productivity tools. Starting from a developer's laptop and extending to Kubernetes clusters, these agents can introduce unauthorized access paths and data exposure risks. Security teams are urged to incorporate AI agent behavior into formal threat modeling exercises. The discussion emphasizes the need for visibility and control over autonomous AI components operating in production environments.
Detecting Lateral Movement with Neural Networks Trained Solely on Synthetic Data
A researcher generated entire corporate network histories using a 135-line configuration file to create synthetic authentication logs containing lateral movement attacks. Neural networks trained exclusively on these artificial datasets were then evaluated against 1.65 billion real authentication events from Los Alamos National Laboratory, including 749 red team events across 301 compromised machines. The best ensemble of six models flagged 3.6 million hourly machine windows and placed 16 genuine attacks among the top 23 highest-scoring entries, producing only seven false positives. In comparison, a simple threshold counter required 161,000 false alarms to reach the same detection level. The approach also demonstrated an iterative feedback loop where detector errors directly informed refinements to the synthetic world generator. The work shows that synthetic data can reach AUC performance comparable to models trained on real labeled attacks while providing full control over the underlying attack definitions.