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: Columbus

Region: Ohio

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

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

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

;; Query time: 49 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Oct 02 04:55:48 CST 2019
;; MSG SIZE  rcvd: 117
Host info
220.64.221.18.in-addr.arpa domain name pointer ec2-18-221-64-220.us-east-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
220.64.221.18.in-addr.arpa	name = ec2-18-221-64-220.us-east-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
158.69.197.113 attack
Scanned 3 times in the last 24 hours on port 22
2020-05-14 09:02:39
159.203.34.76 attackspambots
Invalid user developer from 159.203.34.76 port 52032
2020-05-14 08:34:23
178.33.6.239 attackspam
" "
2020-05-14 08:58:07
218.78.54.80 attackspambots
$f2bV_matches
2020-05-14 08:56:37
40.77.167.6 attackbots
Automatic report - Banned IP Access
2020-05-14 08:55:19
79.137.77.131 attackspam
Invalid user user from 79.137.77.131 port 53410
2020-05-14 08:24:37
177.18.148.65 attackspam
Unauthorized connection attempt from IP address 177.18.148.65 on Port 445(SMB)
2020-05-14 08:26:19
51.68.94.177 attack
$f2bV_matches
2020-05-14 08:45:05
94.23.101.187 attackbots
May 13 16:39:26 pixelmemory sshd[803394]: Failed password for invalid user wagner from 94.23.101.187 port 33944 ssh2
May 13 16:42:44 pixelmemory sshd[803915]: Invalid user linux from 94.23.101.187 port 41324
May 13 16:42:44 pixelmemory sshd[803915]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.23.101.187 
May 13 16:42:44 pixelmemory sshd[803915]: Invalid user linux from 94.23.101.187 port 41324
May 13 16:42:46 pixelmemory sshd[803915]: Failed password for invalid user linux from 94.23.101.187 port 41324 ssh2
...
2020-05-14 08:54:03
128.199.84.248 attackbots
detected by Fail2Ban
2020-05-14 09:03:53
60.235.24.222 attack
Fail2Ban Ban Triggered
2020-05-14 08:57:21
103.243.141.144 attackspam
May 13 23:05:16 debian-2gb-nbg1-2 kernel: \[11662773.273528\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=103.243.141.144 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=57596 PROTO=TCP SPT=52095 DPT=3390 WINDOW=1024 RES=0x00 SYN URGP=0
2020-05-14 08:39:11
106.12.27.11 attackspambots
Tried sshing with brute force.
2020-05-14 08:55:34
49.233.138.118 attackbots
SSH brute force
2020-05-14 08:30:15
51.161.8.70 attackspam
May 14 02:34:54 home sshd[3393]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.161.8.70
May 14 02:34:56 home sshd[3393]: Failed password for invalid user wagner from 51.161.8.70 port 52144 ssh2
May 14 02:39:17 home sshd[4214]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.161.8.70
...
2020-05-14 09:02:09

Recently Reported IPs

14.232.23.13 79.11.228.219 254.14.205.82 113.76.245.40
51.159.49.4 109.165.173.235 105.84.199.122 152.227.75.1
191.239.30.60 61.228.188.110 131.140.237.98 141.201.106.237
160.43.107.82 174.39.83.243 201.216.75.224 193.35.155.30
27.154.101.140 193.111.18.88 84.51.13.142 32.81.247.11