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

;; QUESTION SECTION:
;104.22.33.221.			IN	A

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

;; Query time: 268 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 03:32:14 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 221.33.22.104.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 221.33.22.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
95.181.218.177 attackspambots
B: zzZZzz blocked content access
2019-10-29 15:15:18
45.55.184.78 attackspam
2019-10-29T04:23:10.726974abusebot-8.cloudsearch.cf sshd\[17386\]: Invalid user sor123in from 45.55.184.78 port 57562
2019-10-29 15:23:25
134.175.80.27 attackbotsspam
Automatic report - Banned IP Access
2019-10-29 15:18:27
104.245.145.4 attackbotsspam
(From vail.gregg@gmail.com) Hello! If you're reading this then you just proved that contact form advertising works! We can send your promotional message to people via their contact us form on their website. The advantage of this kind of advertising is that messages sent through feedback forms are automatically whitelisted. This dramatically improves the likelihood that your message will be opened. Never any PPC costs! Pay one flat rate and reach millions of people. To get more info send a message to: william4212sau@gmail.com
2019-10-29 15:10:53
189.151.249.97 attackbotsspam
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/189.151.249.97/ 
 
 MX - 1H : (86)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : MX 
 NAME ASN : ASN8151 
 
 IP : 189.151.249.97 
 
 CIDR : 189.151.248.0/21 
 
 PREFIX COUNT : 6397 
 
 UNIQUE IP COUNT : 13800704 
 
 
 ATTACKS DETECTED ASN8151 :  
  1H - 3 
  3H - 7 
  6H - 17 
 12H - 35 
 24H - 75 
 
 DateTime : 2019-10-29 04:53:02 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-10-29 15:23:58
119.203.240.76 attackbots
Oct 28 20:51:21 web1 sshd\[29892\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.203.240.76  user=root
Oct 28 20:51:22 web1 sshd\[29892\]: Failed password for root from 119.203.240.76 port 64054 ssh2
Oct 28 20:58:12 web1 sshd\[30490\]: Invalid user hue from 119.203.240.76
Oct 28 20:58:12 web1 sshd\[30490\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.203.240.76
Oct 28 20:58:14 web1 sshd\[30490\]: Failed password for invalid user hue from 119.203.240.76 port 15168 ssh2
2019-10-29 15:13:09
180.68.177.209 attackspam
2019-10-29T06:55:19.346972shield sshd\[32543\]: Invalid user nikolay from 180.68.177.209 port 48348
2019-10-29T06:55:19.353205shield sshd\[32543\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.68.177.209
2019-10-29T06:55:21.167889shield sshd\[32543\]: Failed password for invalid user nikolay from 180.68.177.209 port 48348 ssh2
2019-10-29T07:01:00.789436shield sshd\[781\]: Invalid user yangguiying from 180.68.177.209 port 56376
2019-10-29T07:01:00.793710shield sshd\[781\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.68.177.209
2019-10-29 15:02:03
178.128.215.16 attackbots
Oct 29 07:59:42 meumeu sshd[32728]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.215.16 
Oct 29 07:59:44 meumeu sshd[32728]: Failed password for invalid user daisy from 178.128.215.16 port 57968 ssh2
Oct 29 08:03:56 meumeu sshd[1058]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.215.16 
...
2019-10-29 15:12:47
217.68.208.30 attackspam
slow and persistent scanner
2019-10-29 15:22:05
61.133.232.248 attackbotsspam
2019-10-29T07:15:31.569731abusebot-5.cloudsearch.cf sshd\[29868\]: Invalid user lee from 61.133.232.248 port 3402
2019-10-29 15:31:00
201.124.75.125 attackspambots
Fail2Ban Ban Triggered
2019-10-29 15:05:36
50.241.104.9 attack
RDP Bruteforce
2019-10-29 14:59:51
104.131.55.236 attack
Oct 29 07:51:08 MK-Soft-Root2 sshd[21743]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.55.236 
Oct 29 07:51:10 MK-Soft-Root2 sshd[21743]: Failed password for invalid user administration from 104.131.55.236 port 54344 ssh2
...
2019-10-29 15:30:10
185.81.157.154 attack
IP address launched attack on many directories on my self hosted Wordpress blog.

This is a direct example of what many of the URL's that were attacked look like: /up14.php?x=upload&mode=upload&upload=&ssp=RfVbHu&u=&action=upload&chdir=./&do=upload&pass=wcwc2016&login=go%21&H=
2019-10-29 15:06:30
46.143.207.127 attack
Automatic report - Port Scan Attack
2019-10-29 15:25:00

Recently Reported IPs

104.22.33.240 104.22.33.237 104.22.33.241 104.22.33.246
104.22.33.249 104.22.33.251 104.22.33.65 104.22.33.72
104.22.33.73 104.22.33.77 104.22.33.76 104.22.33.80
104.22.33.89 104.22.33.90 104.22.33.94 104.22.34.100
104.22.34.101 104.22.34.104 104.22.34.110 104.22.34.118