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

;; QUESTION SECTION:
;104.21.49.131.			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:21 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 131.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 131.49.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
39.153.89.10 attackbotsspam
Unauthorised access (Nov 24) SRC=39.153.89.10 LEN=40 TTL=48 ID=12237 TCP DPT=23 WINDOW=54688 SYN
2019-11-25 04:41:23
222.169.185.234 attackspam
Nov 24 06:57:07 web1 sshd\[8952\]: Invalid user gadsby from 222.169.185.234
Nov 24 06:57:07 web1 sshd\[8952\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.169.185.234
Nov 24 06:57:10 web1 sshd\[8952\]: Failed password for invalid user gadsby from 222.169.185.234 port 39546 ssh2
Nov 24 07:01:33 web1 sshd\[9350\]: Invalid user steinum from 222.169.185.234
Nov 24 07:01:33 web1 sshd\[9350\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.169.185.234
2019-11-25 04:31:49
159.203.13.141 attackbotsspam
Nov 24 21:15:35 ns382633 sshd\[28870\]: Invalid user dewald from 159.203.13.141 port 36736
Nov 24 21:15:35 ns382633 sshd\[28870\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.13.141
Nov 24 21:15:37 ns382633 sshd\[28870\]: Failed password for invalid user dewald from 159.203.13.141 port 36736 ssh2
Nov 24 21:31:52 ns382633 sshd\[31766\]: Invalid user torheim from 159.203.13.141 port 41766
Nov 24 21:31:52 ns382633 sshd\[31766\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.13.141
2019-11-25 04:47:24
110.77.136.66 attackbotsspam
Nov 24 21:50:58 gw1 sshd[19820]: Failed password for root from 110.77.136.66 port 64556 ssh2
...
2019-11-25 04:53:23
92.118.38.38 attackbots
Nov 24 21:52:01 andromeda postfix/smtpd\[22233\]: warning: unknown\[92.118.38.38\]: SASL LOGIN authentication failed: authentication failure
Nov 24 21:52:13 andromeda postfix/smtpd\[22183\]: warning: unknown\[92.118.38.38\]: SASL LOGIN authentication failed: authentication failure
Nov 24 21:52:33 andromeda postfix/smtpd\[22183\]: warning: unknown\[92.118.38.38\]: SASL LOGIN authentication failed: authentication failure
Nov 24 21:52:36 andromeda postfix/smtpd\[22233\]: warning: unknown\[92.118.38.38\]: SASL LOGIN authentication failed: authentication failure
Nov 24 21:52:48 andromeda postfix/smtpd\[22183\]: warning: unknown\[92.118.38.38\]: SASL LOGIN authentication failed: authentication failure
2019-11-25 04:55:29
58.187.173.88 attackbotsspam
Unauthorized connection attempt from IP address 58.187.173.88 on Port 445(SMB)
2019-11-25 04:55:58
103.66.16.18 attackspam
SSH bruteforce (Triggered fail2ban)
2019-11-25 04:46:11
119.81.240.155 attack
Invalid user redmine from 119.81.240.155 port 44613
2019-11-25 04:47:54
92.46.110.2 attackbotsspam
Unauthorized connection attempt from IP address 92.46.110.2 on Port 445(SMB)
2019-11-25 04:59:23
159.203.82.201 attack
WordPress login Brute force / Web App Attack on client site.
2019-11-25 04:50:18
60.199.133.71 attack
RDP Bruteforce
2019-11-25 04:51:22
122.166.237.117 attack
Nov 24 18:33:47 *** sshd[11412]: User root from 122.166.237.117 not allowed because not listed in AllowUsers
2019-11-25 04:40:01
49.88.112.74 attackspam
Nov 24 20:55:03 MK-Soft-VM4 sshd[26358]: Failed password for root from 49.88.112.74 port 42004 ssh2
Nov 24 20:55:06 MK-Soft-VM4 sshd[26358]: Failed password for root from 49.88.112.74 port 42004 ssh2
...
2019-11-25 04:22:55
222.127.53.107 attack
Nov 24 05:31:38 hanapaa sshd\[4668\]: Invalid user shell from 222.127.53.107
Nov 24 05:31:38 hanapaa sshd\[4668\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.127.53.107
Nov 24 05:31:40 hanapaa sshd\[4668\]: Failed password for invalid user shell from 222.127.53.107 port 49852 ssh2
Nov 24 05:40:50 hanapaa sshd\[5478\]: Invalid user admin from 222.127.53.107
Nov 24 05:40:50 hanapaa sshd\[5478\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.127.53.107
2019-11-25 05:03:15
106.75.87.152 attack
SSH Brute-Force reported by Fail2Ban
2019-11-25 04:41:50

Recently Reported IPs

104.21.49.124 104.21.49.13 104.21.49.11 104.21.48.95
104.21.49.135 104.21.49.145 104.21.49.14 104.21.49.146
104.21.49.143 104.21.49.150 104.21.49.154 104.21.49.147
104.21.49.139 104.21.49.138 104.21.49.162 104.21.49.151
104.21.49.152 104.21.7.17 104.21.49.168 104.21.49.163