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

;; QUESTION SECTION:
;104.22.57.104.			IN	A

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

;; Query time: 57 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 20 21:41:58 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 104.57.22.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 104.57.22.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
176.107.187.151 attackbotsspam
Automatic report - Banned IP Access
2020-10-05 08:08:03
186.229.64.128 attackspam
 TCP (SYN) 186.229.64.128:53301 -> port 445, len 52
2020-10-05 12:03:55
220.85.104.202 attackbots
Ssh brute force
2020-10-05 12:19:57
2.57.122.186 attackbots
SSHD brute force attack detected by fail2ban
2020-10-05 12:13:13
103.119.58.28 attack
20/10/4@16:41:46: FAIL: Alarm-Telnet address from=103.119.58.28
...
2020-10-05 12:14:50
49.235.221.66 attackbotsspam
SSH Bruteforce Attempt on Honeypot
2020-10-05 12:15:12
142.93.122.207 attack
Automatic report - Banned IP Access
2020-10-05 08:05:38
61.110.143.248 attackspambots
 TCP (SYN) 61.110.143.248:32999 -> port 8080, len 40
2020-10-05 12:12:48
187.101.140.232 attack
445/tcp 1433/tcp...
[2020-08-28/10-04]7pkt,2pt.(tcp)
2020-10-05 12:08:34
52.167.169.102 attack
Port Scan: TCP/80
2020-10-05 08:11:33
167.71.237.128 attackbots
(sshd) Failed SSH login from 167.71.237.128 (IN/India/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct  4 14:21:19 optimus sshd[18283]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.237.128  user=root
Oct  4 14:21:21 optimus sshd[18283]: Failed password for root from 167.71.237.128 port 52898 ssh2
Oct  4 14:22:40 optimus sshd[18769]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.237.128  user=root
Oct  4 14:22:42 optimus sshd[18769]: Failed password for root from 167.71.237.128 port 41344 ssh2
Oct  4 14:24:07 optimus sshd[19419]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.237.128  user=root
2020-10-05 08:04:39
103.82.14.144 attack
Listed on    abuseat.org plus zen-spamhaus   / proto=6  .  srcport=41165  .  dstport=23 Telnet  .     (2176)
2020-10-05 07:58:01
113.94.85.201 attack
Port probing on unauthorized port 23
2020-10-05 08:01:57
112.85.42.237 attack
Oct  4 19:54:00 NPSTNNYC01T sshd[11932]: Failed password for root from 112.85.42.237 port 11333 ssh2
Oct  4 19:54:48 NPSTNNYC01T sshd[12064]: Failed password for root from 112.85.42.237 port 21468 ssh2
Oct  4 19:54:50 NPSTNNYC01T sshd[12064]: Failed password for root from 112.85.42.237 port 21468 ssh2
...
2020-10-05 08:08:45
49.228.176.222 attack
23/tcp
[2020-10-03]1pkt
2020-10-05 08:09:15

Recently Reported IPs

176.28.238.118 104.22.57.128 104.22.57.129 104.22.57.144
104.22.57.147 104.22.57.156 104.22.57.167 252.56.225.10
104.22.57.193 104.22.57.210 104.22.57.230 104.22.57.237
104.22.57.244 104.22.57.249 104.22.57.251 104.22.57.89
104.22.58.108 104.22.58.110 104.22.61.93 104.22.62.111