IP Report
116.179.37.240
CHINA UNICOM China169 Backbone · AS4837 · Jinrongjie (Xicheng District), China
Score 60 of 100, in the medium risk band. Bands run 0 to 19 minimal, 20 to 49 low, 50 to 79 medium, 80 to 100 high.
Its risk score of 60/100 is elevated — enough signal to justify friction such as a CAPTCHA or extra verification, though not necessarily an outright block.
Detection signals
Not detected: Tor, VPN, Proxy, Datacenter, Hosting
Summary
116.179.37.240 is crawler infrastructure — automated software that fetches pages, not a person on a browser.
The address is announced by CHINA UNICOM China169 Backbone (AS4837) and geolocates to Jinrongjie (Xicheng District), Beijing, China.
Why this address scores 60
It is identified as crawler infrastructure, which explains automated request patterns without implying abuse.
Together these produce the score of 60/100 shown above.
Observation history
This address has been looked up through Predax 4 times between August 16, 2026 and September 2, 2026.
Each lookup re-evaluates the address against current feeds, so the classification above reflects its most recent check, not a stale record.
Network & location
- ASN
- AS4837
- Country
- China (CN)
- Provider
- CHINA UNICOM China169 Backbone
- Region
- Beijing
- CIDR
- 116.178.98.0/14
- City
- Jinrongjie (Xicheng District)
- Network type
- isp
- PTR
- baiduspider-116-179-37-240.crawl.baidu.com
- First seen
- 8/16/2026, 3:15:02 AM
- Last seen
- 9/2/2026, 5:53:43 AM
- Times seen
- 4
Network context
We have observed 1,303 addresses on CHINA UNICOM China169 Backbone (AS4837); 1% of them carried a threat flag or a notable risk score when last checked.
That is a low share, typical of a general-purpose network whose addresses are mostly unremarkable.
What to do with this
If you run a site and this address showed up
This is declared crawler infrastructure, not a visitor. Whether it is welcome is your call: search crawlers usually earn their bandwidth, while others may not.
If it appears in your block log, check which crawler it is before unblocking — blocking a search engine hurts your own site, blocking a scraper does not.
If you want to decide which crawlers may access your site rather than blocking by user agent, the Predax Security plugin for WordPress enforces per-category crawler policy against published IP ranges like the one this address sits in.
If you found this address in your logs
Hits from this address in your logs are automated fetches. The user agent will usually name the bot; verify identity by IP range rather than trusting the header.
Systematic page-by-page access from it is a crawl, not a user session — exclude it from analytics about human behaviour.
Loading map...
Detection sources
No risk signals triggered
This IP didn't match any of our VPN, proxy, Tor, datacenter, or crawler detectors.