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

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

;; QUESTION SECTION:
;104.202.117.221.		IN	A

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

;; Query time: 45 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 19:51:17 CST 2022
;; MSG SIZE  rcvd: 108
Host info
221.117.202.104.in-addr.arpa domain name pointer 221.117-202-104.rdns.scalabledns.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
221.117.202.104.in-addr.arpa	name = 221.117-202-104.rdns.scalabledns.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
81.95.119.147 attack
SSH Brute-Force reported by Fail2Ban
2019-10-22 23:47:36
110.185.106.47 attackbots
2019-10-22T13:57:44.173669abusebot-5.cloudsearch.cf sshd\[21017\]: Invalid user kevinl from 110.185.106.47 port 33458
2019-10-23 00:26:20
49.88.112.76 attack
2019-10-22T23:17:18.860714enmeeting.mahidol.ac.th sshd\[20799\]: User root from 49.88.112.76 not allowed because not listed in AllowUsers
2019-10-22T23:17:19.284903enmeeting.mahidol.ac.th sshd\[20799\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.76  user=root
2019-10-22T23:17:21.430938enmeeting.mahidol.ac.th sshd\[20799\]: Failed password for invalid user root from 49.88.112.76 port 19050 ssh2
...
2019-10-23 00:21:46
106.13.10.159 attackbots
$f2bV_matches
2019-10-23 00:19:07
107.170.227.141 attackspam
Oct 22 08:33:08 Tower sshd[43250]: Connection from 107.170.227.141 port 35726 on 192.168.10.220 port 22
Oct 22 08:33:09 Tower sshd[43250]: Invalid user dmin2 from 107.170.227.141 port 35726
Oct 22 08:33:09 Tower sshd[43250]: error: Could not get shadow information for NOUSER
Oct 22 08:33:09 Tower sshd[43250]: Failed password for invalid user dmin2 from 107.170.227.141 port 35726 ssh2
Oct 22 08:33:09 Tower sshd[43250]: Received disconnect from 107.170.227.141 port 35726:11: Bye Bye [preauth]
Oct 22 08:33:09 Tower sshd[43250]: Disconnected from invalid user dmin2 107.170.227.141 port 35726 [preauth]
2019-10-22 23:53:45
159.89.104.243 attackbots
Oct 22 17:15:05 server sshd\[485\]: Invalid user admin from 159.89.104.243
Oct 22 17:15:05 server sshd\[485\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.104.243 
Oct 22 17:15:07 server sshd\[485\]: Failed password for invalid user admin from 159.89.104.243 port 46069 ssh2
Oct 22 17:26:56 server sshd\[5842\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.104.243  user=root
Oct 22 17:26:59 server sshd\[5842\]: Failed password for root from 159.89.104.243 port 58706 ssh2
...
2019-10-23 00:09:58
188.131.136.36 attackbotsspam
Oct 22 13:11:00 marvibiene sshd[17171]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.131.136.36  user=root
Oct 22 13:11:02 marvibiene sshd[17171]: Failed password for root from 188.131.136.36 port 32994 ssh2
Oct 22 13:32:47 marvibiene sshd[17269]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.131.136.36  user=root
Oct 22 13:32:49 marvibiene sshd[17269]: Failed password for root from 188.131.136.36 port 60724 ssh2
...
2019-10-23 00:32:29
77.247.110.201 attackspam
\[2019-10-22 11:47:40\] NOTICE\[2038\] chan_sip.c: Registration from '\' failed for '77.247.110.201:62281' - Wrong password
\[2019-10-22 11:47:40\] SECURITY\[2046\] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2019-10-22T11:47:40.205-0400",Severity="Error",Service="SIP",EventVersion="2",AccountID="1426",SessionID="0x7f6130477218",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/77.247.110.201/62281",Challenge="7623f41a",ReceivedChallenge="7623f41a",ReceivedHash="8900413bcf8937c495b0238efa4cf55a"
\[2019-10-22 11:47:40\] NOTICE\[2038\] chan_sip.c: Registration from '\' failed for '77.247.110.201:62283' - Wrong password
\[2019-10-22 11:47:40\] SECURITY\[2046\] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2019-10-22T11:47:40.206-0400",Severity="Error",Service="SIP",EventVersion="2",AccountID="1426",SessionID="0x7f6130804e48",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/77.247
2019-10-22 23:51:08
183.2.202.42 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-10-23 00:26:41
94.177.163.133 attackbotsspam
Oct 22 15:43:29 *** sshd[12564]: Invalid user it2 from 94.177.163.133
2019-10-23 00:28:38
223.220.159.78 attack
Oct 22 18:01:10 * sshd[17419]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.220.159.78
Oct 22 18:01:12 * sshd[17419]: Failed password for invalid user woziji from 223.220.159.78 port 53925 ssh2
2019-10-23 00:11:29
217.113.28.7 attackbotsspam
$f2bV_matches
2019-10-22 23:58:28
178.32.206.76 attack
Wordpress bruteforce
2019-10-23 00:30:15
138.197.146.132 attack
WordPress wp-login brute force :: 138.197.146.132 0.088 BYPASS [23/Oct/2019:00:35:34  1100] [censored_2] "POST /wp-login.php HTTP/1.1" 200 4630 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-10-22 23:46:45
91.244.6.63 attackbotsspam
Fail2Ban Ban Triggered
2019-10-22 23:45:05

Recently Reported IPs

104.202.117.218 104.202.117.222 104.202.117.214 104.202.117.237
104.202.117.232 101.109.22.72 104.202.117.226 104.202.117.238
104.202.117.235 104.202.117.249 104.202.117.230 104.202.117.25
104.202.117.240 104.202.117.250 104.202.117.31 101.109.22.77
104.202.117.29 104.202.117.39 104.202.117.32 104.202.117.35