Overview
Kernel Browsers is an AI crawler from Kernel used for assistant-driven browsing, page retrieval, and automated web access on behalf of an AI product.
Its primary user-agent pattern is kernel; related patterns include Kernel Browsers.
Kernel Browsers is Unverified at the identity-evidence level. The listed identity remains useful for detection, but this record does not currently contain authoritative evidence sufficient to authenticate the identity claim.
Robots.txt behavior is not currently confirmed.
Kernel Browsers should be handled according to the site owner’s AI crawler policy, with allow, block, or rate-limit rules applied deliberately.
Identity
- User-Agent Pattern
-
kernel - Aliases
- Kernel Browsers
- HTTP Agent Examples
-
kernel - Robots Token
- kernel
- Identity Type
- Observed
- Evidence Method
- Treat `kernel` as an identity signal only. Confirm it with current operator documentation, cryptographic verification, forward-confirmed reverse DNS, source-network ownership, or other authoritative evidence before trusting the claimed identity.
Classification
- Type
- AI
- Kind
- Agent
- Family
- Kernel
- Purpose
- AI assistant
Behavior and handling
- Common Use
- Kernel Browsers is used for assistant-driven browsing, page retrieval, and automated web access on behalf of an AI product.
- Detection Notes
- Kernel Browsers traffic is primarily detected by the `kernel` user-agent pattern; related patterns include `Kernel Browsers`. Compare source IPs, reverse DNS, request paths, and crawl cadence with Kernel infrastructure before trusting the traffic.
- Respects robots.txt
- Unknown
- Spoofing Risk
- Kernel Browsers has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
- Risk
- Neutral
- Recommended Handling
- Depends
Rules and controls
- Robots.txt Snippet
-
# robots.txt behavior is unconfirmed. Do not rely on this rule without verification.
Relationships
- Operator
- Kernel Checked 2026-08-07
Relationships without an Evidence link are normalized from the canonical directory record. They should not be interpreted as independent proof of physical presence or request origin.