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 '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-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

% 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 info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 112.50.51.199
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3562
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;112.50.51.199.			IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Oct 02 06:31:19 CST 2026
;; MSG SIZE  rcvd: 106
Host info
Host 199.51.50.112.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 199.51.50.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
192.117.187.254 attackbots
Automatic report - XMLRPC Attack
2019-12-21 04:36:24
65.75.93.36 attackspam
detected by Fail2Ban
2019-12-21 04:55:57
123.206.30.76 attackbotsspam
Dec 20 20:20:15 zeus sshd[5587]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.206.30.76 
Dec 20 20:20:18 zeus sshd[5587]: Failed password for invalid user willetta from 123.206.30.76 port 56448 ssh2
Dec 20 20:26:44 zeus sshd[5693]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.206.30.76 
Dec 20 20:26:46 zeus sshd[5693]: Failed password for invalid user xmrpool from 123.206.30.76 port 54904 ssh2
2019-12-21 04:31:33
106.13.4.150 attackspam
Dec 20 05:32:05 php1 sshd\[10623\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.4.150  user=root
Dec 20 05:32:07 php1 sshd\[10623\]: Failed password for root from 106.13.4.150 port 23936 ssh2
Dec 20 05:37:43 php1 sshd\[11283\]: Invalid user betje from 106.13.4.150
Dec 20 05:37:43 php1 sshd\[11283\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.4.150
Dec 20 05:37:46 php1 sshd\[11283\]: Failed password for invalid user betje from 106.13.4.150 port 60752 ssh2
2019-12-21 04:27:06
187.190.235.89 attackbotsspam
Dec 20 10:24:33 kapalua sshd\[27236\]: Invalid user oradata from 187.190.235.89
Dec 20 10:24:33 kapalua sshd\[27236\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=fixed-187-190-235-89.totalplay.net
Dec 20 10:24:35 kapalua sshd\[27236\]: Failed password for invalid user oradata from 187.190.235.89 port 8491 ssh2
Dec 20 10:32:07 kapalua sshd\[27912\]: Invalid user pcap from 187.190.235.89
Dec 20 10:32:07 kapalua sshd\[27912\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=fixed-187-190-235-89.totalplay.net
2019-12-21 04:45:05
192.138.189.89 attackbots
Dec 16 21:18:59 lvps87-230-18-107 sshd[4879]: reveeclipse mapping checking getaddrinfo for webaccountserver-rev-dns [192.138.189.89] failed - POSSIBLE BREAK-IN ATTEMPT!
Dec 16 21:18:59 lvps87-230-18-107 sshd[4879]: Invalid user roseme from 192.138.189.89
Dec 16 21:18:59 lvps87-230-18-107 sshd[4879]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.138.189.89 
Dec 16 21:19:01 lvps87-230-18-107 sshd[4879]: Failed password for invalid user roseme from 192.138.189.89 port 50266 ssh2
Dec 16 21:19:02 lvps87-230-18-107 sshd[4879]: Received disconnect from 192.138.189.89: 11: Bye Bye [preauth]
Dec 16 21:27:16 lvps87-230-18-107 sshd[5046]: reveeclipse mapping checking getaddrinfo for webaccountserver-rev-dns [192.138.189.89] failed - POSSIBLE BREAK-IN ATTEMPT!
Dec 16 21:27:16 lvps87-230-18-107 sshd[5046]: Invalid user admin from 192.138.189.89
Dec 16 21:27:16 lvps87-230-18-107 sshd[5046]: pam_unix(sshd:auth): authentication failure; log........
-------------------------------
2019-12-21 04:46:59
138.197.5.191 attackspambots
Dec 20 21:28:22 ns3042688 sshd\[2883\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.5.191  user=root
Dec 20 21:28:23 ns3042688 sshd\[2883\]: Failed password for root from 138.197.5.191 port 39594 ssh2
Dec 20 21:33:46 ns3042688 sshd\[5514\]: Invalid user mistrulli from 138.197.5.191
Dec 20 21:33:46 ns3042688 sshd\[5514\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.5.191 
Dec 20 21:33:47 ns3042688 sshd\[5514\]: Failed password for invalid user mistrulli from 138.197.5.191 port 47696 ssh2
...
2019-12-21 04:34:40
40.73.34.44 attackspam
Dec 20 18:02:45 ns381471 sshd[26054]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=40.73.34.44
Dec 20 18:02:47 ns381471 sshd[26054]: Failed password for invalid user mmoseley from 40.73.34.44 port 57528 ssh2
2019-12-21 04:46:04
132.232.59.247 attackbotsspam
Dec 20 14:44:28 microserver sshd[18825]: Invalid user heung from 132.232.59.247 port 33580
Dec 20 14:44:28 microserver sshd[18825]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.59.247
Dec 20 14:44:30 microserver sshd[18825]: Failed password for invalid user heung from 132.232.59.247 port 33580 ssh2
Dec 20 14:51:40 microserver sshd[20087]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.59.247  user=root
Dec 20 14:51:42 microserver sshd[20087]: Failed password for root from 132.232.59.247 port 38238 ssh2
Dec 20 15:05:17 microserver sshd[22320]: Invalid user guest from 132.232.59.247 port 48174
Dec 20 15:05:17 microserver sshd[22320]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.59.247
Dec 20 15:05:19 microserver sshd[22320]: Failed password for invalid user guest from 132.232.59.247 port 48174 ssh2
Dec 20 15:12:13 microserver sshd[23193]: Invalid user wwwadmin fr
2019-12-21 04:37:42
130.162.66.198 attackspambots
Repeated brute force against a port
2019-12-21 04:30:35
188.217.238.230 attackspambots
Unauthorized connection attempt detected from IP address 188.217.238.230 to port 23
2019-12-21 04:35:10
89.208.246.240 attackspam
Dec 20 15:41:10 tux-35-217 sshd\[29424\]: Invalid user hamley from 89.208.246.240 port 42180
Dec 20 15:41:10 tux-35-217 sshd\[29424\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.208.246.240
Dec 20 15:41:13 tux-35-217 sshd\[29424\]: Failed password for invalid user hamley from 89.208.246.240 port 42180 ssh2
Dec 20 15:49:15 tux-35-217 sshd\[29479\]: Invalid user kandshom from 89.208.246.240 port 22972
Dec 20 15:49:15 tux-35-217 sshd\[29479\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.208.246.240
...
2019-12-21 04:49:09
106.12.199.74 attackspambots
Dec 20 10:35:32 wbs sshd\[13815\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.199.74  user=root
Dec 20 10:35:34 wbs sshd\[13815\]: Failed password for root from 106.12.199.74 port 60296 ssh2
Dec 20 10:41:04 wbs sshd\[14474\]: Invalid user ftpuser from 106.12.199.74
Dec 20 10:41:04 wbs sshd\[14474\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.199.74
Dec 20 10:41:06 wbs sshd\[14474\]: Failed password for invalid user ftpuser from 106.12.199.74 port 56164 ssh2
2019-12-21 04:53:08
176.31.252.148 attack
Invalid user hareton from 176.31.252.148 port 58783
2019-12-21 04:22:02
209.17.96.98 attackspambots
Unauthorized connection attempt from IP address 209.17.96.98 on Port 137(NETBIOS)
2019-12-21 04:48:17

Recently Reported IPs

117.159.194.85 60.222.142.27 42.239.148.196 42.238.179.131
42.235.14.196 42.229.72.22 42.229.253.163 42.179.15.161
27.47.38.32 27.47.38.224 27.211.248.143 223.89.236.85
222.138.47.255 221.209.246.252 221.207.72.233 123.157.188.241
123.12.56.20 120.242.194.75 120.239.27.15 115.63.66.67