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

;; QUESTION SECTION:
;104.21.52.196.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 10:12:39 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 196.52.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 196.52.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
51.158.21.170 attackspam
CloudCIX Reconnaissance Scan Detected, PTR: 51-158-21-170.rev.poneytelecom.eu.
2019-11-21 08:54:21
198.23.223.139 attack
CloudCIX Reconnaissance Scan Detected, PTR: 198-23-223-139-host.colocrossing.com.
2019-11-21 08:56:29
63.88.23.235 attackbotsspam
63.88.23.235 was recorded 10 times by 7 hosts attempting to connect to the following ports: 80. Incident counter (4h, 24h, all-time): 10, 84, 418
2019-11-21 13:13:51
185.143.223.146 attack
Port scan on 13 port(s): 10 222 1000 3381 3392 3395 4000 14000 18000 20000 22000 27000 60000
2019-11-21 08:44:56
111.42.88.248 attackspambots
REQUESTED PAGE: /TP/public/index.php
2019-11-21 08:53:38
92.118.37.86 attackbots
92.118.37.86 was recorded 136 times by 34 hosts attempting to connect to the following ports: 127,577,155,163,44,714,711,210,559,23,518,422,617,238,979,751,739,263,707,628,748,566,504,129,510,891,345,986,285,731,514,332,251,443,390,747,745,520,560,630,183,703,726,147,803,983,160,165,140,197,89,878,847,203,631,85,414,427,636,76,539,329,840,779,261,327,206,730,998,775,284,136,627,470,277,695,975,732,473,511,288,283,797,429,716,818,644,215,350,875,794,93,611,736,681,256,727,143,300,52,486,813,157,266,708,746,278,176,792,154,709,138,131,920,626,755,217. Incident counter (4h, 24h, all-time): 136, 791, 10361
2019-11-21 08:55:35
82.147.220.206 attack
Thu Nov 21 05:56:12 2019 [pid 11599] [anonymous] FAIL LOGIN: Client "82.147.220.206"
Thu Nov 21 05:56:17 2019 [pid 11601] [notgoodbutcrazy] FAIL LOGIN: Client "82.147.220.206"
Thu Nov 21 05:56:21 2019 [pid 11603] [notgoodbutcrazy] FAIL LOGIN: Client "82.147.220.206"
Thu Nov 21 05:56:25 2019 [pid 11605] [www] FAIL LOGIN: Client "82.147.220.206"
Thu Nov 21 05:56:28 2019 [pid 11607] [www] FAIL LOGIN: Client "82.147.220.206"
2019-11-21 13:15:19
176.57.208.195 attack
Multiport scan : 29 ports scanned 1000 2289 3030 3113 3301 3311 3320 3344 3355 3382 3383 3384 3386 4001 6001 6389 7789 8080 9002 9090 9876 9989 10003 10389 33000 33889 33896 45678 54321
2019-11-21 08:50:23
185.156.73.31 attackbotsspam
185.156.73.31 was recorded 26 times by 18 hosts attempting to connect to the following ports: 21231,21230,21229,52453,52454,52455. Incident counter (4h, 24h, all-time): 26, 214, 2250
2019-11-21 08:39:49
178.33.236.23 attackspam
Nov 21 07:32:57 server sshd\[25893\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns328667.ip-178-33-236.eu  user=root
Nov 21 07:32:59 server sshd\[25893\]: Failed password for root from 178.33.236.23 port 49436 ssh2
Nov 21 07:53:12 server sshd\[31040\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns328667.ip-178-33-236.eu  user=operator
Nov 21 07:53:14 server sshd\[31040\]: Failed password for operator from 178.33.236.23 port 60456 ssh2
Nov 21 07:56:28 server sshd\[31990\]: Invalid user frati from 178.33.236.23
Nov 21 07:56:28 server sshd\[31990\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns328667.ip-178-33-236.eu 
...
2019-11-21 13:13:16
125.124.147.117 attack
2019-11-21T04:56:44.019328abusebot-2.cloudsearch.cf sshd\[973\]: Invalid user disc from 125.124.147.117 port 43522
2019-11-21 13:03:49
185.156.73.17 attackbots
11/20/2019-19:00:32.288300 185.156.73.17 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-11-21 08:42:32
46.38.144.146 attackbots
Nov 21 06:19:18 webserver postfix/smtpd\[26563\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 21 06:19:53 webserver postfix/smtpd\[26622\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 21 06:20:31 webserver postfix/smtpd\[26563\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 21 06:21:07 webserver postfix/smtpd\[26622\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 21 06:21:43 webserver postfix/smtpd\[26563\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-11-21 13:21:44
125.64.94.212 attackspambots
20.11.2019 22:56:30 Connection to port 3528 blocked by firewall
2019-11-21 08:51:57
41.93.48.73 attackbots
Nov 21 10:05:33 gw1 sshd[31637]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.93.48.73
Nov 21 10:05:35 gw1 sshd[31637]: Failed password for invalid user hersch from 41.93.48.73 port 55094 ssh2
...
2019-11-21 13:06:53

Recently Reported IPs

104.21.52.17 104.21.52.217 104.21.52.220 104.21.52.214
104.21.52.42 104.21.52.230 104.21.52.32 104.21.52.39
104.21.52.207 104.21.52.43 104.21.52.246 104.21.52.253
13.225.71.30 104.21.52.7 104.21.52.51 13.225.71.31
104.21.52.74 104.21.52.86 104.21.52.85 104.21.52.94