Overview
MJ12Bot is a search crawler from Majestic used for search indexing, URL discovery, page rendering, result freshness, and search-quality checks.
Its primary user-agent pattern is MJ12bot; a representative HTTP user-agent is Mozilla/5.0 (compatible; MJ12bot/v1.4.8; http://mj12bot.com/).
MJ12Bot is Verified from current authoritative identity documentation reviewed on 2026-08-07. The identity type is Official Documented.
MJ12Bot is marked as respecting robots.txt directives for crawler access control.
MJ12Bot should be reviewed against site policy, source evidence, crawl rate, and requested paths before a permanent allow or block rule is created.
Identity
- User-Agent Pattern
-
MJ12bot - HTTP Agent Examples
-
Mozilla/5.0 (compatible; MJ12bot/v1.4.8; http://mj12bot.com/) - Robots Token
- MJ12bot
- Identity Type
- Officially documented
- Evidence Method
- Match `MJ12bot` to the current operator documentation and corroborate the request with operator-controlled verification signals where available; User-Agent strings alone can be spoofed.
Classification
- Type
- Search
- Kind
- Crawler
- Family
- Majestic
- Purpose
- Indexing
Behavior and handling
- Common Use
- MJ12Bot is used for search indexing, URL discovery, page rendering, result freshness, and search-quality checks.
- Detection Notes
- MJ12Bot traffic is primarily detected by the `MJ12bot` user-agent pattern; a representative HTTP user-agent is `Mozilla/5.0 (compatible; MJ12bot/v1.4.8; http://mj12bot.com/)`. Compare source IPs, reverse DNS, request paths, and crawl cadence with Majestic infrastructure before trusting the traffic.
- Respects robots.txt
- Yes
- Spoofing Risk
- MJ12Bot has medium spoofing risk because the user-agent can be copied, even when the bot has strong source or documentation support.
- Risk
- Neutral
- Recommended Handling
- Depends
Rules and controls
- Robots.txt Snippet
-
User-agent: MJ12bot Disallow: /
Relationships
- Operator
- Majestic 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.