What is MJ12bot?
MJ12bot is a generic crawler operated by Majestic. Use this crawler profile to identify user-agent tokens, operator signals, platform hints, and recommended handling.
MJ12bot
Majestic · Generic crawler
- Version
- v2.0.5
- First seen
- May 20, 2026
- Last seen
- May 25, 2026
- Confidence
- Known user-agent token
What is MJ12bot?
MJ12bot is a generic crawler operated by Majestic. MJ12bot is classified as a generic crawler that may fetch pages for search, SEO, monitoring, or data collection workflows.
MJ12bot matched a known crawler token in the user-agent string, but this page alone does not prove IP ownership.
How to identify MJ12bot in logs
Search server logs for MJ12bot. Matching those tokens is useful for discovery, but IP verification is still recommended before trusting the identity.
Mozilla/5.0 (compatible; MJ12bot/v2.0.5; http://mj12bot.com/)
Use this as a web-crawler lookup reference for identifying how this user-agent presents itself in server logs.
User-agent signals
- Product tokens
- Mozilla/5.0, MJ12bot/v2.0.5
- Documentation
- http://mj12bot.com/
- Contact
- None found
- Platform
- Unknown · Unknown
- Browser profile
- Unknown · Unknown
- Browser-like UA
- Yes
- HTTP library
- Unknown
- Spoof risk
- Medium
Questions answered by this crawler profile
What is MJ12bot?
MJ12bot is classified as a generic crawler that may fetch pages for search, SEO, monitoring, or data collection workflows.
Who operates MJ12bot?
MJ12bot is associated with Majestic.
How do I identify MJ12bot in logs?
Search server logs for MJ12bot. Matching those tokens is useful for discovery, but IP verification is still recommended before trusting the identity.
Should I allow MJ12bot?
Verify IP ownership or behavior before making security decisions because user-agent strings can be spoofed. Monitor crawl rate and paths, then allow normal traffic or rate-limit/block if behavior becomes abusive.
Does MJ12bot respect robots.txt?
Robots.txt compliance cannot be proven from a user-agent string alone. Check the crawler operator documentation and your own logs before assuming behavior.