Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: Qujing

Region: Yunnan

Country: China

Internet Service Provider: China Mobile

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
% [whois.apnic.net]
% Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html

% Information related to '39.128.0.0 - 39.191.255.255'

% Abuse contact for '39.128.0.0 - 39.191.255.255' is 'abuse@chinamobile.com'

inetnum:        39.128.0.0 - 39.191.255.255
netname:        CMNET
descr:          China Mobile Communications Corporation
descr:          Mobile Communications Network Operator in China
descr:          Internet Service Provider in China
country:        CN
org:            ORG-CM1-AP
admin-c:        ct74-AP
tech-c:         HL1318-AP
abuse-c:        AC2006-AP
status:         ALLOCATED PORTABLE
remarks:        service provider
remarks:        --------------------------------------------------------
remarks:        To report network abuse, please contact mnt-irt
remarks:        For troubleshooting, please contact tech-c and admin-c
remarks:        Report invalid contact via www.apnic.net/invalidcontact
remarks:        --------------------------------------------------------
mnt-by:         APNIC-HM
mnt-lower:      MAINT-CN-CMCC
mnt-routes:     MAINT-CN-CMCC
mnt-irt:        IRT-CHINAMOBILE-CN
last-modified:  2020-10-20T00:58:36Z
source:         APNIC

irt:            IRT-CHINAMOBILE-CN
address:        China Mobile Communications Corporation
address:        29, Jinrong Ave., Xicheng District, Beijing, 100032
e-mail:         abuse@chinamobile.com
abuse-mailbox:  abuse@chinamobile.com
admin-c:        CT74-AP
tech-c:         CT74-AP
auth:           # Filtered
remarks:        abuse@chinamobile.com was validated on 2026-03-23
mnt-by:         MAINT-CN-CMCC
last-modified:  2026-03-23T00:47:53Z
source:         APNIC

organisation:   ORG-CM1-AP
org-name:       China Mobile
org-type:       LIR
country:        CN
address:        29, Jinrong Ave.
phone:          +86-10-5268-6688
fax-no:         +86-10-5261-6187
e-mail:         hostmaster@chinamobile.com
mnt-ref:        APNIC-HM
mnt-by:         APNIC-HM
last-modified:  2023-09-05T02:14:48Z
source:         APNIC

role:           ABUSE CHINAMOBILECN
country:        ZZ
address:        China Mobile Communications Corporation
address:        29, Jinrong Ave., Xicheng District, Beijing, 100032
phone:          +000000000
e-mail:         abuse@chinamobile.com
admin-c:        CT74-AP
tech-c:         CT74-AP
nic-hdl:        AC2006-AP
remarks:        Generated from irt object IRT-CHINAMOBILE-CN
remarks:        abuse@chinamobile.com was validated on 2026-03-23
abuse-mailbox:  abuse@chinamobile.com
mnt-by:         APNIC-ABUSE
last-modified:  2026-03-23T00:48:02Z
source:         APNIC

role:           chinamobile tech
address:        29, Jinrong Ave.,Xicheng district
address:        Beijing
country:        CN
phone:          +86 5268 6688
fax-no:         +86 5261 6187
e-mail:         hostmaster@chinamobile.com
admin-c:        HL1318-AP
tech-c:         HL1318-AP
nic-hdl:        ct74-AP
notify:         hostmaster@chinamobile.com
mnt-by:         MAINT-cn-cmcc
abuse-mailbox:  abuse@chinamobile.com
last-modified:  2016-11-29T09:37:27Z
source:         APNIC

person:         haijun li
nic-hdl:        HL1318-AP
e-mail:         hostmaster@chinamobile.com
address:        29,Jinrong Ave, Xicheng district,beijing,100032
phone:          +86 1052686688
fax-no:         +86 10 52616187
country:        CN
mnt-by:         MAINT-CN-CMCC
abuse-mailbox:  abuse@chinamobile.com
last-modified:  2016-11-29T09:38:38Z
source:         APNIC

% This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-AU4)
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 39.128.41.74
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17935
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;39.128.41.74.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2026060602 1800 900 604800 86400

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jun 07 08:00:41 CST 2026
;; MSG SIZE  rcvd: 105
Host info
Host 74.41.128.39.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 74.41.128.39.in-addr.arpa: SERVFAIL

Related IP info:
Related comments:
IP Type Details Datetime
206.189.239.103 attackbots
May 13 13:30:32 game-panel sshd[21026]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.239.103
May 13 13:30:33 game-panel sshd[21026]: Failed password for invalid user ftp2 from 206.189.239.103 port 33492 ssh2
May 13 13:34:01 game-panel sshd[21196]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.239.103
2020-05-13 21:44:52
106.54.141.65 attackspambots
2020-05-13T12:58:57.091793abusebot-7.cloudsearch.cf sshd[8522]: Invalid user deploy from 106.54.141.65 port 40986
2020-05-13T12:58:57.102341abusebot-7.cloudsearch.cf sshd[8522]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.141.65
2020-05-13T12:58:57.091793abusebot-7.cloudsearch.cf sshd[8522]: Invalid user deploy from 106.54.141.65 port 40986
2020-05-13T12:58:58.544294abusebot-7.cloudsearch.cf sshd[8522]: Failed password for invalid user deploy from 106.54.141.65 port 40986 ssh2
2020-05-13T13:03:41.794592abusebot-7.cloudsearch.cf sshd[8898]: Invalid user teste from 106.54.141.65 port 43832
2020-05-13T13:03:41.804314abusebot-7.cloudsearch.cf sshd[8898]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.141.65
2020-05-13T13:03:41.794592abusebot-7.cloudsearch.cf sshd[8898]: Invalid user teste from 106.54.141.65 port 43832
2020-05-13T13:03:43.897748abusebot-7.cloudsearch.cf sshd[8898]: Failed pass
...
2020-05-13 21:31:05
180.214.236.138 attack
Port Scan
2020-05-13 21:57:17
134.122.14.226 attackspam
Fail2Ban - SSH Bruteforce Attempt
2020-05-13 21:27:52
103.48.192.203 attackbotsspam
103.48.192.203 - - \[13/May/2020:14:38:13 +0200\] "POST /wp-login.php HTTP/1.0" 200 5508 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
103.48.192.203 - - \[13/May/2020:14:38:16 +0200\] "POST /wp-login.php HTTP/1.0" 200 5506 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
103.48.192.203 - - \[13/May/2020:14:38:18 +0200\] "POST /xmlrpc.php HTTP/1.0" 200 736 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2020-05-13 21:56:07
117.50.65.85 attackspam
May 13 07:16:52 server1 sshd\[23115\]: Invalid user telcel3 from 117.50.65.85
May 13 07:16:52 server1 sshd\[23115\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.50.65.85 
May 13 07:16:54 server1 sshd\[23115\]: Failed password for invalid user telcel3 from 117.50.65.85 port 36926 ssh2
May 13 07:19:17 server1 sshd\[23746\]: Invalid user hance from 117.50.65.85
May 13 07:19:17 server1 sshd\[23746\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.50.65.85 
...
2020-05-13 21:28:18
2.135.39.134 attack
May 13 12:38:53 ssh2 sshd[20445]: Connection from 2.135.39.134 port 53358 on 192.240.101.3 port 22
May 13 12:38:55 ssh2 sshd[20445]: Invalid user admina from 2.135.39.134 port 53358
May 13 12:38:55 ssh2 sshd[20445]: Failed password for invalid user admina from 2.135.39.134 port 53358 ssh2
...
2020-05-13 21:17:35
222.186.175.216 attack
May 13 15:21:15 pve1 sshd[17319]: Failed password for root from 222.186.175.216 port 26612 ssh2
May 13 15:21:20 pve1 sshd[17319]: Failed password for root from 222.186.175.216 port 26612 ssh2
...
2020-05-13 21:23:20
23.254.215.210 attackspambots
Port scan - 12 hits (greater than 5)
2020-05-13 21:54:52
106.53.2.215 attack
May 13 15:21:53 plex sshd[14991]: Invalid user saima from 106.53.2.215 port 45842
2020-05-13 21:24:47
212.237.50.122 attackbots
May 13 15:12:42 vps639187 sshd\[23468\]: Invalid user design from 212.237.50.122 port 34058
May 13 15:12:42 vps639187 sshd\[23468\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.237.50.122
May 13 15:12:44 vps639187 sshd\[23468\]: Failed password for invalid user design from 212.237.50.122 port 34058 ssh2
...
2020-05-13 21:24:20
35.202.157.96 attackbots
WordPress wp-login brute force :: 35.202.157.96 0.332 - [13/May/2020:12:38:58  0000] [censored_1] "POST /wp-login.php HTTP/1.1" 200 1837 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" "HTTP/1.1"
2020-05-13 21:15:22
152.136.22.63 attack
May 13 14:38:46 vpn01 sshd[26365]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.136.22.63
May 13 14:38:48 vpn01 sshd[26365]: Failed password for invalid user anu from 152.136.22.63 port 42356 ssh2
...
2020-05-13 21:24:34
124.156.105.251 attackspam
May 13 15:08:13 plex sshd[14198]: Invalid user hadoop from 124.156.105.251 port 48350
2020-05-13 21:34:00
14.40.112.44 attack
May 13 14:27:02 ms-srv sshd[51834]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.40.112.44
May 13 14:27:04 ms-srv sshd[51834]: Failed password for invalid user a1 from 14.40.112.44 port 38186 ssh2
2020-05-13 21:43:50

Recently Reported IPs

36.143.128.184 223.88.174.62 183.197.76.244 135.237.127.112
119.162.111.220 117.139.32.19 115.56.117.17 112.18.177.97
103.116.121.62 101.26.28.116 107.174.189.2 52.91.101.47
3.87.196.32 20.169.107.4 98.93.104.4 8.209.228.11
54.163.219.20 50.240.165.101 40.124.186.101 216.180.246.141