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

;; QUESTION SECTION:
;104.21.196.2.			IN	A

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

;; Query time: 125 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Mar 14 18:43:36 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 2.196.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 2.196.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
86.30.243.212 attack
Nov 10 08:54:41 dedicated sshd[23882]: Invalid user cxh from 86.30.243.212 port 53668
2019-11-10 15:56:54
49.235.209.223 attackbotsspam
2019-11-10T08:25:04.537219scmdmz1 sshd\[4801\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.209.223  user=root
2019-11-10T08:25:05.983647scmdmz1 sshd\[4801\]: Failed password for root from 49.235.209.223 port 40026 ssh2
2019-11-10T08:29:33.349240scmdmz1 sshd\[5121\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.209.223  user=root
...
2019-11-10 15:48:25
189.112.109.189 attackbots
Nov 10 06:42:13 *** sshd[19626]: User root from 189.112.109.189 not allowed because not listed in AllowUsers
2019-11-10 15:19:01
106.3.147.213 attackspambots
Nov 10 07:26:22 sd-53420 sshd\[27931\]: User root from 106.3.147.213 not allowed because none of user's groups are listed in AllowGroups
Nov 10 07:26:22 sd-53420 sshd\[27931\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.3.147.213  user=root
Nov 10 07:26:24 sd-53420 sshd\[27931\]: Failed password for invalid user root from 106.3.147.213 port 38662 ssh2
Nov 10 07:32:11 sd-53420 sshd\[29552\]: Invalid user kxso from 106.3.147.213
Nov 10 07:32:11 sd-53420 sshd\[29552\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.3.147.213
...
2019-11-10 15:36:41
106.13.128.71 attackbots
Nov 10 12:14:26 gw1 sshd[8830]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.128.71
Nov 10 12:14:28 gw1 sshd[8830]: Failed password for invalid user unix123$ from 106.13.128.71 port 43220 ssh2
...
2019-11-10 15:16:29
193.32.160.152 attack
Nov 10 07:31:44 relay postfix/smtpd\[5754\]: NOQUEUE: reject: RCPT from unknown\[193.32.160.152\]: 554 5.7.1 \: Relay access denied\; from=\ to=\ proto=ESMTP helo=\<\[193.32.160.151\]\>
Nov 10 07:31:44 relay postfix/smtpd\[5754\]: NOQUEUE: reject: RCPT from unknown\[193.32.160.152\]: 554 5.7.1 \: Relay access denied\; from=\ to=\ proto=ESMTP helo=\<\[193.32.160.151\]\>
Nov 10 07:31:44 relay postfix/smtpd\[5754\]: NOQUEUE: reject: RCPT from unknown\[193.32.160.152\]: 554 5.7.1 \: Relay access denied\; from=\ to=\ proto=ESMTP helo=\<\[193.32.160.151\]\>
Nov 10 07:31:44 relay postfix/smtpd\[5754\]: NOQUEUE: reject: RCPT from unknown\[193.32.160.152\]: 554 5.7.1 \: Relay access denied\; from=\
2019-11-10 15:41:30
151.40.209.27 attack
Automatic report - Port Scan Attack
2019-11-10 15:54:36
47.247.147.60 attack
Port scan on 1 port(s): 445
2019-11-10 15:59:43
60.250.149.19 attack
Automatic report - SSH Brute-Force Attack
2019-11-10 15:58:04
178.62.54.233 attack
2019-11-10T07:02:23.152302abusebot-2.cloudsearch.cf sshd\[16827\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.54.233  user=root
2019-11-10 15:43:24
185.176.27.102 attack
185.176.27.102 was recorded 26 times by 15 hosts attempting to connect to the following ports: 5494,5587,5588,5586. Incident counter (4h, 24h, all-time): 26, 117, 649
2019-11-10 15:42:23
154.91.32.166 attack
Unauthorised access (Nov 10) SRC=154.91.32.166 LEN=40 TOS=0x08 PREC=0x20 TTL=235 ID=31489 TCP DPT=1433 WINDOW=1024 SYN
2019-11-10 15:30:48
210.245.8.110 attackbots
Automatic report - XMLRPC Attack
2019-11-10 15:51:52
193.31.24.113 attackbots
11/10/2019-08:33:07.584816 193.31.24.113 Protocol: 6 SURICATA SMTP tls rejected
2019-11-10 15:41:54
46.38.144.57 attackbotsspam
Nov 10 08:23:13 relay postfix/smtpd\[27256\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 10 08:23:29 relay postfix/smtpd\[3073\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 10 08:23:50 relay postfix/smtpd\[32464\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 10 08:24:08 relay postfix/smtpd\[3851\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 10 08:24:27 relay postfix/smtpd\[32464\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-11-10 15:39:31

Recently Reported IPs

104.21.118.69 104.21.201.233 104.21.201.76 104.21.204.206
104.21.207.127 104.21.207.235 104.21.209.197 104.21.215.142
104.21.223.62 104.21.224.11 104.21.226.107 104.21.228.103
104.21.228.12 104.22.1.120 104.22.1.14 104.22.1.20
104.22.1.207 104.22.1.221 104.22.1.36 104.22.1.55