How wireshark.org treats AI agents
wireshark.org is open to AI agents: no bot wall, no JavaScript needed, robots.txt restricts some paths, no llms.txt, feed or sitemap. A plain HTTP fetch works.
| Fact | Value | Source |
|---|---|---|
| Access | Open | Registry check, unverified, 25 Oct 2026 |
| Bot wall | None | Registry check, unverified, 25 Oct 2026 |
| JavaScript needed | No | Registry check, unverified, 25 Oct 2026 |
| robots.txt | Restricts some paths | Registry check, unverified, 25 Oct 2026 |
| Machine interface | None found | Registry check, unverified, 25 Oct 2026 |
Listed in
Questions
Does wireshark.org block AI bots?
No. wireshark.org is open to AI agents.
Does wireshark.org need JavaScript?
No. The page has real content without JavaScript.
Does wireshark.org have an llms.txt?
No llms.txt was found.
Does wireshark.org use a bot wall?
No bot wall was seen.
How should an agent fetch wireshark.org?
A plain HTTP fetch works.
Use this from an agent
JSON: /v1/origins/wireshark.org. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.