Overview
Nooshub is a feed fetcher used for RSS or Atom feed polling, syndication refresh, subscription delivery, and content update checks.
Its primary user-agent pattern is Nooshub; a representative HTTP user-agent is Mozilla/5.0 (compatible; Nooshub/1.0; +https://www.nooshub.com/statics/bots).
Nooshub is verified with Medium confidence. The identity type is Verified Bot, and the evidence basis is a public crawler reference or source-linked documentation.
Nooshub is marked as not reliably governed by robots.txt directives; use server-side rules if the traffic should be restricted.
Nooshub can usually be allowed after confirming the source and monitoring request volume.
Identity
- User-Agent Pattern
-
Nooshub - HTTP Agent Examples
-
Mozilla/5.0 (compatible; Nooshub/1.0; +https://www.nooshub.com/statics/bots) - Robots Token
- Nooshub
- Identity Type
- Verified bot
- Evidence Method
- Verify Nooshub by matching `Nooshub` to a public crawler reference or source-linked documentation, then checking reverse DNS, IP ownership, request behavior, and crawl consistency.
Classification
- Type
- Feed
- Kind
- Fetcher
- Family
- Nooshub
- Purpose
- Feed fetch
Behavior and handling
- Common Use
- Nooshub is used for RSS or Atom feed polling, syndication refresh, subscription delivery, and content update checks.
- Detection Notes
- Nooshub traffic is primarily detected by the `Nooshub` user-agent pattern; a representative HTTP user-agent is `Mozilla/5.0 (compatible; Nooshub/1.0; +https://www.nooshub.com/statics/bots)`. Compare source IPs, reverse DNS, request paths, and crawl cadence before trusting the traffic.
- Respects robots.txt
- No
- Spoofing Risk
- Nooshub has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
- Risk
- Safe
- Recommended Handling
- Depends
Rules and controls
- Robots.txt Snippet
-
# This agent may ignore robots.txt. Use authenticated access controls or network policy when blocking is required.
Relationships
- Operator
- Nooshub Checked 2026-06-23
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.