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

;; QUESTION SECTION:
;104.21.43.51.			IN	A

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

;; Query time: 30 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 02:30:26 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 51.43.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 51.43.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
162.243.141.184 attackspam
ET SCAN Zmap User-Agent (zgrab) - port: 80 proto: TCP cat: Detection of a Network Scan
2020-05-03 06:01:31
185.176.27.42 attackspam
05/02/2020-22:49:34.121099 185.176.27.42 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2020-05-03 05:29:56
112.85.42.94 attack
SSH Brute Force
2020-05-03 05:49:49
181.225.44.26 attackspambots
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-03 06:00:34
182.74.25.246 attackspambots
May  2 23:18:53 icinga sshd[62855]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.74.25.246 
May  2 23:18:55 icinga sshd[62855]: Failed password for invalid user andrei from 182.74.25.246 port 1601 ssh2
May  2 23:23:04 icinga sshd[5426]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.74.25.246 
...
2020-05-03 05:30:42
118.70.216.153 attack
May  2 22:58:31 tor-proxy-02 sshd\[1196\]: User root from 118.70.216.153 not allowed because not listed in AllowUsers
May  2 22:58:32 tor-proxy-02 sshd\[1198\]: User root from 118.70.216.153 not allowed because not listed in AllowUsers
May  2 22:58:33 tor-proxy-02 sshd\[1200\]: User root from 118.70.216.153 not allowed because not listed in AllowUsers
...
2020-05-03 05:34:18
157.245.12.36 attack
SSH Invalid Login
2020-05-03 05:47:45
103.94.6.69 attackbots
21 attempts against mh-ssh on cloud
2020-05-03 05:51:20
194.6.231.122 attack
SSH Brute Force
2020-05-03 05:42:48
190.205.59.6 attackspambots
SSH Brute Force
2020-05-03 05:43:35
222.239.28.177 attackbots
May  2 23:32:25 vpn01 sshd[13016]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.239.28.177
May  2 23:32:27 vpn01 sshd[13016]: Failed password for invalid user matriz from 222.239.28.177 port 38684 ssh2
...
2020-05-03 05:40:42
113.87.160.114 attackbots
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-03 06:04:50
111.229.202.53 attackspam
May  2 18:24:01 vps46666688 sshd[7037]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.202.53
May  2 18:24:02 vps46666688 sshd[7037]: Failed password for invalid user test from 111.229.202.53 port 60250 ssh2
...
2020-05-03 05:34:49
151.80.140.166 attackbots
SSH Brute Force
2020-05-03 05:32:39
177.22.91.247 attackbots
SSH Brute Force
2020-05-03 05:46:36

Recently Reported IPs

104.21.43.38 104.21.43.67 104.21.69.95 104.21.43.36
104.21.43.49 104.21.43.52 104.21.43.64 104.21.43.3
104.21.43.7 104.21.43.76 104.21.43.8 104.21.69.99
104.21.43.74 104.21.43.68 104.21.43.77 104.21.43.93
104.21.43.89 104.21.43.99 104.21.43.71 104.21.44.100