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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;3.213.136.145.			IN	A

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

;; Query time: 89 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jul 15 05:58:09 CST 2020
;; MSG SIZE  rcvd: 117
Host info
145.136.213.3.in-addr.arpa domain name pointer ec2-3-213-136-145.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
145.136.213.3.in-addr.arpa	name = ec2-3-213-136-145.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
140.143.233.29 attackspam
Apr  2 23:49:40 ns382633 sshd\[24529\]: Invalid user Vv123456789 from 140.143.233.29 port 59000
Apr  2 23:49:40 ns382633 sshd\[24529\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.233.29
Apr  2 23:49:42 ns382633 sshd\[24529\]: Failed password for invalid user Vv123456789 from 140.143.233.29 port 59000 ssh2
Apr  2 23:53:31 ns382633 sshd\[25473\]: Invalid user Aeqy3Zj9LnV from 140.143.233.29 port 37126
Apr  2 23:53:31 ns382633 sshd\[25473\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.233.29
2020-04-03 07:54:04
94.193.38.209 attackbots
Invalid user clc from 94.193.38.209 port 55078
2020-04-03 07:34:33
94.191.50.57 attackspam
Apr  2 21:44:37 124388 sshd[17104]: Failed password for root from 94.191.50.57 port 56096 ssh2
Apr  2 21:47:34 124388 sshd[17242]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.191.50.57  user=root
Apr  2 21:47:37 124388 sshd[17242]: Failed password for root from 94.191.50.57 port 56520 ssh2
Apr  2 21:50:38 124388 sshd[17258]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.191.50.57  user=root
Apr  2 21:50:41 124388 sshd[17258]: Failed password for root from 94.191.50.57 port 56956 ssh2
2020-04-03 07:43:05
198.108.67.37 attack
firewall-block, port(s): 6789/tcp
2020-04-03 08:00:41
159.203.30.208 attackspam
Apr  3 01:09:47 vpn01 sshd[30851]: Failed password for root from 159.203.30.208 port 43715 ssh2
Apr  3 01:15:06 vpn01 sshd[30930]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.30.208
...
2020-04-03 07:42:39
164.132.73.220 attackbots
Unauthorized connection attempt detected from IP address 164.132.73.220 to port 8737
2020-04-03 08:10:42
139.199.23.233 attackbots
$f2bV_matches | Triggered by Fail2Ban at Vostok web server
2020-04-03 08:09:48
221.122.116.72 attack
Apr  2 23:44:57 ns382633 sshd\[23551\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.122.116.72  user=root
Apr  2 23:45:00 ns382633 sshd\[23551\]: Failed password for root from 221.122.116.72 port 50772 ssh2
Apr  2 23:50:48 ns382633 sshd\[25088\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.122.116.72  user=root
Apr  2 23:50:50 ns382633 sshd\[25088\]: Failed password for root from 221.122.116.72 port 42486 ssh2
Apr  2 23:53:46 ns382633 sshd\[25498\]: Invalid user fengyun123 from 221.122.116.72 port 58496
Apr  2 23:53:46 ns382633 sshd\[25498\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.122.116.72
2020-04-03 07:44:51
188.51.139.160 attackbotsspam
Tries to login WordPress (wp-login.php)
2020-04-03 07:54:50
134.122.72.221 attackbotsspam
3x Failed Password
2020-04-03 07:49:16
67.205.135.127 attackspambots
2020-04-02T23:58:45.987587shield sshd\[19925\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.205.135.127  user=root
2020-04-02T23:58:47.678711shield sshd\[19925\]: Failed password for root from 67.205.135.127 port 49258 ssh2
2020-04-03T00:02:01.758413shield sshd\[20605\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.205.135.127  user=root
2020-04-03T00:02:03.690433shield sshd\[20605\]: Failed password for root from 67.205.135.127 port 55420 ssh2
2020-04-03T00:05:24.770297shield sshd\[21163\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.205.135.127  user=root
2020-04-03 08:07:54
120.132.117.254 attackspam
Apr  2 19:51:59 vps46666688 sshd[16929]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.132.117.254
Apr  2 19:52:01 vps46666688 sshd[16929]: Failed password for invalid user test from 120.132.117.254 port 57280 ssh2
...
2020-04-03 07:52:34
106.13.45.212 attackbotsspam
Apr  3 00:54:33 sso sshd[8137]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.45.212
Apr  3 00:54:35 sso sshd[8137]: Failed password for invalid user admin from 106.13.45.212 port 56614 ssh2
...
2020-04-03 07:58:22
31.13.32.186 attack
Invalid user dgp from 31.13.32.186 port 55110
2020-04-03 08:02:25
185.250.205.84 attack
firewall-block, port(s): 1688/tcp, 7491/tcp, 7502/tcp, 16907/tcp
2020-04-03 08:07:17

Recently Reported IPs

186.226.71.179 151.14.6.4 37.208.41.110 204.93.106.189
202.78.200.132 78.173.172.23 134.212.153.13 140.19.146.40
206.146.167.123 138.7.65.184 176.196.191.23 186.221.18.219
51.15.229.198 202.188.219.29 188.152.189.220 177.38.77.202
166.62.27.55 127.14.102.143 106.12.214.173 5.38.146.37