City: Fuzhou
Region: Fujian
Country: China
Internet Service Provider: China Mobile
Hostname: unknown
Organization: unknown
Usage Type: unknown
% [whois.apnic.net]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html
% Information related to '112.0.0.0 - 112.63.255.255'
% Abuse contact for '112.0.0.0 - 112.63.255.255' is 'abuse@chinamobile.com'
inetnum: 112.0.0.0 - 112.63.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
status: ALLOCATED PORTABLE
abuse-c: AC2006-AP
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: 2026-05-22T03:50:58Z
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-08-13T06:25:29Z
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-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
% Information related to '112.48.0.0/14AS9808'
route: 112.48.0.0/14
descr: China Mobile communications corporation
origin: AS9808
mnt-by: MAINT-CN-CMCC
last-modified: 2009-10-27T08:12:05Z
source: APNIC
% This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-AU4); <<>> DiG 9.10.3-P4-Ubuntu <<>> 112.49.106.84
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4637
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;112.49.106.84. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026090600 1800 900 604800 86400
;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Sep 06 15:02:53 CST 2026
;; MSG SIZE rcvd: 106Host 84.106.49.112.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 84.106.49.112.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 222.242.223.75 | attackbotsspam | May 27 15:14:48 home sshd[14403]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.242.223.75 May 27 15:14:50 home sshd[14403]: Failed password for invalid user wking from 222.242.223.75 port 40545 ssh2 May 27 15:18:08 home sshd[14725]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.242.223.75 ... |
2020-05-27 23:42:39 |
| 2.228.87.194 | attackbotsspam | May 27 13:45:45 ns382633 sshd\[3220\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=2.228.87.194 user=root May 27 13:45:47 ns382633 sshd\[3220\]: Failed password for root from 2.228.87.194 port 41421 ssh2 May 27 13:53:37 ns382633 sshd\[4535\]: Invalid user test from 2.228.87.194 port 38915 May 27 13:53:37 ns382633 sshd\[4535\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=2.228.87.194 May 27 13:53:39 ns382633 sshd\[4535\]: Failed password for invalid user test from 2.228.87.194 port 38915 ssh2 |
2020-05-27 23:15:00 |
| 80.211.13.167 | attackspam | May 27 16:38:09 ArkNodeAT sshd\[9177\]: Invalid user deb from 80.211.13.167 May 27 16:38:09 ArkNodeAT sshd\[9177\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.211.13.167 May 27 16:38:12 ArkNodeAT sshd\[9177\]: Failed password for invalid user deb from 80.211.13.167 port 36542 ssh2 |
2020-05-27 23:29:58 |
| 212.145.192.205 | attackspambots | May 27 12:43:47 sshgateway sshd\[3278\]: Invalid user lkihara from 212.145.192.205 May 27 12:43:47 sshgateway sshd\[3278\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.145.192.205 May 27 12:43:49 sshgateway sshd\[3278\]: Failed password for invalid user lkihara from 212.145.192.205 port 46628 ssh2 |
2020-05-27 23:24:37 |
| 121.43.163.22 | attack | 20 attempts against mh-ssh on grass |
2020-05-27 23:42:12 |
| 212.64.19.237 | attackbots | SSH Brute-Forcing (server1) |
2020-05-27 23:31:43 |
| 187.141.71.27 | attackspambots | sshd: Failed password for invalid user .... from 187.141.71.27 port 49134 ssh2 (8 attempts) |
2020-05-27 23:15:46 |
| 222.186.175.23 | attack | May 27 17:15:21 minden010 sshd[8886]: Failed password for root from 222.186.175.23 port 55265 ssh2 May 27 17:15:24 minden010 sshd[8886]: Failed password for root from 222.186.175.23 port 55265 ssh2 May 27 17:15:26 minden010 sshd[8886]: Failed password for root from 222.186.175.23 port 55265 ssh2 ... |
2020-05-27 23:17:40 |
| 142.93.56.12 | attack | May 27 20:34:34 webhost01 sshd[410]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.56.12 May 27 20:34:36 webhost01 sshd[410]: Failed password for invalid user ekp from 142.93.56.12 port 57434 ssh2 ... |
2020-05-27 23:22:46 |
| 36.225.69.80 | attackspam | TW_MAINT-TW-TWNIC_<177>1590588341 [1:2403330:57575] ET CINS Active Threat Intelligence Poor Reputation IP TCP group 16 [Classification: Misc Attack] [Priority: 2]: |
2020-05-27 23:33:52 |
| 83.241.232.51 | attackbotsspam | May 27 13:40:54 ns382633 sshd\[2334\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.241.232.51 user=root May 27 13:40:56 ns382633 sshd\[2334\]: Failed password for root from 83.241.232.51 port 59538 ssh2 May 27 13:49:47 ns382633 sshd\[3669\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.241.232.51 user=root May 27 13:49:49 ns382633 sshd\[3669\]: Failed password for root from 83.241.232.51 port 50610 ssh2 May 27 13:53:01 ns382633 sshd\[4437\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.241.232.51 user=root |
2020-05-27 23:43:56 |
| 112.85.42.174 | attack | 2020-05-27T15:20:41.219041shield sshd\[1373\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.174 user=root 2020-05-27T15:20:42.786856shield sshd\[1373\]: Failed password for root from 112.85.42.174 port 30464 ssh2 2020-05-27T15:20:46.123329shield sshd\[1373\]: Failed password for root from 112.85.42.174 port 30464 ssh2 2020-05-27T15:20:49.215481shield sshd\[1373\]: Failed password for root from 112.85.42.174 port 30464 ssh2 2020-05-27T15:20:52.743876shield sshd\[1373\]: Failed password for root from 112.85.42.174 port 30464 ssh2 |
2020-05-27 23:21:18 |
| 24.16.139.106 | attack | 2020-05-27T15:03:15.522078abusebot-3.cloudsearch.cf sshd[24785]: Invalid user usuario from 24.16.139.106 port 58552 2020-05-27T15:03:15.529607abusebot-3.cloudsearch.cf sshd[24785]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=24.16.139.106 2020-05-27T15:03:15.522078abusebot-3.cloudsearch.cf sshd[24785]: Invalid user usuario from 24.16.139.106 port 58552 2020-05-27T15:03:17.500530abusebot-3.cloudsearch.cf sshd[24785]: Failed password for invalid user usuario from 24.16.139.106 port 58552 ssh2 2020-05-27T15:07:19.348429abusebot-3.cloudsearch.cf sshd[24988]: Invalid user lmwangi from 24.16.139.106 port 35762 2020-05-27T15:07:19.358135abusebot-3.cloudsearch.cf sshd[24988]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=24.16.139.106 2020-05-27T15:07:19.348429abusebot-3.cloudsearch.cf sshd[24988]: Invalid user lmwangi from 24.16.139.106 port 35762 2020-05-27T15:07:21.161785abusebot-3.cloudsearch.cf sshd[2498 ... |
2020-05-27 23:19:14 |
| 45.142.195.7 | attackbots | May 27 17:41:13 srv01 postfix/smtpd\[18312\]: warning: unknown\[45.142.195.7\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 May 27 17:41:25 srv01 postfix/smtpd\[11085\]: warning: unknown\[45.142.195.7\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 May 27 17:41:27 srv01 postfix/smtpd\[18312\]: warning: unknown\[45.142.195.7\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 May 27 17:41:28 srv01 postfix/smtpd\[15674\]: warning: unknown\[45.142.195.7\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 May 27 17:42:11 srv01 postfix/smtpd\[19631\]: warning: unknown\[45.142.195.7\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-05-27 23:46:38 |
| 111.231.75.83 | attack | Unauthorised connection attempt detected at AUO NODE 4. System is sshd. Protected by AUO Stack Web Application Firewall (WAF) |
2020-05-27 23:14:08 |