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

;; QUESTION SECTION:
;104.21.81.33.			IN	A

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

;; Query time: 64 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 03:02:53 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 33.81.21.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 33.81.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
216.245.192.242 attackbotsspam
k+ssh-bruteforce
2019-08-01 05:56:54
103.242.13.70 attackbots
2019-07-31T21:27:58.592270abusebot-8.cloudsearch.cf sshd\[14530\]: Invalid user fr from 103.242.13.70 port 57404
2019-08-01 06:17:13
40.76.1.138 attackspam
SSH Brute-Force reported by Fail2Ban
2019-08-01 05:50:44
218.92.0.191 attackspambots
2019-07-31T21:52:59.278947abusebot-8.cloudsearch.cf sshd\[14621\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.191  user=root
2019-08-01 06:08:44
104.245.145.36 attackspambots
(From mcphillamy.garnet@hotmail.com) Enjoy tons of high converting visitors sent directly to your site starting at only $38. Would you like to learn more? Write a reply here for info: emma5885fro@gmail.com
2019-08-01 05:28:25
116.4.97.5 attack
Automatic report - Port Scan Attack
2019-08-01 05:52:18
49.234.5.134 attackbots
Triggered by Fail2Ban at Vostok web server
2019-08-01 05:51:24
51.254.123.131 attack
Aug  1 00:35:00 server sshd\[17268\]: Invalid user osm from 51.254.123.131 port 34716
Aug  1 00:35:00 server sshd\[17268\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.254.123.131
Aug  1 00:35:02 server sshd\[17268\]: Failed password for invalid user osm from 51.254.123.131 port 34716 ssh2
Aug  1 00:39:01 server sshd\[27273\]: Invalid user sammy from 51.254.123.131 port 58078
Aug  1 00:39:01 server sshd\[27273\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.254.123.131
2019-08-01 05:54:52
14.63.165.49 attack
Jul 31 21:14:31 mail1 sshd\[14575\]: Invalid user islm from 14.63.165.49 port 60468
Jul 31 21:14:31 mail1 sshd\[14575\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.63.165.49
Jul 31 21:14:33 mail1 sshd\[14575\]: Failed password for invalid user islm from 14.63.165.49 port 60468 ssh2
Jul 31 21:27:36 mail1 sshd\[20528\]: Invalid user henk from 14.63.165.49 port 49390
Jul 31 21:27:36 mail1 sshd\[20528\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.63.165.49
...
2019-08-01 05:53:06
189.91.5.228 attackbots
SMTP-sasl brute force
...
2019-08-01 05:46:09
31.163.186.28 attackspambots
Jul 31 08:59:24 localhost kernel: [15822158.142718] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=31.163.186.28 DST=[mungedIP2] LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=39742 PROTO=TCP SPT=27311 DPT=37215 WINDOW=29111 RES=0x00 SYN URGP=0 
Jul 31 08:59:24 localhost kernel: [15822158.142743] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=31.163.186.28 DST=[mungedIP2] LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=39742 PROTO=TCP SPT=27311 DPT=37215 SEQ=758669438 ACK=0 WINDOW=29111 RES=0x00 SYN URGP=0 
Jul 31 14:46:47 localhost kernel: [15843001.079903] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=31.163.186.28 DST=[mungedIP2] LEN=40 TOS=0x00 PREC=0x00 TTL=53 ID=46682 PROTO=TCP SPT=27311 DPT=37215 WINDOW=29111 RES=0x00 SYN URGP=0 
Jul 31 14:46:47 localhost kernel: [15843001.079931] iptables_INPUT_denied: IN=eth0 OUT= MAC=f2:3c:91:84:83:95:84:78:ac:57:a8:41:08:00 SRC=31.163.186.28 DST=[mungedIP2] LEN=40 TOS=0x0
2019-08-01 05:38:01
140.143.183.71 attack
Jul 31 17:52:18 debian sshd\[19191\]: Invalid user mb from 140.143.183.71 port 34496
Jul 31 17:52:18 debian sshd\[19191\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.183.71
Jul 31 17:52:20 debian sshd\[19191\]: Failed password for invalid user mb from 140.143.183.71 port 34496 ssh2
...
2019-08-01 05:55:45
198.57.247.209 attackbots
Probing for vulnerable PHP code /5tgvr4r9.php
2019-08-01 06:16:48
218.5.244.218 attack
Jun 28 15:47:05 dallas01 sshd[7573]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.5.244.218
Jun 28 15:47:07 dallas01 sshd[7573]: Failed password for invalid user unreal from 218.5.244.218 port 32215 ssh2
Jun 28 15:48:33 dallas01 sshd[7682]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.5.244.218
Jun 28 15:48:35 dallas01 sshd[7682]: Failed password for invalid user pk from 218.5.244.218 port 38614 ssh2
2019-08-01 06:04:14
188.254.0.112 attackspambots
SSH authentication failure x 6 reported by Fail2Ban
...
2019-08-01 05:51:09

Recently Reported IPs

104.21.81.28 104.21.81.32 104.21.81.30 104.21.81.37
104.21.81.35 104.21.81.40 104.21.81.4 104.21.81.44
104.21.81.39 104.21.81.41 104.21.81.46 104.21.81.45
104.21.81.48 104.21.81.49 104.21.81.5 104.21.81.52
104.21.81.50 104.21.81.53 104.21.81.55 104.21.81.54