Bot intelligence record
Seekport
Usually allowSeekport is a search crawler from SISTRIX used for search indexing, URL discovery, page rendering, result freshness; it appears in server logs as `SeekportBot`.
User-Agent Pattern
SISTRIXSeekportBot
User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.
Robots.txt Snippet
Click snippet to copyUser-agent: SeekportBot
Disallow: /
Click the snippet to copy it, or highlight the text manually.
Handling Guidance
DependsThis bot is usually safe to allow when the request source is verified and the traffic matches your site policy.
Seekport is used for search indexing, URL discovery, page rendering, result freshness, and search-quality checks.
Record Details
Verified fields- Operator
- SISTRIX
- Family
- SISTRIX
- Type
- Search
- Purpose
- Indexing
- Identity type
- Verified Bot
- Confidence
- Medium
- Last verified
- 2026-06-23
- Last checked
- 2026-06-23
- Source type
- Documented
- Verification
- Verify Seekport by matching `SeekportBot` to SISTRIX evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- Spoofing risk
- Seekport has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
Notes
- Seekport is a search crawler from SISTRIX used for search indexing, URL discovery, page rendering, result freshness, and search-quality checks.
- Its primary user-agent pattern is
SeekportBot; a representative HTTP user-agent isMozilla/5.0 (compatible; SeekportBot; +https://bot.seekport.com). - Seekport is verified with Medium confidence. The identity type is Verified Bot, and the evidence basis is a public crawler reference or source-linked documentation.
- Seekport is marked as not reliably governed by robots.txt directives; use server-side rules if the traffic should be restricted.
- Seekport can usually be allowed after confirming the source and monitoring request volume.
Evidence and Source
- Verify Seekport by matching `SeekportBot` to SISTRIX evidence, then checking reverse DNS, source-network ownership, signed request data, or published crawler documentation when available.
- Seekport traffic is primarily detected by the `SeekportBot` user-agent pattern; a representative HTTP user-agent is `Mozilla/5.0 (compatible; SeekportBot; +https://bot.seekport.com)`. Compare source IPs, reverse DNS, request paths, and crawl cadence with SISTRIX infrastructure before trusting the traffic.
- Seekport is used for search indexing, URL discovery, page rendering, result freshness, and search-quality checks.
- Seekport has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
Use This Signal In Edge
Botcrawl EdgeUse Edge to match live requests, detect related datacenter traffic, and apply allow, block, rate-limit, or log rules.
