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

;; QUESTION SECTION:
;104.18.20.157.			IN	A

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

;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 14:35:01 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 157.20.18.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 157.20.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
162.241.216.164 attack
+union+all+select+1,1,1,1,1,1,1,CONCAT(0x3a6f79753a,0x4244764877697569706b,0x3a70687a3a)%23
2020-04-21 18:25:00
80.211.52.58 attack
Invalid user fp from 80.211.52.58 port 36764
2020-04-21 18:15:46
106.124.131.194 attack
2020-04-21T06:52:37.342900librenms sshd[16481]: Invalid user admin from 106.124.131.194 port 56756
2020-04-21T06:52:39.142566librenms sshd[16481]: Failed password for invalid user admin from 106.124.131.194 port 56756 ssh2
2020-04-21T06:58:45.453180librenms sshd[16984]: Invalid user of from 106.124.131.194 port 34247
...
2020-04-21 18:23:29
83.159.194.187 attackbots
2020-04-20 UTC: (8x) - admin,di,kb,kt,root(2x),test01,tester
2020-04-21 18:27:22
119.29.216.238 attackspambots
2020-04-20 UTC: (2x) - ,root
2020-04-21 18:35:07
113.160.205.222 attackbotsspam
20/4/20@23:49:33: FAIL: IoT-SSH address from=113.160.205.222
...
2020-04-21 18:46:50
72.167.190.154 attackbots
xmlrpc attack
2020-04-21 18:10:08
175.24.57.194 attackbotsspam
$f2bV_matches
2020-04-21 18:43:38
125.24.144.59 attackspambots
20/4/21@00:56:14: FAIL: Alarm-Network address from=125.24.144.59
...
2020-04-21 18:44:02
213.85.40.69 attackspambots
Apr 21 11:45:09 roki sshd[18448]: refused connect from 213.85.40.69 (213.85.40.69)
Apr 21 11:45:49 roki sshd[18496]: refused connect from 213.85.40.69 (213.85.40.69)
Apr 21 11:45:57 roki sshd[18505]: refused connect from 213.85.40.69 (213.85.40.69)
Apr 21 11:46:06 roki sshd[18515]: refused connect from 213.85.40.69 (213.85.40.69)
Apr 21 11:46:14 roki sshd[18525]: refused connect from 213.85.40.69 (213.85.40.69)
...
2020-04-21 18:34:00
106.13.173.12 attack
SSH brute-force: detected 10 distinct usernames within a 24-hour window.
2020-04-21 18:18:16
195.190.132.246 attack
Invalid user admin2 from 195.190.132.246 port 49989
2020-04-21 18:22:34
14.157.14.188 attackbots
Unauthorized connection attempt detected from IP address 14.157.14.188 to port 23 [T]
2020-04-21 18:36:25
123.206.36.174 attack
Apr 20 19:52:52 wbs sshd\[29377\]: Invalid user mb from 123.206.36.174
Apr 20 19:52:52 wbs sshd\[29377\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.206.36.174
Apr 20 19:52:54 wbs sshd\[29377\]: Failed password for invalid user mb from 123.206.36.174 port 46586 ssh2
Apr 20 19:56:08 wbs sshd\[29611\]: Invalid user pg from 123.206.36.174
Apr 20 19:56:08 wbs sshd\[29611\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.206.36.174
2020-04-21 18:31:09
195.154.42.43 attack
Invalid user firefart from 195.154.42.43 port 45772
2020-04-21 18:42:26

Recently Reported IPs

104.18.20.155 104.18.20.158 104.18.20.187 104.18.20.188
104.18.20.2 78.110.30.34 104.18.20.203 104.18.20.208
104.18.20.212 104.18.20.230 104.18.20.236 104.18.20.238
104.18.20.244 104.18.20.248 104.18.20.34 93.131.87.55
104.18.20.51 104.18.20.6 171.171.47.9 104.18.20.65