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

Region: Tokyo

Country: Japan

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:
IP Type Details Datetime
47.74.54.116 attackspam
24.07.2020 15:43:03 - RDP Login Fail Detected by 
https://www.elinox.de/RDP-Wächter
2020-07-25 05:51:17
47.74.54.105 attack
11/02/2019-09:22:48.802212 47.74.54.105 Protocol: 6 ET SCAN Potential SSH Scan
2019-11-02 21:27:45
47.74.54.8 attackspambots
11/02/2019-08:59:22.889739 47.74.54.8 Protocol: 6 ET SCAN Potential SSH Scan
2019-11-02 20:59:56
47.74.54.38 attackbots
11/02/2019-08:22:03.022447 47.74.54.38 Protocol: 6 ET SCAN Potential SSH Scan
2019-11-02 20:22:38
Whois info:
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#



# start

NetRange:       47.74.0.0 - 47.87.255.255
CIDR:           47.74.0.0/15, 47.80.0.0/13, 47.76.0.0/14
NetName:        AL-3
NetHandle:      NET-47-74-0-0-1
Parent:         NET47 (NET-47-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       
Organization:   Alibaba Cloud LLC (AL-3)
RegDate:        2016-03-17
Updated:        2017-04-26
Ref:            https://rdap.arin.net/registry/ip/47.74.0.0



OrgName:        Alibaba Cloud LLC
OrgId:          AL-3
Address:        400 S El Camino Real, Suite 400
City:           San Mateo
StateProv:      CA
PostalCode:     94402
Country:        US
RegDate:        2010-10-29
Updated:        2026-02-11
Comment:        1.For AliCloud IPR Infringement and Abuse Claim, please use below link with browser to report: https://intl.aliyun.com/report
Comment:        
Comment:        2.For Alibaba.com and Aliexpress.com's IPR Infringement , please use below link with browser to report: https://ipp.alibabagroup.com
Comment:        
Comment:        3.For Alibaba.com and Aliexpress.com's Abuse, please send email to those two mail lists to report: intl-abuse@list.alibaba-inc.com and abuse@alibaba-inc.com
Comment:        
Comment:        4. For network issue, please send email to this mail list: aliops-goc@list.alibaba-inc.com
Ref:            https://rdap.arin.net/registry/entity/AL-3


OrgNOCHandle: ALIBA-ARIN
OrgNOCName:   Alibaba NOC
OrgNOCPhone:  +1-408-748-1200 
OrgNOCEmail:  noc@list.alibaba-inc.com
OrgNOCRef:    https://rdap.arin.net/registry/entity/ALIBA-ARIN

OrgTechHandle: ALIBA-ARIN
OrgTechName:   Alibaba NOC
OrgTechPhone:  +1-408-748-1200 
OrgTechEmail:  noc@list.alibaba-inc.com
OrgTechRef:    https://rdap.arin.net/registry/entity/ALIBA-ARIN

OrgAbuseHandle: NETWO4028-ARIN
OrgAbuseName:   Network Abuse
OrgAbusePhone:  +1-408-785-5580 
OrgAbuseEmail:  abuse@alibaba-inc.com
OrgAbuseRef:    https://rdap.arin.net/registry/entity/NETWO4028-ARIN

# end


# start

NetRange:       47.74.0.0 - 47.74.63.255
CIDR:           47.74.0.0/18
NetName:        ALIBABA CLOUD - JP
NetHandle:      NET-47-74-0-0-2
Parent:         AL-3 (NET-47-74-0-0-1)
NetType:        Reassigned
OriginAS:       
Customer:       Alibaba Cloud - JP (C07477109)
RegDate:        2019-12-22
Updated:        2024-09-02
Comment:        1.For AliCloud IPR Infringement and Abuse Claim, please use below link with browser to report: https://intl.aliyun.com/report
Comment:        
Comment:        2.For Alibaba.com and Aliexpress.com's IPR Infringement , please use below link with browser to report: https://ipp.alibabagroup.com
Comment:        
Comment:        3.For Alibaba.com and Aliexpress.com's Abuse, please send email to those two mail lists to report: intl-abuse@list.alibaba-inc.com and abuse@alibaba-inc.com
Comment:        
Comment:        4. For network issue, please send email to this mail list: aliops-goc@list.alibaba-inc.com
Ref:            https://rdap.arin.net/registry/ip/47.74.0.0


CustName:       Alibaba Cloud - JP
Address:        27F Kyobashi Edogrand, 2-2-1 Kyobashi, Chuo-ku, Tokyo 1040031
City:           TOKYO
StateProv:      
PostalCode:     
Country:        JP
RegDate:        2019-12-22
Updated:        2024-09-02
Ref:            https://rdap.arin.net/registry/entity/C07477109

OrgNOCHandle: ALIBA-ARIN
OrgNOCName:   Alibaba NOC
OrgNOCPhone:  +1-408-748-1200 
OrgNOCEmail:  noc@list.alibaba-inc.com
OrgNOCRef:    https://rdap.arin.net/registry/entity/ALIBA-ARIN

OrgTechHandle: ALIBA-ARIN
OrgTechName:   Alibaba NOC
OrgTechPhone:  +1-408-748-1200 
OrgTechEmail:  noc@list.alibaba-inc.com
OrgTechRef:    https://rdap.arin.net/registry/entity/ALIBA-ARIN

OrgAbuseHandle: NETWO4028-ARIN
OrgAbuseName:   Network Abuse
OrgAbusePhone:  +1-408-785-5580 
OrgAbuseEmail:  abuse@alibaba-inc.com
OrgAbuseRef:    https://rdap.arin.net/registry/entity/NETWO4028-ARIN

# end



#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 47.74.54.45
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30549
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;47.74.54.45.			IN	A

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

;; Query time: 27 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Nov 22 02:48:23 CST 2026
;; MSG SIZE  rcvd: 104
Host info
Host 45.54.74.47.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 45.54.74.47.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
109.116.41.170 attackbots
Aug 27 21:30:01 124388 sshd[20533]: Invalid user zcy from 109.116.41.170 port 54674
Aug 27 21:30:01 124388 sshd[20533]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.116.41.170
Aug 27 21:30:01 124388 sshd[20533]: Invalid user zcy from 109.116.41.170 port 54674
Aug 27 21:30:03 124388 sshd[20533]: Failed password for invalid user zcy from 109.116.41.170 port 54674 ssh2
Aug 27 21:35:01 124388 sshd[20715]: Invalid user dp from 109.116.41.170 port 33124
2020-08-28 05:36:18
45.154.35.251 attackbots
Aug 27 23:08:44 ns41 sshd[30732]: Failed password for sshd from 45.154.35.251 port 55056 ssh2
Aug 27 23:08:46 ns41 sshd[30732]: Failed password for sshd from 45.154.35.251 port 55056 ssh2
Aug 27 23:08:48 ns41 sshd[30732]: Failed password for sshd from 45.154.35.251 port 55056 ssh2
Aug 27 23:08:50 ns41 sshd[30732]: Failed password for sshd from 45.154.35.251 port 55056 ssh2
2020-08-28 05:35:07
117.121.214.50 attackspam
Aug 27 23:05:51 nuernberg-4g-01 sshd[14597]: Failed password for root from 117.121.214.50 port 37282 ssh2
Aug 27 23:06:27 nuernberg-4g-01 sshd[14756]: Failed password for root from 117.121.214.50 port 36898 ssh2
2020-08-28 05:40:38
89.232.192.40 attackspam
Aug 27 23:08:56 vpn01 sshd[6706]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.232.192.40
Aug 27 23:08:58 vpn01 sshd[6706]: Failed password for invalid user hqd from 89.232.192.40 port 47169 ssh2
...
2020-08-28 05:26:44
191.222.196.231 attack
Unauthorised access (Aug 28) SRC=191.222.196.231 LEN=60 TTL=105 ID=13844 DF TCP DPT=445 WINDOW=8192 SYN
2020-08-28 05:37:34
202.51.74.23 attack
Aug 27 21:21:42 rush sshd[3034]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.51.74.23
Aug 27 21:21:43 rush sshd[3034]: Failed password for invalid user rsyncd from 202.51.74.23 port 47550 ssh2
Aug 27 21:25:56 rush sshd[3168]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.51.74.23
...
2020-08-28 05:27:39
203.6.149.195 attackbots
SSH Brute Force
2020-08-28 05:24:32
129.204.129.170 attackbots
Lines containing failures of 129.204.129.170
Aug 25 21:00:14 kmh-vmh-003-fsn07 sshd[15563]: Invalid user xerox from 129.204.129.170 port 42516
Aug 25 21:00:14 kmh-vmh-003-fsn07 sshd[15563]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.129.170 
Aug 25 21:00:16 kmh-vmh-003-fsn07 sshd[15563]: Failed password for invalid user xerox from 129.204.129.170 port 42516 ssh2
Aug 25 21:00:19 kmh-vmh-003-fsn07 sshd[15563]: Received disconnect from 129.204.129.170 port 42516:11: Bye Bye [preauth]
Aug 25 21:00:19 kmh-vmh-003-fsn07 sshd[15563]: Disconnected from invalid user xerox 129.204.129.170 port 42516 [preauth]
Aug 25 21:05:04 kmh-vmh-003-fsn07 sshd[16250]: Invalid user secretaria from 129.204.129.170 port 35278
Aug 25 21:05:04 kmh-vmh-003-fsn07 sshd[16250]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.129.170 


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=129.204.1
2020-08-28 05:43:44
222.73.182.137 attackbots
SSH Invalid Login
2020-08-28 05:48:10
222.186.175.154 attack
Aug 27 23:22:24 abendstille sshd\[14771\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.154  user=root
Aug 27 23:22:24 abendstille sshd\[14769\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.154  user=root
Aug 27 23:22:25 abendstille sshd\[14771\]: Failed password for root from 222.186.175.154 port 28458 ssh2
Aug 27 23:22:25 abendstille sshd\[14769\]: Failed password for root from 222.186.175.154 port 34752 ssh2
Aug 27 23:22:28 abendstille sshd\[14771\]: Failed password for root from 222.186.175.154 port 28458 ssh2
...
2020-08-28 05:32:28
131.193.45.153 attack
[H1] Blocked by UFW
2020-08-28 05:26:17
61.133.232.250 attackbots
Aug 27 23:14:35 hell sshd[5622]: Failed password for postgres from 61.133.232.250 port 25961 ssh2
Aug 27 23:22:43 hell sshd[7247]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.133.232.250
...
2020-08-28 05:24:10
134.209.96.131 attack
Aug 27 23:40:33 lnxded64 sshd[32576]: Failed password for root from 134.209.96.131 port 41652 ssh2
Aug 27 23:40:33 lnxded64 sshd[32576]: Failed password for root from 134.209.96.131 port 41652 ssh2
2020-08-28 05:52:16
182.122.1.232 attackbotsspam
Aug 26 08:45:31 fwweb01 sshd[6586]: reveeclipse mapping checking getaddrinfo for hn.kd.ny.adsl [182.122.1.232] failed - POSSIBLE BREAK-IN ATTEMPT!
Aug 26 08:45:31 fwweb01 sshd[6586]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.122.1.232  user=r.r
Aug 26 08:45:33 fwweb01 sshd[6586]: Failed password for r.r from 182.122.1.232 port 25500 ssh2
Aug 26 08:45:33 fwweb01 sshd[6586]: Received disconnect from 182.122.1.232: 11: Bye Bye [preauth]
Aug 26 08:50:14 fwweb01 sshd[7096]: reveeclipse mapping checking getaddrinfo for hn.kd.ny.adsl [182.122.1.232] failed - POSSIBLE BREAK-IN ATTEMPT!
Aug 26 08:50:14 fwweb01 sshd[7096]: Invalid user yangchen from 182.122.1.232
Aug 26 08:50:14 fwweb01 sshd[7096]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.122.1.232 
Aug 26 08:50:16 fwweb01 sshd[7096]: Failed password for invalid user yangchen from 182.122.1.232 port 21272 ssh2
Aug 26 08:50:17 fwwe........
-------------------------------
2020-08-28 05:55:22
129.211.54.147 attackspambots
SSH Invalid Login
2020-08-28 05:53:21

Recently Reported IPs

52.129.1.1 33.72.78.155 27.109.112.171 242.145.170.220
223.130.168.17 211.1.233.151 187.157.132.238 186.240.144.48
185.239.31.138 182.158.53.215 74.127.65.47 173.80.207.213
172.29.129.212 17.85.71.58 169.78.70.121 159.144.214.209
146.103.221.131 132.191.9.196 128.122.126.33 123.19.170.165