Overview
LohiSoftBot is a crawler associated with LohiSoft s.r.o. and used for search-indexing.
The primary identifying User-Agent token is LohiSoftBot. Representative HTTP request identity: LohiSoftBot/1.0 (+https://lohisoft.com/bot).
Directory status: Active. Identity classification: Verified with High confidence. Identity type: official documented.
This identity is recorded as honoring robots.txt under LohiSoftBot. Site-specific access policy should still be evaluated before enforcement.
Risk classification: Neutral. Recommended handling is to evaluate the request context before allowing, rate-limiting, or blocking.
Identity
- User-Agent Pattern
-
LohiSoftBot - Aliases
- LohiSoftBot/1.0
- HTTP Agent Examples
-
LohiSoftBot/1.0 (+https://lohisoft.com/bot) - Robots Token
- LohiSoftBot
- Identity Type
- Officially documented
- Evidence Method
- Match `LohiSoftBot` as the claimed identity signal and corroborate it with independent network, DNS, cryptographic, or request-context signals when stronger authentication is required.
Classification
- Type
- Search
- Kind
- Crawler
- Family
- LohiSoft
- Purpose
- Search indexing
Behavior and handling
- Common Use
- Builds a search index from selected public page metadata, headings, URLs, and link text.
- Detection Notes
- Match the `LohiSoftBot` User-Agent token and consider recorded aliases where applicable. A User-Agent match identifies a claim, not authenticated origin.
- Respects robots.txt
- Yes
- Spoofing Risk
- The `LohiSoftBot` User-Agent token can be copied by unrelated clients. Treat it as a claimed identity unless corroborated by stronger request or network signals.
- Risk
- Neutral
- Recommended Handling
- Depends
Rules and controls
- Robots.txt Snippet
-
User-agent: LohiSoftBot Disallow: / - Apache Rule
-
RewriteCond %{HTTP_USER_AGENT} "LohiSoftBot" [NC] RewriteRule ^ - [F,L] - Nginx Rule
-
if ($http_user_agent ~* "LohiSoftBot") { return 403; }
Relationships
- Operator
- LohiSoft s.r.o. Checked 2026-10-05
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.