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

;; QUESTION SECTION:
;104.196.234.21.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Mar 20 16:28:58 CST 2022
;; MSG SIZE  rcvd: 107
Host info
21.234.196.104.in-addr.arpa domain name pointer 21.234.196.104.bc.googleusercontent.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
21.234.196.104.in-addr.arpa	name = 21.234.196.104.bc.googleusercontent.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
195.154.38.177 attack
detected by Fail2Ban
2019-11-04 03:19:04
14.231.60.114 attack
Unauthorized connection attempt from IP address 14.231.60.114 on Port 445(SMB)
2019-11-04 03:18:08
45.226.81.197 attackbots
$f2bV_matches
2019-11-04 02:42:17
177.40.243.19 attackbotsspam
Fail2Ban Ban Triggered
2019-11-04 02:51:25
91.207.40.42 attack
$f2bV_matches
2019-11-04 02:56:14
46.38.144.202 attackbotsspam
2019-11-03T19:58:06.445167mail01 postfix/smtpd[7566]: warning: unknown[46.38.144.202]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-11-03T19:58:31.261345mail01 postfix/smtpd[14666]: warning: unknown[46.38.144.202]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-11-03T19:58:52.240452mail01 postfix/smtpd[7566]: warning: unknown[46.38.144.202]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-11-04 03:00:15
54.37.154.113 attackbotsspam
2019-11-03T18:36:05.972484scmdmz1 sshd\[24439\]: Invalid user shaker from 54.37.154.113 port 56382
2019-11-03T18:36:05.975216scmdmz1 sshd\[24439\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.ip-54-37-154.eu
2019-11-03T18:36:07.537755scmdmz1 sshd\[24439\]: Failed password for invalid user shaker from 54.37.154.113 port 56382 ssh2
...
2019-11-04 02:52:36
223.12.7.249 attackspam
Telnet Server BruteForce Attack
2019-11-04 03:10:01
156.210.5.194 attackbots
ENG,WP GET /wp-login.php
2019-11-04 03:18:41
159.89.162.118 attackbots
Nov  3 16:34:45 ArkNodeAT sshd\[27553\]: Invalid user postgresql from 159.89.162.118
Nov  3 16:34:45 ArkNodeAT sshd\[27553\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.162.118
Nov  3 16:34:46 ArkNodeAT sshd\[27553\]: Failed password for invalid user postgresql from 159.89.162.118 port 38630 ssh2
2019-11-04 03:13:59
51.158.112.242 attackbotsspam
Port scan on 1 port(s): 23
2019-11-04 02:58:53
78.128.112.14 attackspambots
78.128.112.14 was recorded 21 times by 2 hosts attempting to connect to the following ports: 1212,33893,3399,1101,3396,5000,2005,23389,3400,10000,5050,2041,3383,33390,5557,8890,1976,3398,444,33890. Incident counter (4h, 24h, all-time): 21, 104, 251
2019-11-04 02:43:51
185.156.73.31 attack
ET DROP Dshield Block Listed Source group 1 - port: 26717 proto: TCP cat: Misc Attack
2019-11-04 02:52:57
1.63.226.147 attack
SSH/22 MH Probe, BF, Hack -
2019-11-04 03:24:05
193.70.114.154 attackspam
Automatic report - Banned IP Access
2019-11-04 03:12:40

Recently Reported IPs

104.196.233.41 15.50.96.55 104.196.248.212 104.196.29.22
104.196.31.40 104.196.35.246 104.196.35.30 104.196.36.116
104.196.54.235 104.196.60.137 104.196.61.133 104.196.96.92
104.196.99.212 104.197.101.35 104.197.102.170 159.244.147.252
104.197.112.123 104.197.120.235 104.197.133.124 104.197.140.254