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

;; QUESTION SECTION:
;13.57.51.94.			IN	A

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

;; Query time: 164 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 17:15:14 CST 2022
;; MSG SIZE  rcvd: 104
Host info
94.51.57.13.in-addr.arpa domain name pointer ec2-13-57-51-94.us-west-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
94.51.57.13.in-addr.arpa	name = ec2-13-57-51-94.us-west-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
116.110.10.167 attackspam
Jun  8 15:52:37 UTC__SANYALnet-Labs__lste sshd[22496]: Connection from 116.110.10.167 port 55756 on 192.168.1.10 port 22
Jun  8 15:52:39 UTC__SANYALnet-Labs__lste sshd[22496]: User r.r from 116.110.10.167 not allowed because not listed in AllowUsers
Jun  8 15:52:39 UTC__SANYALnet-Labs__lste sshd[22496]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.110.10.167  user=r.r
Jun  8 15:52:42 UTC__SANYALnet-Labs__lste sshd[22496]: Failed password for invalid user r.r from 116.110.10.167 port 55756 ssh2
Jun  8 15:52:42 UTC__SANYALnet-Labs__lste sshd[22496]: Connection closed by 116.110.10.167 port 55756 [preauth]
Jun  8 15:53:00 UTC__SANYALnet-Labs__lste sshd[22553]: Connection from 116.110.10.167 port 57298 on 192.168.1.10 port 22
Jun  8 15:53:02 UTC__SANYALnet-Labs__lste sshd[22555]: Connection from 116.110.10.167 port 57624 on 192.168.1.10 port 22
Jun  8 15:53:04 UTC__SANYALnet-Labs__lste sshd[22555]: User r.r from 116.110.10.167 ........
-------------------------------
2020-06-09 05:04:34
46.38.145.6 attackspam
Jun  8 22:45:00 mail postfix/smtpd\[30290\]: warning: unknown\[46.38.145.6\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Jun  8 22:46:35 mail postfix/smtpd\[30290\]: warning: unknown\[46.38.145.6\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Jun  8 22:48:07 mail postfix/smtpd\[30177\]: warning: unknown\[46.38.145.6\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
Jun  8 23:19:09 mail postfix/smtpd\[31477\]: warning: unknown\[46.38.145.6\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\
2020-06-09 05:22:42
49.68.145.56 attackspambots
Jun  8 22:20:26 tux postfix/smtpd[10558]: connect from unknown[49.68.145.56]
Jun x@x
Jun  8 22:20:30 tux postfix/smtpd[10558]: disconnect from unknown[49.68.145.56]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=49.68.145.56
2020-06-09 05:02:06
222.186.15.62 attackspam
06/08/2020-16:52:04.736082 222.186.15.62 Protocol: 6 ET SCAN Potential SSH Scan
2020-06-09 04:54:32
103.89.91.156 attackspambots
RDP brute force attack detected by fail2ban
2020-06-09 04:48:48
201.231.115.87 attack
Jun  8 22:21:54 vpn01 sshd[15403]: Failed password for root from 201.231.115.87 port 39777 ssh2
Jun  8 22:25:55 vpn01 sshd[15422]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.231.115.87
...
2020-06-09 05:08:51
49.234.219.31 attackspam
Jun  8 20:51:45 rush sshd[13980]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.219.31
Jun  8 20:51:47 rush sshd[13980]: Failed password for invalid user admin from 49.234.219.31 port 57060 ssh2
Jun  8 20:54:54 rush sshd[14034]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.219.31
...
2020-06-09 05:01:37
223.71.240.230 attackbots
IP 223.71.240.230 attacked honeypot on port: 139 at 6/8/2020 9:26:01 PM
2020-06-09 04:50:51
115.236.78.222 attackspambots
IP 115.236.78.222 attacked honeypot on port: 139 at 6/8/2020 9:25:56 PM
2020-06-09 04:58:18
193.27.228.221 attackspam
Triggered: repeated knocking on closed ports.
2020-06-09 05:02:56
139.59.12.65 attack
Jun  8 22:22:10 localhost sshd\[15223\]: Invalid user share from 139.59.12.65
Jun  8 22:22:10 localhost sshd\[15223\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.12.65
Jun  8 22:22:11 localhost sshd\[15223\]: Failed password for invalid user share from 139.59.12.65 port 60604 ssh2
Jun  8 22:26:06 localhost sshd\[15457\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.12.65  user=root
Jun  8 22:26:08 localhost sshd\[15457\]: Failed password for root from 139.59.12.65 port 35472 ssh2
...
2020-06-09 04:57:47
222.92.132.5 attackbotsspam
IP 222.92.132.5 attacked honeypot on port: 139 at 6/8/2020 9:25:53 PM
2020-06-09 05:00:58
218.93.105.166 attackspam
IP 218.93.105.166 attacked honeypot on port: 139 at 6/8/2020 9:25:39 PM
2020-06-09 05:13:43
123.177.19.13 attackbots
IP 123.177.19.13 attacked honeypot on port: 139 at 6/8/2020 9:25:57 PM
2020-06-09 04:56:38
61.153.23.172 attackspambots
IP 61.153.23.172 attacked honeypot on port: 139 at 6/8/2020 9:25:54 PM
2020-06-09 05:00:12

Recently Reported IPs

13.57.56.82 13.57.57.176 13.57.56.122 13.57.54.204
13.57.59.222 13.57.51.7 13.57.6.120 13.57.6.177
13.57.56.215 13.57.6.163 117.233.139.4 13.57.51.77
13.57.6.39 13.57.67.249 13.57.7.160 13.57.7.164
13.57.7.182 13.57.68.94 13.57.71.133 13.57.7.90