Bot IP: 52.167.144.229
Bot Name: Bingbot
Bingbot is the primary web crawler used by Microsoft Bing to discover and index web content for its search engine results.
Likely legitimate
Track-A-Bot Trust Score: 87/100
87
score
0255075100
Why Track-A-Bot rated this IP (tap to expand)
Identity
- β Marked as bot traffic
- β Bot name present
- β User-agent matches bot name
- β User-agent includes identity link/email
Hostname
- β Hostname observed
- βΉοΈ Hostname does not resemble bot name
- βΉοΈ Hostname status not verified
- β No hostname mismatch flags
Behavior
- βΉοΈ No /robots.txt request observed
- β No referrer (typical crawler behavior)
- β Mostly 200/304 responses
- π Visits: 154
- β±οΈ Age: 15219h
Penalties
- β No major spoof pattern
- β No fingerprint fields
- β Cookies not enabled
- β No connection type
Total visits: 154 First seen: Mar 18th, 2024 4:17 PM Last seen: Dec 12th, 2025 7:23 PM
Known Hostname(s)
msnbot-52-167-144-229.search.msn.com
Known User Agent(s)
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm) Chrome/116.0.1938.76 Safari/537.36Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36 Edg/112.0.1722.68
Known Accepted Encoding(s)
gzip, deflate, br
Common User-Agent Tokens
These are identifiers found inside user-agent strings we observed for bingbot.
Token
Seen
First seen
Last seen
bingbot/2.0
40,280
3/17/24
12/12/25
bingbot/2.0
40,280 seen
bingbot/2.0
40,280 seen
First
3/17/24
Last
12/12/25
mobile/15e148
13
1/26/25
12/12/25
mobile/15e148
13 seen
mobile/15e148
13 seen
First
1/26/25
Last
12/12/25
17_1
3
2/26/25
12/12/25
17_1
3 seen
17_1
3 seen
First
2/26/25
Last
12/12/25
17_2
3
1/26/25
12/12/25
17_2
3 seen
17_2
3 seen
First
1/26/25
Last
12/12/25
microsoftpreview/2.0
3
12/12/25
12/12/25
microsoftpreview/2.0
3 seen
microsoftpreview/2.0
3 seen
First
12/12/25
Last
12/12/25
unknown
3
12/12/25
12/12/25
unknown
3 seen
unknown
3 seen
First
12/12/25
Last
12/12/25
10_15_7
2
5/7/25
12/12/25
10_15_7
2 seen
10_15_7
2 seen
First
5/7/25
Last
12/12/25
17_0
2
4/10/25
4/10/25
17_0
2 seen
17_0
2 seen
First
4/10/25
Last
4/10/25
17_3
2
12/12/25
12/12/25
17_3
2 seen
17_3
2 seen
First
12/12/25
Last
12/12/25
18_1_1
2
4/29/25
5/2/25
18_1_1
2 seen
18_1_1
2 seen
First
4/29/25
Last
5/2/25
adidxbot/2.0
2
10/21/25
10/22/25
adidxbot/2.0
2 seen
adidxbot/2.0
2 seen
First
10/21/25
Last
10/22/25
crios/131.0.6778.73
2
4/29/25
4/29/25
crios/131.0.6778.73
2 seen
crios/131.0.6778.73
2 seen
First
4/29/25
Last
4/29/25
gecko/20100101
2
2/18/25
12/12/25
gecko/20100101
2 seen
gecko/20100101
2 seen
First
2/18/25
Last
12/12/25
unique/97.7.7286.70
2
1/27/25
12/12/25
unique/97.7.7286.70
2 seen
unique/97.7.7286.70
2 seen
First
1/27/25
Last
12/12/25
17_5_1
1
4/28/25
4/28/25
17_5_1
1 seen
17_5_1
1 seen
First
4/28/25
Last
4/28/25
avastsecurebrowser/5.3.1
1
12/12/25
12/12/25
avastsecurebrowser/5.3.1
1 seen
avastsecurebrowser/5.3.1
1 seen
First
12/12/25
Last
12/12/25
build/mmb29p
1
12/11/25
12/11/25
build/mmb29p
1 seen
build/mmb29p
1 seen
First
12/11/25
Last
12/11/25
crios/122.0.6261.62
1
12/12/25
12/12/25
crios/122.0.6261.62
1 seen
crios/122.0.6261.62
1 seen
First
12/12/25
Last
12/12/25
edga/121.0.0.0
1
2/20/25
2/20/25
edga/121.0.0.0
1 seen
edga/121.0.0.0
1 seen
First
2/20/25
Last
2/20/25
edgios/116.0.1938.56
1
3/1/25
3/1/25
edgios/116.0.1938.56
1 seen
edgios/116.0.1938.56
1 seen
First
3/1/25
Last
3/1/25
edgios/116.0.1938.79
1
4/10/25
4/10/25
edgios/116.0.1938.79
1 seen
edgios/116.0.1938.79
1 seen
First
4/10/25
Last
4/10/25
edgios/118.0.2088.68
1
2/26/25
2/26/25
edgios/118.0.2088.68
1 seen
edgios/118.0.2088.68
1 seen
First
2/26/25
Last
2/26/25
edgios/119.0.2151.78
1
12/12/25
12/12/25
edgios/119.0.2151.78
1 seen
edgios/119.0.2151.78
1 seen
First
12/12/25
Last
12/12/25
edgios/120.0.2210.126
1
12/12/25
12/12/25
edgios/120.0.2210.126
1 seen
edgios/120.0.2210.126
1 seen
First
12/12/25
Last
12/12/25
edgios/120.0.2210.141
1
2/25/25
2/25/25
edgios/120.0.2210.141
1 seen
edgios/120.0.2210.141
1 seen
First
2/25/25
Last
2/25/25
edgios/120.0.2210.86
1
1/26/25
1/26/25
edgios/120.0.2210.86
1 seen
edgios/120.0.2210.86
1 seen
First
1/26/25
Last
1/26/25
edgios/121.0.2277.107
1
12/12/25
12/12/25
edgios/121.0.2277.107
1 seen
edgios/121.0.2277.107
1 seen
First
12/12/25
Last
12/12/25
trailer/93.3.3516.28
1
4/16/25
4/16/25
trailer/93.3.3516.28
1 seen
trailer/93.3.3516.28
1 seen
First
4/16/25
Last
4/16/25
viewer/99.9.9009.89
1
12/12/25
12/12/25
viewer/99.9.9009.89
1 seen
viewer/99.9.9009.89
1 seen
First
12/12/25
Last
12/12/25
Identity Links
These are URLs we observed in association with bingbot (often used as an identity, help, or policy link).
URL
Seen
First seen
Last seen
First
3/17/24
Last
12/12/25
First
12/12/25
Last
12/12/25
Bot FAQ for this IP
Why is bingbot visiting my website?
Bingbot is visiting your website to crawl and index your pages for Microsoft's Bing search engine. This helps Bing keep its search results up to date and relevant. According to your logs, the bot with IP 52.167.144.229 accessed various pages, including your sitemap and several state-specific URLs, all at the same timestamp. The user agent and reverse DNS (msnbot-52-167-144-229.search.msn.com) match Bing's documented patterns. If you want to control what bingbot can access, update your robots.txt file. You can also monitor its activity for unusual patterns and set rate limits if needed.
What does bingbot do?
Bingbot is an automated crawler used by Bing to discover and index web content. It systematically visits your site's pages, following links and reading content to update Bing's search listings. In your case, bingbot accessed your sitemap and multiple content pages, which is typical crawler behavior. You can verify its identity by checking the user agent string and performing reverse DNS lookups, as you have done. To manage bingbot's access, use robots.txt directives, and consider monitoring your server logs for crawling frequency.
Is bingbot safe?
Bingbot is generally considered safe and is a legitimate crawler operated by Microsoft. The IP address 52.167.144.229 resolves to a hostname consistent with Bing's infrastructure, and the user agent matches Bing's official documentation. However, always verify by checking the reverse DNS and user agent, as you have done. To protect your site, you can: 1) Use robots.txt to control access, 2) Set reasonable rate limits to prevent server overload, 3) Monitor for unusual or excessive requests, and 4) Use a Web Application Firewall (WAF) for added security. If you notice suspicious behavior, investigate further before taking action.
This page provides a detailed lookup for the bot with the IP address of 52.167.144.229, based on real-world traffic observed across websites using Track-A-Bot software. Use this information to verify whether activity from this IP belongs to a legitimate search engine crawler, or to analyze bot behavior on your website.