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

;; QUESTION SECTION:
;104.21.12.171.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 20 19:29:05 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 171.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 171.12.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
178.62.117.106 attackbotsspam
2020-03-25T07:20:41.043239vps773228.ovh.net sshd[24184]: Invalid user you from 178.62.117.106 port 49795
2020-03-25T07:20:41.054152vps773228.ovh.net sshd[24184]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.117.106
2020-03-25T07:20:41.043239vps773228.ovh.net sshd[24184]: Invalid user you from 178.62.117.106 port 49795
2020-03-25T07:20:43.113266vps773228.ovh.net sshd[24184]: Failed password for invalid user you from 178.62.117.106 port 49795 ssh2
2020-03-25T07:24:57.403791vps773228.ovh.net sshd[25767]: Invalid user claudia from 178.62.117.106 port 57403
...
2020-03-25 14:54:43
222.186.31.127 attackspambots
[MK-VM6] SSH login failed
2020-03-25 14:45:18
159.89.1.19 attack
Automatic report - XMLRPC Attack
2020-03-25 14:38:46
219.148.39.134 attack
CMS (WordPress or Joomla) login attempt.
2020-03-25 14:44:38
185.6.172.152 attack
Invalid user juham from 185.6.172.152 port 39794
2020-03-25 14:44:03
115.159.51.239 attackbots
Invalid user if from 115.159.51.239 port 52972
2020-03-25 14:48:24
113.161.54.30 attackbots
Mar 25 07:45:26 host01 sshd[22684]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.161.54.30 
Mar 25 07:45:27 host01 sshd[22684]: Failed password for invalid user bou from 113.161.54.30 port 33830 ssh2
Mar 25 07:49:43 host01 sshd[23483]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.161.54.30 
...
2020-03-25 15:00:43
185.165.168.229 attackspam
Mar 25 07:42:39 vpn01 sshd[19874]: Failed password for root from 185.165.168.229 port 40769 ssh2
Mar 25 07:42:41 vpn01 sshd[19874]: Failed password for root from 185.165.168.229 port 40769 ssh2
...
2020-03-25 15:10:59
69.163.225.129 attackspam
$f2bV_matches
2020-03-25 14:40:01
58.56.164.166 attackbotsspam
SSH Login Bruteforce
2020-03-25 14:43:00
186.234.80.17 attackspambots
Automatic report - XMLRPC Attack
2020-03-25 15:08:50
106.54.201.240 attackspam
DATE:2020-03-25 08:13:00, IP:106.54.201.240, PORT:ssh SSH brute force auth (docker-dc)
2020-03-25 15:14:07
104.225.159.30 attack
$f2bV_matches
2020-03-25 14:35:18
178.128.255.8 attackbotsspam
SSH brute-force: detected 17 distinct usernames within a 24-hour window.
2020-03-25 15:03:18
31.184.198.75 attackbotsspam
SSH Brute-Force reported by Fail2Ban
2020-03-25 15:07:36

Recently Reported IPs

104.21.12.191 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 104.18.19.14 104.21.14.58 104.21.15.108