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

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

;; QUESTION SECTION:
;54.196.45.23.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 07 23:29:28 CST 2022
;; MSG SIZE  rcvd: 105
Host info
23.45.196.54.in-addr.arpa domain name pointer ec2-54-196-45-23.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
23.45.196.54.in-addr.arpa	name = ec2-54-196-45-23.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
80.66.81.143 attackspambots
Feb  9 18:08:38 relay postfix/smtpd\[23033\]: warning: unknown\[80.66.81.143\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Feb  9 18:09:10 relay postfix/smtpd\[26766\]: warning: unknown\[80.66.81.143\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Feb  9 18:09:30 relay postfix/smtpd\[23033\]: warning: unknown\[80.66.81.143\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Feb  9 18:14:04 relay postfix/smtpd\[23595\]: warning: unknown\[80.66.81.143\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Feb  9 18:14:23 relay postfix/smtpd\[23533\]: warning: unknown\[80.66.81.143\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-02-10 01:21:55
80.82.77.245 attackspambots
80.82.77.245 was recorded 24 times by 12 hosts attempting to connect to the following ports: 1026,1029,1032,1022. Incident counter (4h, 24h, all-time): 24, 131, 20389
2020-02-10 00:39:37
80.23.235.225 attackspambots
Feb  9 14:17:26 icinga sshd[55367]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.23.235.225 
Feb  9 14:17:29 icinga sshd[55367]: Failed password for invalid user edk from 80.23.235.225 port 54623 ssh2
Feb  9 14:35:13 icinga sshd[6834]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=80.23.235.225 
...
2020-02-10 00:38:45
220.142.173.149 attack
23/tcp
[2020-02-09]1pkt
2020-02-10 00:42:27
84.1.30.70 attackbotsspam
Feb  9 06:48:14 auw2 sshd\[25164\]: Invalid user cly from 84.1.30.70
Feb  9 06:48:14 auw2 sshd\[25164\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ktv54011e46.fixip.t-online.hu
Feb  9 06:48:16 auw2 sshd\[25164\]: Failed password for invalid user cly from 84.1.30.70 port 57602 ssh2
Feb  9 06:51:04 auw2 sshd\[25476\]: Invalid user tie from 84.1.30.70
Feb  9 06:51:04 auw2 sshd\[25476\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ktv54011e46.fixip.t-online.hu
2020-02-10 01:10:49
109.130.255.121 attackbots
Automatic report - Port Scan Attack
2020-02-10 00:48:21
185.95.185.238 attack
Port probing on unauthorized port 8080
2020-02-10 01:21:07
164.163.1.126 attackbotsspam
20/2/9@08:34:52: FAIL: Alarm-Network address from=164.163.1.126
20/2/9@08:34:52: FAIL: Alarm-Network address from=164.163.1.126
...
2020-02-10 00:58:30
49.232.60.2 attack
Feb  9 00:27:13 server sshd\[1007\]: Invalid user bdn from 49.232.60.2
Feb  9 00:27:13 server sshd\[1007\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.60.2 
Feb  9 00:27:15 server sshd\[1007\]: Failed password for invalid user bdn from 49.232.60.2 port 56160 ssh2
Feb  9 16:35:11 server sshd\[24202\]: Invalid user us from 49.232.60.2
Feb  9 16:35:11 server sshd\[24202\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.60.2 
...
2020-02-10 00:40:09
134.209.164.184 attack
Feb  9 16:20:19 silence02 sshd[7619]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.164.184
Feb  9 16:20:20 silence02 sshd[7619]: Failed password for invalid user jne from 134.209.164.184 port 42100 ssh2
Feb  9 16:23:38 silence02 sshd[7758]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.164.184
2020-02-10 01:17:30
163.172.228.9 attackspambots
WordPress login Brute force / Web App Attack on client site.
2020-02-10 00:56:28
24.188.152.107 attackbots
Telnet/23 MH Probe, BF, Hack -
2020-02-10 01:14:13
218.91.97.187 attackbots
Telnet/23 MH Probe, BF, Hack -
2020-02-10 01:20:05
80.88.90.86 attackspam
Automatic report - Banned IP Access
2020-02-10 01:16:51
87.198.108.53 attack
23/tcp
[2020-02-09]1pkt
2020-02-10 01:02:24

Recently Reported IPs

201.209.147.13 212.193.29.56 42.200.143.12 35.198.85.1
117.54.114.99 222.139.75.191 182.127.209.162 194.5.12.15
45.83.64.133 68.71.249.153 176.50.213.84 113.190.16.44
85.172.31.16 31.173.124.114 162.193.245.62 184.154.61.170
121.43.184.83 82.56.55.86 93.143.44.24 223.72.57.250