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

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

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

;; Query time: 51 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jul 20 06:36:56 CST 2020
;; MSG SIZE  rcvd: 114
Host info
45.59.21.3.in-addr.arpa domain name pointer ec2-3-21-59-45.us-east-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
45.59.21.3.in-addr.arpa	name = ec2-3-21-59-45.us-east-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
106.12.22.159 attackspambots
Invalid user data from 106.12.22.159 port 58092
2020-05-17 07:48:25
185.53.88.205 attackspam
Scanned 1 times in the last 24 hours on port 5060
2020-05-17 08:05:26
121.241.244.92 attack
SSH Invalid Login
2020-05-17 07:46:07
103.45.117.20 attack
ET CINS Active Threat Intelligence Poor Reputation IP group 98 - port: 23 proto: TCP cat: Misc Attack
2020-05-17 08:10:50
185.173.35.21 attackspam
 TCP (SYN) 185.173.35.21:64105 -> port 445, len 44
2020-05-17 08:04:37
103.45.70.63 attackbots
ET CINS Active Threat Intelligence Poor Reputation IP group 98 - port: 1433 proto: TCP cat: Misc Attack
2020-05-17 08:11:19
122.51.131.225 attack
SSH Brute Force
2020-05-17 07:45:26
220.180.104.130 attackbots
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-17 07:57:55
36.68.6.7 attack
$f2bV_matches
2020-05-17 07:55:17
112.85.42.72 attackspam
May 17 02:30:37 pkdns2 sshd\[4451\]: Failed password for root from 112.85.42.72 port 13541 ssh2May 17 02:32:19 pkdns2 sshd\[4509\]: Failed password for root from 112.85.42.72 port 63731 ssh2May 17 02:35:45 pkdns2 sshd\[4647\]: Failed password for root from 112.85.42.72 port 59631 ssh2May 17 02:37:29 pkdns2 sshd\[4703\]: Failed password for root from 112.85.42.72 port 64332 ssh2May 17 02:38:21 pkdns2 sshd\[4732\]: Failed password for root from 112.85.42.72 port 49070 ssh2May 17 02:39:14 pkdns2 sshd\[4774\]: Failed password for root from 112.85.42.72 port 63345 ssh2
...
2020-05-17 07:47:02
221.226.56.210 attackspambots
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-17 07:57:15
45.178.1.37 attackbots
Invalid user job from 45.178.1.37 port 48122
2020-05-17 07:54:45
183.82.121.34 attackspambots
May 17 00:01:10 ncomp sshd[24279]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.82.121.34  user=root
May 17 00:01:12 ncomp sshd[24279]: Failed password for root from 183.82.121.34 port 33228 ssh2
May 17 00:14:51 ncomp sshd[24589]: Invalid user zhywu from 183.82.121.34
2020-05-17 07:42:06
107.148.131.145 attack
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-17 08:09:01
51.91.250.49 attackspam
Invalid user vagrant1 from 51.91.250.49 port 38896
2020-05-17 07:53:24

Recently Reported IPs

221.241.56.139 119.129.228.122 77.22.150.70 150.148.9.66
222.224.139.114 182.138.100.22 179.187.127.103 116.209.137.201
125.140.166.216 93.105.246.176 87.48.10.88 97.239.3.191
211.241.242.230 173.24.54.134 87.52.101.240 91.183.190.118
182.108.250.42 71.255.0.122 201.151.75.62 159.89.160.31