City: unknown
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-AU5); <<>> DiG 9.10.3-P4-Ubuntu <<>> 112.51.80.47
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2077
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;112.51.80.47. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026091001 1800 900 604800 86400
;; Query time: 5 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Sep 11 04:02:39 CST 2026
;; MSG SIZE rcvd: 105Host 47.80.51.112.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 47.80.51.112.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 122.51.186.219 | attackspambots | Jun 9 05:51:02 game-panel sshd[31476]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.186.219 Jun 9 05:51:04 game-panel sshd[31476]: Failed password for invalid user clamav from 122.51.186.219 port 39958 ssh2 Jun 9 05:55:36 game-panel sshd[31785]: Failed password for root from 122.51.186.219 port 33022 ssh2 |
2020-06-09 15:03:33 |
| 49.232.87.218 | attack | Jun 8 03:53:45 reporting7 sshd[21403]: User r.r from 49.232.87.218 not allowed because not listed in AllowUsers Jun 8 03:53:45 reporting7 sshd[21403]: Failed password for invalid user r.r from 49.232.87.218 port 49386 ssh2 Jun 8 03:58:52 reporting7 sshd[23705]: User r.r from 49.232.87.218 not allowed because not listed in AllowUsers Jun 8 03:58:52 reporting7 sshd[23705]: Failed password for invalid user r.r from 49.232.87.218 port 40568 ssh2 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=49.232.87.218 |
2020-06-09 14:43:07 |
| 114.67.77.159 | attackbots | Jun 9 11:13:41 dhoomketu sshd[592251]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.67.77.159 user=root Jun 9 11:13:44 dhoomketu sshd[592251]: Failed password for root from 114.67.77.159 port 60304 ssh2 Jun 9 11:14:42 dhoomketu sshd[592263]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.67.77.159 user=root Jun 9 11:14:44 dhoomketu sshd[592263]: Failed password for root from 114.67.77.159 port 45736 ssh2 Jun 9 11:15:42 dhoomketu sshd[592287]: Invalid user guoliang from 114.67.77.159 port 59404 ... |
2020-06-09 14:45:22 |
| 167.99.75.240 | attackbots | 2020-06-09T05:50:52.852605sd-86998 sshd[33158]: Invalid user user2 from 167.99.75.240 port 49094 2020-06-09T05:50:52.858077sd-86998 sshd[33158]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.75.240 2020-06-09T05:50:52.852605sd-86998 sshd[33158]: Invalid user user2 from 167.99.75.240 port 49094 2020-06-09T05:50:54.570532sd-86998 sshd[33158]: Failed password for invalid user user2 from 167.99.75.240 port 49094 ssh2 2020-06-09T05:54:48.523150sd-86998 sshd[33649]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.75.240 user=root 2020-06-09T05:54:50.300860sd-86998 sshd[33649]: Failed password for root from 167.99.75.240 port 51798 ssh2 ... |
2020-06-09 14:28:14 |
| 35.221.156.44 | attackbotsspam | Attempted to connect 2 times to port 80 TCP |
2020-06-09 14:50:55 |
| 134.209.252.17 | attackbots | SSH Brute Force |
2020-06-09 15:12:00 |
| 159.65.111.89 | attack | $f2bV_matches |
2020-06-09 14:49:08 |
| 192.168.0.1 | attackspambots | Port scan |
2020-06-09 15:06:45 |
| 186.88.166.79 | attackspam | IP 186.88.166.79 attacked honeypot on port: 1434 at 6/9/2020 4:54:17 AM |
2020-06-09 14:45:54 |
| 101.187.123.101 | attackbots | Jun 9 08:16:43 piServer sshd[4208]: Failed password for root from 101.187.123.101 port 49262 ssh2 Jun 9 08:25:03 piServer sshd[4897]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.187.123.101 Jun 9 08:25:05 piServer sshd[4897]: Failed password for invalid user fml from 101.187.123.101 port 50607 ssh2 ... |
2020-06-09 14:37:23 |
| 123.59.213.68 | attackbots | Jun 9 08:51:35 vps639187 sshd\[19260\]: Invalid user software from 123.59.213.68 port 34988 Jun 9 08:51:35 vps639187 sshd\[19260\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.59.213.68 Jun 9 08:51:37 vps639187 sshd\[19260\]: Failed password for invalid user software from 123.59.213.68 port 34988 ssh2 ... |
2020-06-09 14:53:40 |
| 84.255.249.179 | attackbotsspam | Jun 9 01:35:20 ws22vmsma01 sshd[174051]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.255.249.179 Jun 9 01:35:22 ws22vmsma01 sshd[174051]: Failed password for invalid user MYUSER from 84.255.249.179 port 56314 ssh2 ... |
2020-06-09 14:49:28 |
| 51.178.30.102 | attackbotsspam | Jun 9 07:59:01 vpn01 sshd[26409]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.178.30.102 Jun 9 07:59:03 vpn01 sshd[26409]: Failed password for invalid user ding@123 from 51.178.30.102 port 44002 ssh2 ... |
2020-06-09 15:12:50 |
| 144.91.94.185 | attackspambots | Jun 9 06:03:01 xxxxxxx7446550 sshd[12219]: Invalid user production from 144.91.94.185 Jun 9 06:03:03 xxxxxxx7446550 sshd[12219]: Failed password for invalid user production from 144.91.94.185 port 43788 ssh2 Jun 9 06:03:03 xxxxxxx7446550 sshd[12220]: Received disconnect from 144.91.94.185: 11: Bye Bye Jun 9 06:07:08 xxxxxxx7446550 sshd[14610]: Failed password for r.r from 144.91.94.185 port 55466 ssh2 Jun 9 06:07:08 xxxxxxx7446550 sshd[14611]: Received disconnect from 144.91.94.185: 11: Bye Bye Jun 9 06:10:25 xxxxxxx7446550 sshd[16504]: Invalid user administrador from 144.91.94.185 Jun 9 06:10:27 xxxxxxx7446550 sshd[16504]: Failed password for invalid user administrador from 144.91.94.185 port 33244 ssh2 Jun 9 06:10:27 xxxxxxx7446550 sshd[16505]: Received disconnect from 144.91.94.185: 11: Bye Bye Jun 9 06:13:49 xxxxxxx7446550 sshd[18885]: Failed password for r.r from 144.91.94.185 port 39248 ssh2 Jun 9 06:13:49 xxxxxxx7446550 sshd[18886]: Received disconnect ........ ------------------------------- |
2020-06-09 14:36:27 |
| 34.92.68.172 | attack | Jun 9 06:51:31 nextcloud sshd\[27602\]: Invalid user shclient from 34.92.68.172 Jun 9 06:51:31 nextcloud sshd\[27602\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=34.92.68.172 Jun 9 06:51:33 nextcloud sshd\[27602\]: Failed password for invalid user shclient from 34.92.68.172 port 53762 ssh2 |
2020-06-09 14:35:09 |