IP abuse report222.185.3.71

Suspicious Residential IPv4 China AS4134

222.185.3.71 is an IPv4 address located in Nanjing, China. It belongs to a network operated by No.31,Jin-rong Street (AS4134). The address is listed by 2 of the threat-intelligence sources we track and carries a confidence score of 69/100. It has also been reported 1 time(s) by the community.

Last updated Listing sources 2 Community Reports 1 How the score works
Listing sources2
Community Reports1
Distinct Reporters1
Last seen 18 minutes ago

IP Information

ISP / Organization
No.31,Jin-rong Street
ASN
AS4134 CHINANET-BACKBONE
ASN Domain
chinatelecom.cn
IP Range
222.184.0.0/13
Regional Registry
APNIC
Connection Type
Residential
Country
China (CN)
Region / State
Jiangsu
City
Nanjing 2 sources agree
Time Zone
Asia/Shanghai
Abuse contact
anti-spam@chinatelecom.cn The abuse mailbox this network lists with its regional registry. Report traffic from this IP here, with logs and timestamps.

City is an estimate. The country is reliable; the city varies by provider.

Approximate location

City level
Nanjing Jiangsu, China
Coordinates
32.06, 118.76
Network
AS4134 No.31,Jin-rong Street
Open on the threat map

The point is the city centre given by IP geolocation databases, not a street address. The circle shows the area of uncertainty.

Network Neighbourhood

222.185.3.0/24

No other address in 222.185.3.0/24 is listed.

An address is not guiltier for having a few listed neighbours, which is why this stays out of the confidence score entirely while the block is mostly clean. It contributes at most 20 points, and only once a substantial share of the block is listed — that ceiling is deliberate: neighbours alone can raise an address to "low" and no further.

Threat Evidence

Last 30 days: how many feeds listed this address each day, and the community reports filed.

Blocklist feeds Community reports

Blacklist Matches

2

In our pool since: 2026-11-16 06:17 (3 days ago) · Last confirmed: 2026-11-20 03:19

Attack Source 1
SourceScopeFirst seenConfirmed
Data-Shield IPv4 Blocklist Single address 2026-11-17 08:48 2026-11-20 03:1918 minutes ago
Malicious Activity 1
SourceScopeFirst seenConfirmed
Malicious IP (romainmarcoux) Aggregator Single address 2026-11-19 09:48 2026-11-20 03:1919 minutes ago

“Confirmed” is the moment the address was still on that source at its most recent fetch — the feeds are replaced wholesale on every refresh. Per-source “first seen” only began being recorded on 30 August 2026, so for listings older than that this column shows the start of record-keeping. The address-level history is the “in our pool since” value above.

IP-DB Sensor · free honeypot

Catch addresses like this on your own server

Sensor opens realistic decoy services — FortiGate, GlobalProtect, Exchange, NetScaler and more — on your server's unused ports. Every address that touches them is logged with evidence, and your firewall, fail2ban and Shield pull the same list to block it.

  • Realistic decoys for VPN gateways, mail, web panels and databases
  • Names exploit attempts by their CVE signature
  • One-command install; runs unprivileged and never touches your real services

While a Sensor reports, your daily API quota rises to 30,000 lookups.

root@web-01 — ipdb-sensor DEMO
● ipdb-sensor.serviceactive (running)
4hits
4decoys
1blocked
  1. 14:02:07 ssh:22 222.185.3.71 login attempt root / ••••••
  2. 14:02:10 globalprotect:443 222.185.3.71 exploit attempt CVE-2024-3400
  3. 14:02:13 owa:4443 222.185.3.71 password spray Exchange OWA
  4. 14:02:16 netscaler:8443 222.185.3.71 Citrix Bleed scan CVE-2023-4966
  5. 14:02:20 ✓ evidence logged → added to your blocklist
Sample output — if this address probed your server

Community Reports 1

Report This IP

Who reported this address, when, and on what grounds.

0Last 24 Hours
1Last 7 Days
1Last 30 Days
1Last 90 Days
  1. nak Registered member
    2 days ago 2026-11-17 15:40Reported from: Japan (JP)
    Reason: Vulnerability Scanning
    Observed by PHP honeypot (static responder; no code executed). 1 requests on 2026-11-17 06:39:45–06:39:45 UTC (0 s). Automated LLM API endpoint scanner. Attack attempts: - LLM API endpoint probing: GET /api/tags -> enumerates available model tags or API capabilities Signatures: llm-api-probe

Reporters' IP addresses are never published — only the country they reported from.

Listing History

1
Added to the pool
3 days ago
2026-11-16 06:22

The pool is a live picture: an address listed today leaves it when the sources drop it. This record outlives that removal — “listed on 12 August, delisted on 3 September” is truer than either a permanent accusation or a blank page. Events are kept for 400 days.

Frequently asked questions about 222.185.3.71

Is 222.185.3.71 safe?

222.185.3.71 scores 69/100 from several independent signals (2 sources, 1 community report). Rate-limit or challenge its traffic and review your logs for it.

Who owns 222.185.3.71?

222.185.3.71 is announced by AS4134 and operated by No.31,Jin-rong Street. It sits in the 222.184.0.0/13 block registered with APNIC.

Where is 222.185.3.71 located?

Geolocation places 222.185.3.71 in Nanjing, China. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.

Is 222.185.3.71 on a blacklist?

Yes. 222.185.3.71 is currently listed by 2 threat sources: Malicious IP (romainmarcoux), Data-Shield IPv4 Blocklist.

How do I report abuse from 222.185.3.71?

Send your log lines to the network's abuse contact, anti-spam@chinatelecom.cn, and file a report on IP-DB so others can see it too.

Run this check via the API

The same score and evidence are available as JSON, free with an API key.

API documentation →
curl -H "Key: YOUR_API_KEY" https://ip-db.com/api/v1/check/222.185.3.71

Guides for this IP