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: unknown

Region: unknown

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-09-30
mnt-by:         MAINT-CN-CMCC
last-modified:  2026-09-30T02:37:06Z
source:         APNIC

organisation:   ORG-CM1-AP
org-name:       China Mobile Communications Group Co., Ltd
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:  2026-07-31T13:46:41Z
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-09-30
abuse-mailbox:  abuse@chinamobile.com
mnt-by:         APNIC-ABUSE
last-modified:  2026-09-30T02:37:41Z
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-US2)
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 39.163.142.230
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 33117
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;39.163.142.230.			IN	A

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

;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Oct 09 19:02:01 CST 2026
;; MSG SIZE  rcvd: 107
Host info
Host 230.142.163.39.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 230.142.163.39.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
180.183.225.52 attackspambots
Unauthorised access (Aug  8) SRC=180.183.225.52 LEN=52 TTL=114 ID=28544 DF TCP DPT=445 WINDOW=8192 SYN
2019-08-08 13:12:15
51.89.22.106 attack
Aug  8 06:01:31 microserver sshd[34790]: Invalid user yar from 51.89.22.106 port 35346
Aug  8 06:01:31 microserver sshd[34790]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.89.22.106
Aug  8 06:01:33 microserver sshd[34790]: Failed password for invalid user yar from 51.89.22.106 port 35346 ssh2
Aug  8 06:07:15 microserver sshd[35504]: Invalid user odoo from 51.89.22.106 port 58790
Aug  8 06:07:15 microserver sshd[35504]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.89.22.106
Aug  8 06:18:24 microserver sshd[36986]: Invalid user weaver from 51.89.22.106 port 48936
Aug  8 06:18:24 microserver sshd[36986]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.89.22.106
Aug  8 06:18:26 microserver sshd[36986]: Failed password for invalid user weaver from 51.89.22.106 port 48936 ssh2
Aug  8 06:24:11 microserver sshd[37708]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=
2019-08-08 12:45:02
153.36.138.52 attackbotsspam
Aug  8 02:22:55   DDOS Attack: SRC=153.36.138.52 DST=[Masked] LEN=40 TOS=0x00 PREC=0x00 TTL=47  DF PROTO=TCP SPT=5921 DPT=80 WINDOW=0 RES=0x00 RST URGP=0
2019-08-08 13:23:30
91.134.240.73 attackbots
Automated report - ssh fail2ban:
Aug 8 06:19:48 wrong password, user=vlc, port=50018, ssh2
Aug 8 06:54:36 authentication failure 
Aug 8 06:54:38 wrong password, user=ts3, port=52454, ssh2
2019-08-08 13:04:31
45.227.255.223 attackspambots
Multi Port-Scan
2019-08-08 12:54:07
134.209.154.143 attack
Aug  8 06:40:14 server sshd\[7484\]: User root from 134.209.154.143 not allowed because listed in DenyUsers
Aug  8 06:40:14 server sshd\[7484\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.154.143  user=root
Aug  8 06:40:16 server sshd\[7484\]: Failed password for invalid user root from 134.209.154.143 port 34982 ssh2
Aug  8 06:45:21 server sshd\[31253\]: Invalid user iam from 134.209.154.143 port 58756
Aug  8 06:45:21 server sshd\[31253\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.154.143
2019-08-08 12:39:42
188.166.246.46 attack
Aug  8 02:23:09 MK-Soft-VM7 sshd\[14789\]: Invalid user whisper from 188.166.246.46 port 46066
Aug  8 02:23:09 MK-Soft-VM7 sshd\[14789\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.246.46
Aug  8 02:23:11 MK-Soft-VM7 sshd\[14789\]: Failed password for invalid user whisper from 188.166.246.46 port 46066 ssh2
...
2019-08-08 13:15:02
192.169.216.126 attack
POP
2019-08-08 13:16:44
122.165.155.19 attackspam
SSH bruteforce (Triggered fail2ban)
2019-08-08 13:25:43
105.247.157.59 attack
SSH Bruteforce
2019-08-08 13:22:07
187.101.186.61 attack
Aug  8 06:31:02 cp sshd[26757]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.101.186.61
2019-08-08 13:03:19
185.220.101.3 attackbotsspam
Aug  8 06:28:44 vpn01 sshd\[12036\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.220.101.3  user=root
Aug  8 06:28:46 vpn01 sshd\[12036\]: Failed password for root from 185.220.101.3 port 40277 ssh2
Aug  8 06:28:49 vpn01 sshd\[12036\]: Failed password for root from 185.220.101.3 port 40277 ssh2
2019-08-08 12:32:15
151.80.61.103 attackbots
Aug  8 06:50:22 microserver sshd[41553]: Invalid user miusuario from 151.80.61.103 port 39478
Aug  8 06:50:22 microserver sshd[41553]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=151.80.61.103
Aug  8 06:50:24 microserver sshd[41553]: Failed password for invalid user miusuario from 151.80.61.103 port 39478 ssh2
Aug  8 06:54:26 microserver sshd[41764]: Invalid user postgres from 151.80.61.103 port 33654
Aug  8 06:54:26 microserver sshd[41764]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=151.80.61.103
Aug  8 07:06:17 microserver sshd[43630]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=151.80.61.103  user=root
Aug  8 07:06:19 microserver sshd[43630]: Failed password for root from 151.80.61.103 port 43924 ssh2
Aug  8 07:10:24 microserver sshd[44272]: Invalid user plex from 151.80.61.103 port 38034
Aug  8 07:10:24 microserver sshd[44272]: pam_unix(sshd:auth): authentication failure; lo
2019-08-08 13:25:18
169.197.108.6 attackbotsspam
Aug  8 02:23:21   TCP Attack: SRC=169.197.108.6 DST=[Masked] LEN=258 TOS=0x00 PREC=0x00 TTL=57  DF PROTO=TCP SPT=57502 DPT=80 WINDOW=229 RES=0x00 ACK PSH URGP=0
2019-08-08 13:09:43
175.140.220.129 attackspam
Looking for resource vulnerabilities
2019-08-08 13:10:00

Recently Reported IPs

20.14.94.5 61.188.171.3 40.119.45.136 121.199.173.217
120.242.141.199 52.73.187.98 61.52.89.44 58.22.94.152
39.162.74.38 36.36.184.69 183.199.187.3 183.199.181.104
123.5.211.90 120.243.76.65 119.2.187.187 116.171.165.145
74.7.243.201 74.7.228.22 123.147.237.135 20.40.223.141