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

;; QUESTION SECTION:
;104.21.49.44.			IN	A

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

;; Query time: 62 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 02:33:47 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 44.49.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 44.49.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
45.141.87.31 attackbotsspam
RDP Bruteforce
2020-04-23 07:46:29
45.225.216.80 attackspam
(sshd) Failed SSH login from 45.225.216.80 (AR/Argentina/host-80-216-225-45-lincon.net.ar): 5 in the last 3600 secs
2020-04-23 07:32:12
192.141.192.26 attackspambots
Invalid user test from 192.141.192.26 port 34966
2020-04-23 07:13:05
180.101.125.226 attack
Invalid user test from 180.101.125.226 port 42224
2020-04-23 07:29:56
222.239.28.177 attackbotsspam
Invalid user nx from 222.239.28.177 port 60088
2020-04-23 07:41:16
49.234.207.226 attack
Invalid user test from 49.234.207.226 port 39476
2020-04-23 07:19:50
115.159.65.195 attackbots
Invalid user ftpadmin from 115.159.65.195 port 34378
2020-04-23 07:29:06
180.76.234.89 attackbotsspam
Invalid user ftpuser from 180.76.234.89 port 40888
2020-04-23 07:28:11
187.157.135.152 attackspam
Invalid user yn from 187.157.135.152 port 35266
2020-04-23 07:12:40
167.71.254.95 attackspam
run attacks on the service SSH
2020-04-23 07:35:06
134.122.69.200 attack
Apr 23 00:52:37 host sshd[30579]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.69.200  user=root
Apr 23 00:52:39 host sshd[30579]: Failed password for root from 134.122.69.200 port 54242 ssh2
...
2020-04-23 07:23:59
190.196.64.93 attackspambots
Apr 23 00:48:16 lukav-desktop sshd\[17074\]: Invalid user admin from 190.196.64.93
Apr 23 00:48:16 lukav-desktop sshd\[17074\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.196.64.93
Apr 23 00:48:17 lukav-desktop sshd\[17074\]: Failed password for invalid user admin from 190.196.64.93 port 50502 ssh2
Apr 23 00:56:33 lukav-desktop sshd\[17456\]: Invalid user al from 190.196.64.93
Apr 23 00:56:33 lukav-desktop sshd\[17456\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.196.64.93
2020-04-23 07:12:15
203.147.72.106 attackspam
failed_logins
2020-04-23 07:13:32
27.155.65.3 attack
Bruteforce detected by fail2ban
2020-04-23 07:20:09
134.122.73.25 attack
Apr 23 01:34:36 vps sshd[803163]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.73.25
Apr 23 01:34:39 vps sshd[803163]: Failed password for invalid user wq from 134.122.73.25 port 41274 ssh2
Apr 23 01:38:00 vps sshd[821307]: Invalid user zh from 134.122.73.25 port 44508
Apr 23 01:38:00 vps sshd[821307]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.73.25
Apr 23 01:38:02 vps sshd[821307]: Failed password for invalid user zh from 134.122.73.25 port 44508 ssh2
...
2020-04-23 07:42:54

Recently Reported IPs

104.21.49.62 104.21.49.65 104.21.49.63 104.21.49.66
104.21.49.56 104.21.7.177 104.21.49.67 104.21.49.68
104.21.49.7 104.21.49.69 104.21.49.78 104.21.49.8
104.21.7.179 104.21.49.81 104.21.49.77 104.21.49.74
104.21.49.87 104.21.49.83 104.21.49.93 104.21.49.89