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

Region: Oregon

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

;; QUESTION SECTION:
;100.21.74.64.			IN	A

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

;; Query time: 61 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat May 21 16:27:52 CST 2022
;; MSG SIZE  rcvd: 105
Host info
64.74.21.100.in-addr.arpa domain name pointer ec2-100-21-74-64.us-west-2.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
64.74.21.100.in-addr.arpa	name = ec2-100-21-74-64.us-west-2.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
222.186.180.223 attackspam
Dec 12 01:03:06 tux-35-217 sshd\[1674\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.223  user=root
Dec 12 01:03:08 tux-35-217 sshd\[1674\]: Failed password for root from 222.186.180.223 port 28658 ssh2
Dec 12 01:03:11 tux-35-217 sshd\[1674\]: Failed password for root from 222.186.180.223 port 28658 ssh2
Dec 12 01:03:14 tux-35-217 sshd\[1674\]: Failed password for root from 222.186.180.223 port 28658 ssh2
...
2019-12-12 08:05:27
171.244.51.114 attackbotsspam
Dec 12 01:04:13 sd-53420 sshd\[17633\]: Invalid user admin from 171.244.51.114
Dec 12 01:04:13 sd-53420 sshd\[17633\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.244.51.114
Dec 12 01:04:15 sd-53420 sshd\[17633\]: Failed password for invalid user admin from 171.244.51.114 port 32862 ssh2
Dec 12 01:11:58 sd-53420 sshd\[18231\]: Invalid user lassie from 171.244.51.114
Dec 12 01:11:58 sd-53420 sshd\[18231\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.244.51.114
...
2019-12-12 08:18:15
188.166.7.108 attackspam
Invalid user jsm from 188.166.7.108 port 48446
2019-12-12 08:04:08
178.128.242.233 attackbotsspam
Dec 12 00:48:06 MK-Soft-VM5 sshd[2122]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.242.233 
Dec 12 00:48:07 MK-Soft-VM5 sshd[2122]: Failed password for invalid user mysql from 178.128.242.233 port 51390 ssh2
...
2019-12-12 08:20:33
61.19.247.121 attackspambots
Dec 12 02:48:37 hosting sshd[26489]: Invalid user server5 from 61.19.247.121 port 48244
...
2019-12-12 07:52:30
192.241.213.168 attackbotsspam
Dec 12 00:40:20 markkoudstaal sshd[19164]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.241.213.168
Dec 12 00:40:22 markkoudstaal sshd[19164]: Failed password for invalid user web from 192.241.213.168 port 40590 ssh2
Dec 12 00:48:27 markkoudstaal sshd[20041]: Failed password for root from 192.241.213.168 port 48042 ssh2
2019-12-12 08:01:10
104.236.192.6 attackspam
Dec 11 12:48:42 server sshd\[19594\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.236.192.6 
Dec 11 12:48:44 server sshd\[19594\]: Failed password for invalid user soni from 104.236.192.6 port 40724 ssh2
Dec 12 02:38:30 server sshd\[32103\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.236.192.6  user=root
Dec 12 02:38:32 server sshd\[32103\]: Failed password for root from 104.236.192.6 port 35518 ssh2
Dec 12 02:48:12 server sshd\[2558\]: Invalid user cic from 104.236.192.6
Dec 12 02:48:12 server sshd\[2558\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.236.192.6 
...
2019-12-12 08:17:16
165.22.16.90 attackbotsspam
fail2ban
2019-12-12 08:00:32
190.201.97.22 attackspambots
1576108100 - 12/12/2019 00:48:20 Host: 190.201.97.22/190.201.97.22 Port: 445 TCP Blocked
2019-12-12 08:08:22
78.187.236.195 attackbotsspam
Telnet/23 MH Probe, BF, Hack -
2019-12-12 07:59:33
222.186.175.154 attackspam
Unauthorized access to SSH at 11/Dec/2019:23:57:43 +0000.
Received:  (SSH-2.0-PuTTY)
2019-12-12 07:57:56
185.52.2.165 attack
185.52.2.165 - - \[12/Dec/2019:00:48:31 +0100\] "POST /wp-login.php HTTP/1.0" 200 4404 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
185.52.2.165 - - \[12/Dec/2019:00:48:32 +0100\] "POST /wp-login.php HTTP/1.0" 200 4236 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
185.52.2.165 - - \[12/Dec/2019:00:48:33 +0100\] "POST /xmlrpc.php HTTP/1.0" 200 736 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-12-12 07:54:25
58.249.102.55 attackbots
The IP has triggered Cloudflare WAF. CF-Ray: 5433b3816c72e7fd | WAF_Rule_ID: 3b40188685924a32bf11d40edea05a27 | WAF_Kind: firewall | CF_Action: drop | Country: CN | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: api.skk.moe | User-Agent: Mozilla/5.066704189 Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 Safari/537.36 | CF_DC: LAX. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-12 07:44:54
2400:dd0d:2000:0:56c8:e3ee:668f:3df attackbots
The IP has triggered Cloudflare WAF. CF-Ray: 5431acba9890bb4c | WAF_Rule_ID: 1112825 | WAF_Kind: firewall | CF_Action: challenge | Country: CN | CF_IPClass: noRecord | Protocol: HTTP/1.1 | Method: GET | Host: img.skk.moe | User-Agent: Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Mobile Safari/537.36 | CF_DC: SEA. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-12 07:46:51
111.206.198.54 attack
The IP has triggered Cloudflare WAF. CF-Ray: 543333e03c79e815 | WAF_Rule_ID: 3b40188685924a32bf11d40edea05a27 | WAF_Kind: firewall | CF_Action: drop | Country: CN | CF_IPClass: searchEngine | Protocol: HTTP/1.1 | Method: GET | Host: d.skk.moe | User-Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B143 Safari/601.1 (compatible; Baiduspider-render/2.0; +http://www.baidu.com/search/spider.html) | CF_DC: LAX. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).
2019-12-12 07:42:11

Recently Reported IPs

100.21.68.161 100.21.78.109 100.22.6.157 100.24.101.208
100.24.101.248 100.24.108.50 100.24.109.86 100.24.109.96
100.24.110.174 100.24.112.206 100.24.129.225 100.24.132.39
100.24.133.6 100.24.134.19 100.24.136.41 100.24.137.42
100.24.138.55 100.24.149.34 100.24.154.187 100.24.155.132