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

Region: Zhejiang

Country: China

Internet Service Provider: unknown

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.124.0.0 - 112.127.255.255'

% Abuse contact for '112.124.0.0 - 112.127.255.255' is 'didong.jc@alibaba-inc.com'

inetnum:        112.124.0.0 - 112.127.255.255
netname:        ALISOFT
descr:          Aliyun Computing Co., LTD
descr:          5F, Builing D, the West Lake International Plaza of S&T
descr:          No.391 Wen'er Road, Hangzhou, Zhejiang, China, 310099
country:        CN
admin-c:        ZM1015-AP
tech-c:         ZM877-AP
tech-c:         ZM876-AP
tech-c:         ZM875-AP
abuse-c:        AC1601-AP
status:         ALLOCATED PORTABLE
mnt-by:         MAINT-CNNIC-AP
mnt-irt:        IRT-ALISOFT-CN
last-modified:  2023-11-28T00:56:52Z
source:         APNIC

irt:            IRT-ALISOFT-CN
address:        No.391 Wen'er Road, Hangzhou, Zhejiang, China, 310099
e-mail:         didong.jc@alibaba-inc.com
abuse-mailbox:  didong.jc@alibaba-inc.com
admin-c:        ZM877-AP
tech-c:         ZM877-AP
auth:           # Filtered
mnt-by:         MAINT-CNNIC-AP
last-modified:  2025-11-18T00:35:07Z
source:         APNIC

role:           ABUSE CNNICCN
country:        ZZ
address:        Beijing, China
phone:          +000000000
e-mail:         ipas@cnnic.cn
admin-c:        IP50-AP
tech-c:         IP50-AP
nic-hdl:        AC1601-AP
remarks:        Generated from irt object IRT-CNNIC-CN
remarks:        ipas@cnnic.cn is invalid
abuse-mailbox:  ipas@cnnic.cn
mnt-by:         APNIC-ABUSE
last-modified:  2025-09-19T17:20:32Z
source:         APNIC

person:         Li Jia
address:        NO.969 West Wen Yi Road, Yu Hang District, Hangzhou
country:        CN
phone:          +86-0571-85022088
e-mail:         jiali.jl@alibaba-inc.com
nic-hdl:        ZM1015-AP
mnt-by:         MAINT-CNNIC-AP
last-modified:  2025-07-01T07:12:42Z
source:         APNIC

person:         Guoxin Gao
address:        5F, Builing D, the West Lake International Plaza of S&T
address:        No.391 Wen'er Road, Hangzhou City
address:        Zhejiang, China, 310099
country:        CN
phone:          +86-0571-85022600
fax-no:         +86-0571-85022600
e-mail:         anti-spam@list.alibaba-inc.com
nic-hdl:        ZM875-AP
mnt-by:         MAINT-CNNIC-AP
last-modified:  2014-07-30T01:56:01Z
source:         APNIC

person:         security trouble
e-mail:         abuse@alibaba-inc.com
address:        5th,floor,Building D,the West Lake International Plaza of S&T,391#Wen??r Road
address:        Hangzhou, Zhejiang, China
phone:          +86-0571-85022600
country:        CN
mnt-by:         MAINT-CNNIC-AP
nic-hdl:        ZM876-AP
last-modified:  2025-07-01T07:06:11Z
source:         APNIC

person:         Guowei Pan
address:        5F, Builing D, the West Lake International Plaza of S&T
address:        No.391 Wen'er Road, Hangzhou City
address:        Zhejiang, China, 310099
country:        CN
phone:          +86-0571-85022088-30763
fax-no:         +86-0571-85022600
e-mail:         abuse@alibaba-inc.com
nic-hdl:        ZM877-AP
mnt-by:         MAINT-CNNIC-AP
last-modified:  2025-07-01T07:05:46Z
source:         APNIC

% Information related to '112.124.0.0/14AS37963'

route:          112.124.0.0/14
descr:          Hangzhou Alibaba Advertising Co.,Ltd.
country:        CN
origin:         AS37963
mnt-by:         MAINT-CNNIC-AP
last-modified:  2019-08-07T23:28:03Z
source:         APNIC

% Information related to '112.124.0.0/14AS45102'

route:          112.124.0.0/14
descr:          Alibaba (US) Technology Co., Ltd.
country:        CN
origin:         AS45102
mnt-by:         MAINT-CNNIC-AP
last-modified:  2019-08-07T23:28:02Z
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 <<>> 112.124.38.136
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 15621
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;112.124.38.136.			IN	A

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

;; Query time: 28 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 25 05:30:05 CST 2026
;; MSG SIZE  rcvd: 107
Host info
Host 136.38.124.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 136.38.124.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
208.66.192.53 attackspam
fail2ban honeypot
2019-12-24 04:03:34
103.225.124.50 attackbots
Dec 23 05:46:19 kapalua sshd\[17347\]: Invalid user guest from 103.225.124.50
Dec 23 05:46:19 kapalua sshd\[17347\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.225.124.50
Dec 23 05:46:21 kapalua sshd\[17347\]: Failed password for invalid user guest from 103.225.124.50 port 37183 ssh2
Dec 23 05:52:45 kapalua sshd\[17871\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.225.124.50  user=root
Dec 23 05:52:46 kapalua sshd\[17871\]: Failed password for root from 103.225.124.50 port 39578 ssh2
2019-12-24 03:52:09
185.143.223.81 attack
Dec 23 20:09:37 h2177944 kernel: \[326946.943833\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.143.223.81 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=23766 PROTO=TCP SPT=59834 DPT=48524 WINDOW=1024 RES=0x00 SYN URGP=0 
Dec 23 20:09:37 h2177944 kernel: \[326946.943849\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.143.223.81 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=23766 PROTO=TCP SPT=59834 DPT=48524 WINDOW=1024 RES=0x00 SYN URGP=0 
Dec 23 20:14:07 h2177944 kernel: \[327217.067223\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.143.223.81 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=28131 PROTO=TCP SPT=59834 DPT=14295 WINDOW=1024 RES=0x00 SYN URGP=0 
Dec 23 20:14:07 h2177944 kernel: \[327217.067236\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.143.223.81 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=28131 PROTO=TCP SPT=59834 DPT=14295 WINDOW=1024 RES=0x00 SYN URGP=0 
Dec 23 20:14:47 h2177944 kernel: \[327256.660600\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=185.143.223.81 DST=85.214.1
2019-12-24 03:53:29
83.240.245.242 attackspam
Dec 23 13:42:16 *** sshd[5074]: Failed password for invalid user malo from 83.240.245.242 port 34136 ssh2
Dec 23 14:00:24 *** sshd[5266]: Failed password for invalid user jsclient from 83.240.245.242 port 60025 ssh2
Dec 23 14:05:18 *** sshd[5335]: Failed password for invalid user okeda from 83.240.245.242 port 35423 ssh2
Dec 23 14:10:12 *** sshd[5446]: Failed password for invalid user guest from 83.240.245.242 port 33780 ssh2
Dec 23 14:15:11 *** sshd[5509]: Failed password for invalid user ubuntu from 83.240.245.242 port 41194 ssh2
Dec 23 14:20:05 *** sshd[5562]: Failed password for invalid user wellbank from 83.240.245.242 port 40454 ssh2
Dec 23 14:29:56 *** sshd[6120]: Failed password for invalid user host from 83.240.245.242 port 50108 ssh2
Dec 23 14:44:42 *** sshd[6346]: Failed password for invalid user shakeel from 83.240.245.242 port 39200 ssh2
Dec 23 14:49:45 *** sshd[6406]: Failed password for invalid user coreen from 83.240.245.242 port 46769 ssh2
Dec 23 14:54:45 *** sshd[6459]: Failed password for i
2019-12-24 04:16:39
187.87.17.89 attack
2323/tcp 23/tcp...
[2019-10-25/12-22]7pkt,2pt.(tcp)
2019-12-24 04:12:21
58.167.161.212 attackbotsspam
Dec 23 16:00:17 tor-proxy-04 sshd\[30376\]: Invalid user pi from 58.167.161.212 port 49302
Dec 23 16:00:17 tor-proxy-04 sshd\[30377\]: Invalid user pi from 58.167.161.212 port 49304
Dec 23 16:00:17 tor-proxy-04 sshd\[30377\]: Connection closed by 58.167.161.212 port 49304 \[preauth\]
Dec 23 16:00:17 tor-proxy-04 sshd\[30376\]: Connection closed by 58.167.161.212 port 49302 \[preauth\]
...
2019-12-24 04:10:28
61.187.53.119 attack
Dec 23 16:37:04 sd-53420 sshd\[677\]: Invalid user sai from 61.187.53.119
Dec 23 16:37:04 sd-53420 sshd\[677\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.187.53.119
Dec 23 16:37:07 sd-53420 sshd\[677\]: Failed password for invalid user sai from 61.187.53.119 port 4853 ssh2
Dec 23 16:45:57 sd-53420 sshd\[4119\]: Invalid user proxy1 from 61.187.53.119
Dec 23 16:45:57 sd-53420 sshd\[4119\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.187.53.119
...
2019-12-24 04:17:01
129.204.38.136 attackbots
Apr 19 12:26:32 yesfletchmain sshd\[22856\]: Invalid user nr from 129.204.38.136 port 38920
Apr 19 12:26:32 yesfletchmain sshd\[22856\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.38.136
Apr 19 12:26:34 yesfletchmain sshd\[22856\]: Failed password for invalid user nr from 129.204.38.136 port 38920 ssh2
Apr 19 12:30:32 yesfletchmain sshd\[23152\]: Invalid user desktop from 129.204.38.136 port 37330
Apr 19 12:30:32 yesfletchmain sshd\[23152\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.38.136
...
2019-12-24 03:43:02
202.151.30.145 attack
2019-12-23T16:56:20.702134vps751288.ovh.net sshd\[12096\]: Invalid user rpm from 202.151.30.145 port 53956
2019-12-23T16:56:20.710895vps751288.ovh.net sshd\[12096\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.151.30.145
2019-12-23T16:56:22.691849vps751288.ovh.net sshd\[12096\]: Failed password for invalid user rpm from 202.151.30.145 port 53956 ssh2
2019-12-23T17:03:56.774255vps751288.ovh.net sshd\[12166\]: Invalid user squid from 202.151.30.145 port 57888
2019-12-23T17:03:56.784896vps751288.ovh.net sshd\[12166\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.151.30.145
2019-12-24 04:07:27
124.116.223.79 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-12-24 03:55:28
66.96.246.195 attackbotsspam
Unauthorized connection attempt detected from IP address 66.96.246.195 to port 445
2019-12-24 03:46:55
152.32.146.169 attackspambots
2019-12-23T16:59:47.612836scmdmz1 sshd[22824]: Invalid user hattar from 152.32.146.169 port 44968
2019-12-23T16:59:47.615689scmdmz1 sshd[22824]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.32.146.169
2019-12-23T16:59:47.612836scmdmz1 sshd[22824]: Invalid user hattar from 152.32.146.169 port 44968
2019-12-23T16:59:50.013232scmdmz1 sshd[22824]: Failed password for invalid user hattar from 152.32.146.169 port 44968 ssh2
2019-12-23T17:05:42.854207scmdmz1 sshd[23684]: Invalid user matt from 152.32.146.169 port 49998
...
2019-12-24 04:18:19
5.196.227.244 attackbotsspam
Invalid user betsabe from 5.196.227.244 port 59804
2019-12-24 04:17:24
129.204.29.45 attack
Feb 27 00:05:13 dillonfme sshd\[29048\]: Invalid user nw from 129.204.29.45 port 53996
Feb 27 00:05:13 dillonfme sshd\[29048\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.29.45
Feb 27 00:05:15 dillonfme sshd\[29048\]: Failed password for invalid user nw from 129.204.29.45 port 53996 ssh2
Feb 27 00:11:21 dillonfme sshd\[29306\]: User backup from 129.204.29.45 not allowed because not listed in AllowUsers
Feb 27 00:11:21 dillonfme sshd\[29306\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.29.45  user=backup
...
2019-12-24 03:49:42
187.111.212.116 attack
SSH authentication failure x 6 reported by Fail2Ban
...
2019-12-24 04:12:03

Recently Reported IPs

221.165.80.254 52.207.117.184 193.128.202.169 93.81.136.178
115.246.143.17 110.78.154.199 2606:4700:10::6814:7984 2606:4700:10::6814:7778
180.153.236.243 180.153.236.179 14.212.68.19 77.237.240.191
2606:4700:10::6816:62 2606:4700:10::6814:4467 2606:4700:10::ac43:2830 2606:4700:10::ac43:105e
2606:4700:10::6814:7056 2606:4700:10::6816:2369 2606:4700:10::6814:7678 2606:4700:10::6814:4849