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

;; QUESTION SECTION:
;104.21.57.118.			IN	A

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

;; Query time: 73 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 00:29:07 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 118.57.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 118.57.21.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
162.247.73.192 attackspambots
Jun 24 01:03:17 risk sshd[20148]: Failed password for r.r from 162.247.73.192 port 34384 ssh2
Jun 24 01:03:20 risk sshd[20148]: Failed password for r.r from 162.247.73.192 port 34384 ssh2
Jun 24 01:03:23 risk sshd[20148]: Failed password for r.r from 162.247.73.192 port 34384 ssh2
Jun 24 01:03:25 risk sshd[20148]: Failed password for r.r from 162.247.73.192 port 34384 ssh2
Jun 24 01:03:28 risk sshd[20148]: Failed password for r.r from 162.247.73.192 port 34384 ssh2
Jun 24 01:03:30 risk sshd[20148]: Failed password for r.r from 162.247.73.192 port 34384 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=162.247.73.192
2019-06-24 10:15:52
36.81.203.108 attackspam
port scan and connect, tcp 80 (http)
2019-06-24 09:49:05
89.44.32.18 attackspam
Automatic report - Web App Attack
2019-06-24 09:53:36
191.37.32.7 attack
DATE:2019-06-23 21:55:07, IP:191.37.32.7, PORT:telnet - Telnet brute force auth on a honeypot server (epe-dc)
2019-06-24 10:02:52
216.218.206.67 attackbots
GET / HTTP/1.1
2019-06-24 09:45:39
106.13.3.214 attackbotsspam
Jun 23 22:18:43 dedicated sshd[27669]: Invalid user willy from 106.13.3.214 port 44906
Jun 23 22:18:46 dedicated sshd[27669]: Failed password for invalid user willy from 106.13.3.214 port 44906 ssh2
Jun 23 22:18:43 dedicated sshd[27669]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.3.214
Jun 23 22:18:43 dedicated sshd[27669]: Invalid user willy from 106.13.3.214 port 44906
Jun 23 22:18:46 dedicated sshd[27669]: Failed password for invalid user willy from 106.13.3.214 port 44906 ssh2
2019-06-24 09:51:59
210.212.251.186 attackbotsspam
19/6/23@15:56:17: FAIL: Alarm-Intrusion address from=210.212.251.186
...
2019-06-24 09:48:10
119.3.247.96 attackbots
Malicious brute force vulnerability hacking attacks
2019-06-24 10:18:22
187.111.152.149 attackspam
23.06.2019 21:53:05 - Login Fail on hMailserver 
Detected by ELinOX-hMail-A2F
2019-06-24 10:27:32
150.95.54.141 attackspam
Brute force attempt
2019-06-24 09:52:23
179.32.1.90 attack
Jun 23 21:56:07 web02 sshd\[22412\]: Invalid user pi from 179.32.1.90 port 35862
Jun 23 21:56:07 web02 sshd\[22410\]: Invalid user pi from 179.32.1.90 port 35858
...
2019-06-24 09:49:59
77.247.110.194 attack
SIP Server BruteForce Attack
2019-06-24 09:50:45
100.43.91.113 attackbotsspam
port scan and connect, tcp 443 (https)
2019-06-24 09:44:01
184.105.247.243 attackbotsspam
¯\_(ツ)_/¯
2019-06-24 10:27:52
91.236.116.214 attackspam
Jun 24 01:03:18 *** sshd[18254]: Invalid user 0 from 91.236.116.214
2019-06-24 10:20:18

Recently Reported IPs

104.21.57.116 16.206.25.8 104.21.57.12 104.21.57.123
104.21.57.124 104.21.57.125 104.21.57.127 104.21.57.133
104.21.57.136 104.21.57.137 104.21.57.138 104.21.57.139
104.21.57.14 104.21.57.140 104.21.57.142 230.118.11.39
104.21.57.144 104.21.57.15 104.21.57.151 104.21.57.152