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: Korea (the Republic of)

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

;; QUESTION SECTION:
;54.180.67.143.			IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 05 23:44:02 CST 2025
;; MSG SIZE  rcvd: 106
Host info
143.67.180.54.in-addr.arpa domain name pointer ec2-54-180-67-143.ap-northeast-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
143.67.180.54.in-addr.arpa	name = ec2-54-180-67-143.ap-northeast-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
54.37.159.12 attackspam
Dec 27 17:38:58 server sshd\[11750\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=12.ip-54-37-159.eu  user=root
Dec 27 17:39:00 server sshd\[11750\]: Failed password for root from 54.37.159.12 port 40244 ssh2
Dec 27 17:49:25 server sshd\[14714\]: Invalid user legal1 from 54.37.159.12
Dec 27 17:49:25 server sshd\[14714\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=12.ip-54-37-159.eu 
Dec 27 17:49:27 server sshd\[14714\]: Failed password for invalid user legal1 from 54.37.159.12 port 51412 ssh2
...
2019-12-28 02:20:57
221.214.60.17 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2019-12-28 01:52:18
120.192.246.107 attack
SIP/5060 Probe, BF, Hack -
2019-12-28 01:53:00
121.141.117.35 attack
3389BruteforceFW23
2019-12-28 01:52:44
189.90.241.134 attackspambots
Dec 27 17:32:30 dedicated sshd[20959]: Invalid user barney from 189.90.241.134 port 45130
2019-12-28 01:58:03
210.16.187.206 attack
Dec 27 17:22:25 localhost sshd\[103077\]: Invalid user arunp from 210.16.187.206 port 41103
Dec 27 17:22:25 localhost sshd\[103077\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.16.187.206
Dec 27 17:22:27 localhost sshd\[103077\]: Failed password for invalid user arunp from 210.16.187.206 port 41103 ssh2
Dec 27 17:25:31 localhost sshd\[103137\]: Invalid user kbn from 210.16.187.206 port 48909
Dec 27 17:25:31 localhost sshd\[103137\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.16.187.206
...
2019-12-28 02:31:47
61.12.38.162 attackspam
Brute-force attempt banned
2019-12-28 01:49:53
119.28.173.184 attackbotsspam
SIP/5060 Probe, BF, Hack -
2019-12-28 02:15:43
104.236.142.89 attackspam
Dec 27 16:40:07 host sshd[49534]: Invalid user server from 104.236.142.89 port 46340
...
2019-12-28 01:53:25
111.11.107.130 attack
12/27/2019-11:43:42.955017 111.11.107.130 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-12-28 02:28:18
61.177.172.128 attackspambots
Dec 27 21:14:33 server sshd\[23679\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.177.172.128  user=root
Dec 27 21:14:34 server sshd\[23684\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.177.172.128  user=root
Dec 27 21:14:35 server sshd\[23679\]: Failed password for root from 61.177.172.128 port 48352 ssh2
Dec 27 21:14:36 server sshd\[23684\]: Failed password for root from 61.177.172.128 port 26388 ssh2
Dec 27 21:14:38 server sshd\[23679\]: Failed password for root from 61.177.172.128 port 48352 ssh2
...
2019-12-28 02:18:52
118.32.194.132 attackspam
Automatic report - SSH Brute-Force Attack
2019-12-28 02:16:28
82.159.138.57 attack
2019-12-27T14:42:50.028109abusebot-3.cloudsearch.cf sshd[31702]: Invalid user bayfield from 82.159.138.57 port 61781
2019-12-27T14:42:50.034007abusebot-3.cloudsearch.cf sshd[31702]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.159.138.57.static.user.ono.com
2019-12-27T14:42:50.028109abusebot-3.cloudsearch.cf sshd[31702]: Invalid user bayfield from 82.159.138.57 port 61781
2019-12-27T14:42:51.794887abusebot-3.cloudsearch.cf sshd[31702]: Failed password for invalid user bayfield from 82.159.138.57 port 61781 ssh2
2019-12-27T14:49:50.272690abusebot-3.cloudsearch.cf sshd[31756]: Invalid user jeger from 82.159.138.57 port 62061
2019-12-27T14:49:50.280055abusebot-3.cloudsearch.cf sshd[31756]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.159.138.57.static.user.ono.com
2019-12-27T14:49:50.272690abusebot-3.cloudsearch.cf sshd[31756]: Invalid user jeger from 82.159.138.57 port 62061
2019-12-27T14:49:52.03
...
2019-12-28 02:05:51
182.150.58.161 attack
12/27/2019-15:49:40.752067 182.150.58.161 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-12-28 02:15:20
49.88.160.115 attack
Dec 27 15:49:47 grey postfix/smtpd\[4031\]: NOQUEUE: reject: RCPT from unknown\[49.88.160.115\]: 554 5.7.1 Service unavailable\; Client host \[49.88.160.115\] blocked using truncate.gbudb.net\; http://www.gbudb.com/truncate/ \[49.88.160.115\]\; from=\ to=\ proto=ESMTP helo=\
...
2019-12-28 02:11:06

Recently Reported IPs

188.238.249.81 20.214.225.24 46.78.24.116 67.197.79.163
139.221.4.161 237.10.26.128 192.34.2.31 9.115.45.30
189.185.36.195 207.88.27.21 74.41.184.167 224.247.237.24
193.178.84.105 238.152.238.119 230.146.23.149 34.229.85.141
101.77.7.177 84.12.137.175 8.213.187.182 147.115.82.114