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

;; QUESTION SECTION:
;104.21.12.168.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 20 19:29:04 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 168.12.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 168.12.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
120.131.6.144 attack
SSH bruteforce (Triggered fail2ban)
2019-12-14 00:35:55
145.239.91.88 attackspam
$f2bV_matches
2019-12-14 00:57:29
129.146.147.62 attack
2019-12-13T15:52:18.600073abusebot.cloudsearch.cf sshd\[6032\]: Invalid user jdk300 from 129.146.147.62 port 53014
2019-12-13T15:52:18.606851abusebot.cloudsearch.cf sshd\[6032\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.146.147.62
2019-12-13T15:52:20.212227abusebot.cloudsearch.cf sshd\[6032\]: Failed password for invalid user jdk300 from 129.146.147.62 port 53014 ssh2
2019-12-13T15:59:23.901263abusebot.cloudsearch.cf sshd\[6126\]: Invalid user uucp from 129.146.147.62 port 45884
2019-12-14 00:57:55
165.254.255.132 attackbotsspam
46654/tcp
[2019-12-13]1pkt
2019-12-14 00:34:05
95.46.136.53 attackspam
3389/tcp
[2019-12-13]1pkt
2019-12-14 00:41:33
94.25.229.122 attackspam
Unauthorized connection attempt detected from IP address 94.25.229.122 to port 445
2019-12-14 00:34:40
164.132.53.185 attackspambots
Dec 13 17:36:28 meumeu sshd[15081]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.53.185 
Dec 13 17:36:30 meumeu sshd[15081]: Failed password for invalid user candelaria from 164.132.53.185 port 47094 ssh2
Dec 13 17:41:42 meumeu sshd[16086]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.53.185 
...
2019-12-14 00:43:28
58.248.254.124 attackbotsspam
Dec 13 11:24:52 TORMINT sshd\[13137\]: Invalid user toor from 58.248.254.124
Dec 13 11:24:52 TORMINT sshd\[13137\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.248.254.124
Dec 13 11:24:54 TORMINT sshd\[13137\]: Failed password for invalid user toor from 58.248.254.124 port 39276 ssh2
...
2019-12-14 00:35:06
122.227.224.10 attackbots
Dec 13 16:58:15 mail sshd\[16752\]: Invalid user admin from 122.227.224.10
Dec 13 16:58:15 mail sshd\[16752\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.227.224.10
Dec 13 16:58:17 mail sshd\[16752\]: Failed password for invalid user admin from 122.227.224.10 port 26660 ssh2
...
2019-12-14 00:52:34
89.134.126.89 attack
Dec 13 17:41:17 ns41 sshd[3060]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.134.126.89
Dec 13 17:41:17 ns41 sshd[3060]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.134.126.89
2019-12-14 00:46:21
217.182.172.204 attackbots
Dec 13 17:26:35 sd-53420 sshd\[1758\]: Invalid user nologin from 217.182.172.204
Dec 13 17:26:35 sd-53420 sshd\[1758\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.182.172.204
Dec 13 17:26:37 sd-53420 sshd\[1758\]: Failed password for invalid user nologin from 217.182.172.204 port 51316 ssh2
Dec 13 17:31:52 sd-53420 sshd\[2127\]: Invalid user vote from 217.182.172.204
Dec 13 17:31:52 sd-53420 sshd\[2127\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.182.172.204
...
2019-12-14 00:38:55
218.92.0.191 attack
Dec 13 17:15:56 dcd-gentoo sshd[7364]: User root from 218.92.0.191 not allowed because none of user's groups are listed in AllowGroups
Dec 13 17:15:58 dcd-gentoo sshd[7364]: error: PAM: Authentication failure for illegal user root from 218.92.0.191
Dec 13 17:15:56 dcd-gentoo sshd[7364]: User root from 218.92.0.191 not allowed because none of user's groups are listed in AllowGroups
Dec 13 17:15:58 dcd-gentoo sshd[7364]: error: PAM: Authentication failure for illegal user root from 218.92.0.191
Dec 13 17:15:56 dcd-gentoo sshd[7364]: User root from 218.92.0.191 not allowed because none of user's groups are listed in AllowGroups
Dec 13 17:15:58 dcd-gentoo sshd[7364]: error: PAM: Authentication failure for illegal user root from 218.92.0.191
Dec 13 17:15:58 dcd-gentoo sshd[7364]: Failed keyboard-interactive/pam for invalid user root from 218.92.0.191 port 31254 ssh2
...
2019-12-14 00:25:14
111.42.102.134 attack
5060/udp
[2019-12-13]1pkt
2019-12-14 00:53:02
103.76.170.106 attack
445/tcp 445/tcp 445/tcp
[2019-12-13]3pkt
2019-12-14 01:04:42
103.44.2.98 attackbots
IP was detected trying to Brute-Force SSH, FTP, Web Apps, Port-Scan or Hacking.
2019-12-14 00:56:54

Recently Reported IPs

104.21.12.198 104.21.12.156 104.21.12.191 104.21.12.171
104.21.12.203 104.18.19.112 104.21.12.19 104.21.12.208
104.21.12.251 104.21.12.153 104.21.12.253 104.21.12.233
104.18.19.118 104.21.12.234 104.21.12.220 104.21.12.41
104.21.12.32 252.11.71.123 104.18.19.127 104.18.19.129