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

Region: unknown

Country: Singapore

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
54.169.164.154 attack
Lines containing failures of 54.169.164.154
Jul 11 05:23:35 shared12 postfix/smtpd[29762]: connect from em3-54-169-164-154.ap-southeast-1.compute.amazonaws.com[54.169.164.154]
Jul x@x
Jul x@x
Jul 11 05:23:36 shared12 postfix/smtpd[29762]: disconnect from em3-54-169-164-154.ap-southeast-1.compute.amazonaws.com[54.169.164.154] ehlo=1 mail=2 rcpt=0/2 data=0/2 eclipset=1 quhostname=1 commands=5/9
Jul 11 05:23:42 shared12 postfix/smtpd[3713]: connect from em3-54-169-164-154.ap-southeast-1.compute.amazonaws.com[54.169.164.154]
Jul x@x
Jul x@x
Jul 11 05:23:43 shared12 postfix/smtpd[3713]: disconnect from em3-54-169-164-154.ap-southeast-1.compute.amazonaws.com[54.169.164.154] ehlo=1 mail=2 rcpt=0/2 data=0/2 eclipset=1 quhostname=1 commands=5/9
Jul 11 05:23:48 shared12 postfix/smtpd[3713]: connect from em3-54-169-164-154.ap-southeast-1.compute.amazonaws.com[54.169.164.154]
Jul x@x
Jul x@x
Jul 11 05:23:49 shared12 postfix/smtpd[3713]: disconnect from em3-54-169-164-154.ap-southeas........
------------------------------
2019-07-11 20:29:42
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 54.169.164.150
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40035
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;54.169.164.150.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Sep 03 02:30:51 CST 2025
;; MSG SIZE  rcvd: 107
Host info
150.164.169.54.in-addr.arpa domain name pointer ec2-54-169-164-150.ap-southeast-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
150.164.169.54.in-addr.arpa	name = ec2-54-169-164-150.ap-southeast-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
129.211.60.153 attack
Invalid user hirano from 129.211.60.153 port 52710
2020-05-13 16:33:21
66.131.216.79 attack
May 13 08:54:47 gw1 sshd[15890]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.131.216.79
May 13 08:54:49 gw1 sshd[15890]: Failed password for invalid user ems from 66.131.216.79 port 50964 ssh2
...
2020-05-13 16:13:14
187.190.50.112 attack
Dovecot Invalid User Login Attempt.
2020-05-13 16:23:14
45.142.195.8 attackbotsspam
May 13 09:01:34 blackbee postfix/smtpd\[18759\]: warning: unknown\[45.142.195.8\]: SASL LOGIN authentication failed: authentication failure
May 13 09:02:00 blackbee postfix/smtpd\[18759\]: warning: unknown\[45.142.195.8\]: SASL LOGIN authentication failed: authentication failure
May 13 09:02:25 blackbee postfix/smtpd\[18759\]: warning: unknown\[45.142.195.8\]: SASL LOGIN authentication failed: authentication failure
May 13 09:02:50 blackbee postfix/smtpd\[18759\]: warning: unknown\[45.142.195.8\]: SASL LOGIN authentication failed: authentication failure
May 13 09:03:15 blackbee postfix/smtpd\[18759\]: warning: unknown\[45.142.195.8\]: SASL LOGIN authentication failed: authentication failure
...
2020-05-13 16:28:55
165.22.254.70 attackbots
May 13 06:07:56 localhost sshd\[22934\]: Invalid user larry from 165.22.254.70
May 13 06:07:56 localhost sshd\[22934\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.254.70
May 13 06:07:58 localhost sshd\[22934\]: Failed password for invalid user larry from 165.22.254.70 port 35482 ssh2
May 13 06:12:37 localhost sshd\[23276\]: Invalid user hadoop from 165.22.254.70
May 13 06:12:37 localhost sshd\[23276\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.254.70
...
2020-05-13 16:32:49
167.71.209.115 attackbotsspam
May 13 05:54:49 wordpress wordpress(www.ruhnke.cloud)[66710]: Blocked authentication attempt for admin from ::ffff:167.71.209.115
2020-05-13 16:10:27
82.148.18.194 attackspambots
postfix
2020-05-13 16:10:59
185.176.27.30 attackspam
05/13/2020-02:30:46.651146 185.176.27.30 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2020-05-13 16:30:42
103.201.147.107 attackbots
May 13 05:54:40 ns3164893 sshd[8912]: Invalid user ubnt from 103.201.147.107 port 53810
May 13 05:54:40 ns3164893 sshd[8912]: Failed none for invalid user ubnt from 103.201.147.107 port 53810 ssh2
...
2020-05-13 16:18:00
85.172.30.18 attack
Automatic report - Banned IP Access
2020-05-13 16:00:09
223.240.109.231 attack
May 13 09:42:19 sip sshd[240798]: Invalid user deploy from 223.240.109.231 port 56876
May 13 09:42:21 sip sshd[240798]: Failed password for invalid user deploy from 223.240.109.231 port 56876 ssh2
May 13 09:48:52 sip sshd[240847]: Invalid user stream from 223.240.109.231 port 60326
...
2020-05-13 16:22:44
51.77.210.216 attackspam
$f2bV_matches
2020-05-13 16:15:51
106.12.57.149 attackspambots
Invalid user user from 106.12.57.149 port 35248
2020-05-13 16:05:31
184.105.139.116 attack
firewall-block, port(s): 50075/tcp
2020-05-13 16:46:16
35.228.143.74 attack
Client requested banned URL [/user/]
2020-05-13 16:42:42

Recently Reported IPs

54.180.89.2 54.153.81.219 52.87.200.208 52.67.223.119
52.63.127.80 52.26.30.174 52.209.246.181 51.20.63.224
47.129.129.53 43.205.195.174 43.201.112.223 3.98.122.104
3.9.179.82 3.82.144.104 3.67.198.119 3.65.219.233
35.92.152.13 35.90.207.98 35.74.22.192 35.183.182.104