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: Nei Mongol

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:
IP Type Details Datetime
39.154.12.73 attack
Port Scan
2020-01-02 15:36:52
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 2025-09-15
mnt-by:         MAINT-CN-CMCC
last-modified:  2025-11-18T00:26:27Z
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 2025-09-15
abuse-mailbox:  abuse@chinamobile.com
mnt-by:         APNIC-ABUSE
last-modified:  2025-09-15T02:20:13Z
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.36-SNAPSHOT (WHOIS-AU5)
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 39.154.12.12
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 50767
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;39.154.12.12.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Dec 02 09:01:08 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 12.12.154.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 12.12.154.39.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
37.187.17.58 attackbotsspam
Dec 22 10:27:21 ns381471 sshd[23501]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.187.17.58
Dec 22 10:27:24 ns381471 sshd[23501]: Failed password for invalid user password123456 from 37.187.17.58 port 53597 ssh2
2019-12-22 17:53:23
49.235.104.204 attackbotsspam
Dec 22 10:27:17 localhost sshd\[16542\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.104.204  user=root
Dec 22 10:27:19 localhost sshd\[16542\]: Failed password for root from 49.235.104.204 port 50558 ssh2
Dec 22 10:34:19 localhost sshd\[17208\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.104.204  user=root
2019-12-22 17:41:17
159.65.8.65 attackbotsspam
Dec 21 21:17:05 php1 sshd\[17391\]: Invalid user stacey from 159.65.8.65
Dec 21 21:17:05 php1 sshd\[17391\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.8.65
Dec 21 21:17:07 php1 sshd\[17391\]: Failed password for invalid user stacey from 159.65.8.65 port 40028 ssh2
Dec 21 21:23:22 php1 sshd\[18140\]: Invalid user Tarmo from 159.65.8.65
Dec 21 21:23:22 php1 sshd\[18140\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.8.65
2019-12-22 17:52:14
46.27.165.151 attackspambots
Unauthorized connection attempt detected from IP address 46.27.165.151 to port 445
2019-12-22 17:57:35
163.172.39.84 attackspam
Dec 22 14:17:40 itv-usvr-01 sshd[27930]: Invalid user chen from 163.172.39.84
Dec 22 14:17:40 itv-usvr-01 sshd[27930]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=163.172.39.84
Dec 22 14:17:40 itv-usvr-01 sshd[27930]: Invalid user chen from 163.172.39.84
Dec 22 14:17:41 itv-usvr-01 sshd[27930]: Failed password for invalid user chen from 163.172.39.84 port 38258 ssh2
Dec 22 14:23:58 itv-usvr-01 sshd[28207]: Invalid user server from 163.172.39.84
2019-12-22 17:51:27
101.71.2.137 attackspambots
2019-12-22T09:36:25.287240  sshd[9370]: Invalid user lumb from 101.71.2.137 port 39897
2019-12-22T09:36:25.303454  sshd[9370]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.71.2.137
2019-12-22T09:36:25.287240  sshd[9370]: Invalid user lumb from 101.71.2.137 port 39897
2019-12-22T09:36:26.827251  sshd[9370]: Failed password for invalid user lumb from 101.71.2.137 port 39897 ssh2
2019-12-22T09:41:05.781200  sshd[9477]: Invalid user jking from 101.71.2.137 port 32772
...
2019-12-22 17:51:41
46.38.144.17 attackspambots
Dec 22 11:04:49 webserver postfix/smtpd\[14162\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 22 11:06:18 webserver postfix/smtpd\[14162\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 22 11:07:42 webserver postfix/smtpd\[14161\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 22 11:09:11 webserver postfix/smtpd\[14162\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Dec 22 11:10:42 webserver postfix/smtpd\[14162\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-12-22 18:14:24
167.99.70.96 attackspambots
firewall-block, port(s): 6379/tcp
2019-12-22 18:10:40
194.180.224.152 attackbotsspam
Scanning random ports - tries to find possible vulnerable services
2019-12-22 18:00:49
116.97.54.231 attackspam
Attempt to attack host OS, exploiting network vulnerabilities, on 22-12-2019 09:25:14.
2019-12-22 18:10:58
164.132.197.108 attackbotsspam
Dec 22 10:10:59 server sshd\[8934\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=108.ip-164-132-197.eu  user=root
Dec 22 10:11:01 server sshd\[8934\]: Failed password for root from 164.132.197.108 port 44198 ssh2
Dec 22 10:20:23 server sshd\[11791\]: Invalid user buer from 164.132.197.108
Dec 22 10:20:23 server sshd\[11791\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=108.ip-164-132-197.eu 
Dec 22 10:20:25 server sshd\[11791\]: Failed password for invalid user buer from 164.132.197.108 port 37358 ssh2
...
2019-12-22 17:56:58
138.197.33.113 attack
Dec 22 07:19:34 localhost sshd\[23529\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.33.113  user=root
Dec 22 07:19:36 localhost sshd\[23529\]: Failed password for root from 138.197.33.113 port 50530 ssh2
Dec 22 07:27:07 localhost sshd\[24911\]: Invalid user 123456 from 138.197.33.113 port 55174
2019-12-22 18:03:04
49.234.30.33 attackspam
Invalid user mysql from 49.234.30.33 port 60042
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.30.33
Failed password for invalid user mysql from 49.234.30.33 port 60042 ssh2
Invalid user iy from 49.234.30.33 port 50948
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.30.33
2019-12-22 18:16:51
220.191.160.42 attackbotsspam
Dec 22 10:57:28 dedicated sshd[27018]: Invalid user keimoni from 220.191.160.42 port 46942
2019-12-22 18:07:53
222.186.180.8 attack
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.8  user=root
Failed password for root from 222.186.180.8 port 8456 ssh2
Failed password for root from 222.186.180.8 port 8456 ssh2
Failed password for root from 222.186.180.8 port 8456 ssh2
Failed password for root from 222.186.180.8 port 8456 ssh2
2019-12-22 17:49:25

Recently Reported IPs

39.154.15.110 223.90.39.92 183.253.96.52 1.28.52.213
120.242.148.149 117.188.113.148 116.77.4.172 115.60.130.70
115.57.30.98 115.53.120.42 111.18.244.78 111.16.91.167
212.135.41.129 35.203.211.54 80.94.95.98 178.128.168.52
47.85.1.212 47.236.207.24 192.159.99.95 171.37.94.184