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: United States of America (the)

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.149.210.148
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10518
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;54.149.210.148.			IN	A

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

;; Query time: 54 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 27 22:32:29 CST 2025
;; MSG SIZE  rcvd: 107
Host info
148.210.149.54.in-addr.arpa domain name pointer ec2-54-149-210-148.us-west-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
148.210.149.54.in-addr.arpa	name = ec2-54-149-210-148.us-west-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
186.4.123.139 attackspam
$f2bV_matches
2019-11-22 21:46:05
61.163.190.49 attack
Invalid user test from 61.163.190.49 port 59017
2019-11-22 22:12:43
62.173.151.34 attack
11/22/2019-01:18:24.126565 62.173.151.34 Protocol: 17 ET SCAN Sipvicious Scan
2019-11-22 22:02:01
188.133.160.22 attackspam
spam FO
2019-11-22 22:03:30
223.71.139.98 attack
Nov 22 04:21:07 firewall sshd[27028]: Invalid user gabi from 223.71.139.98
Nov 22 04:21:09 firewall sshd[27028]: Failed password for invalid user gabi from 223.71.139.98 port 33336 ssh2
Nov 22 04:25:02 firewall sshd[27096]: Invalid user mai1 from 223.71.139.98
...
2019-11-22 22:12:02
117.94.69.140 attackspambots
badbot
2019-11-22 21:33:08
137.74.171.160 attackbots
Nov 22 09:38:23 sd-53420 sshd\[1672\]: Invalid user dbus from 137.74.171.160
Nov 22 09:38:23 sd-53420 sshd\[1672\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.74.171.160
Nov 22 09:38:26 sd-53420 sshd\[1672\]: Failed password for invalid user dbus from 137.74.171.160 port 33154 ssh2
Nov 22 09:41:46 sd-53420 sshd\[2717\]: Invalid user caila from 137.74.171.160
Nov 22 09:41:46 sd-53420 sshd\[2717\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.74.171.160
...
2019-11-22 22:12:18
120.136.167.74 attackspambots
Nov 22 08:25:19 ny01 sshd[31674]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.136.167.74
Nov 22 08:25:21 ny01 sshd[31674]: Failed password for invalid user operator from 120.136.167.74 port 43518 ssh2
Nov 22 08:29:32 ny01 sshd[32205]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.136.167.74
2019-11-22 21:46:57
188.254.0.145 attackspam
Nov 22 14:01:43 localhost sshd\[76149\]: Invalid user manolis from 188.254.0.145 port 49522
Nov 22 14:01:43 localhost sshd\[76149\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.145
Nov 22 14:01:45 localhost sshd\[76149\]: Failed password for invalid user manolis from 188.254.0.145 port 49522 ssh2
Nov 22 14:05:39 localhost sshd\[76235\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.145  user=root
Nov 22 14:05:41 localhost sshd\[76235\]: Failed password for root from 188.254.0.145 port 56826 ssh2
...
2019-11-22 22:10:56
152.32.96.209 attack
Attempts to probe for or exploit a Drupal site on url: /wp-login.php. Reported by the module https://www.drupal.org/project/abuseipdb.
2019-11-22 21:54:05
200.60.91.42 attackspam
Invalid user camous from 200.60.91.42 port 58156
2019-11-22 21:36:31
154.202.14.250 attackspambots
IP blocked
2019-11-22 21:44:02
185.207.57.123 attackbots
19/11/22@01:18:29: FAIL: IoT-Telnet address from=185.207.57.123
19/11/22@01:18:29: FAIL: IoT-Telnet address from=185.207.57.123
...
2019-11-22 21:57:37
130.180.99.26 attackbots
spam FO
2019-11-22 21:49:52
182.253.205.29 attackbotsspam
Unauthorised access (Nov 22) SRC=182.253.205.29 LEN=44 PREC=0x20 TTL=239 ID=47547 TCP DPT=139 WINDOW=1024 SYN 
Unauthorised access (Nov 21) SRC=182.253.205.29 LEN=44 PREC=0x20 TTL=239 ID=30975 TCP DPT=139 WINDOW=1024 SYN 
Unauthorised access (Nov 19) SRC=182.253.205.29 LEN=44 PREC=0x20 TTL=241 ID=48318 TCP DPT=139 WINDOW=1024 SYN 
Unauthorised access (Nov 18) SRC=182.253.205.29 LEN=44 PREC=0x20 TTL=241 ID=61632 TCP DPT=139 WINDOW=1024 SYN 
Unauthorised access (Nov 17) SRC=182.253.205.29 LEN=44 PREC=0x20 TTL=241 ID=13910 TCP DPT=139 WINDOW=1024 SYN
2019-11-22 22:06:28

Recently Reported IPs

64.58.105.130 77.239.186.244 23.108.162.78 65.153.118.233
169.159.202.76 179.24.157.248 186.251.133.175 147.75.60.103
134.232.193.186 91.110.109.235 42.209.157.246 170.137.129.182
252.139.138.105 29.222.225.65 237.76.224.52 44.104.201.201
12.119.99.66 236.56.234.1 209.183.219.60 22.173.59.183