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 of America (the)

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

;; QUESTION SECTION:
;104.168.107.161.		IN	A

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

;; Query time: 57 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 28 17:59:21 CST 2025
;; MSG SIZE  rcvd: 108
Host info
161.107.168.104.in-addr.arpa domain name pointer 104-168-107-161-host.colocrossing.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
161.107.168.104.in-addr.arpa	name = 104-168-107-161-host.colocrossing.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
121.15.2.178 attackspam
SSH Brute-Force reported by Fail2Ban
2020-04-03 18:38:31
106.12.179.81 attack
(sshd) Failed SSH login from 106.12.179.81 (CN/China/-): 5 in the last 3600 secs
2020-04-03 18:15:07
203.162.166.17 attack
Apr  3 10:07:57 vmd48417 sshd[9293]: Failed password for root from 203.162.166.17 port 46774 ssh2
2020-04-03 18:17:31
40.92.69.82 attack
SpamScore above: 10.0
2020-04-03 18:16:33
24.185.47.170 attackbotsspam
Apr  3 09:05:35 haigwepa sshd[20212]: Failed password for root from 24.185.47.170 port 57502 ssh2
...
2020-04-03 18:17:54
106.12.186.74 attackbotsspam
Apr  3 06:34:18 vps46666688 sshd[4777]: Failed password for root from 106.12.186.74 port 54668 ssh2
...
2020-04-03 18:37:06
45.55.155.72 attackbotsspam
SSH Brute-Force reported by Fail2Ban
2020-04-03 18:17:03
222.186.175.183 attackspam
Apr  3 12:14:41 nextcloud sshd\[12838\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.183  user=root
Apr  3 12:14:43 nextcloud sshd\[12838\]: Failed password for root from 222.186.175.183 port 42218 ssh2
Apr  3 12:14:56 nextcloud sshd\[12838\]: Failed password for root from 222.186.175.183 port 42218 ssh2
2020-04-03 18:22:41
103.74.123.41 attack
103.74.123.41 - - [03/Apr/2020:10:49:01 +0200] "GET /wp-login.php HTTP/1.1" 200 5702 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
103.74.123.41 - - [03/Apr/2020:10:49:10 +0200] "POST /wp-login.php HTTP/1.1" 200 6601 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
103.74.123.41 - - [03/Apr/2020:10:49:12 +0200] "POST /xmlrpc.php HTTP/1.1" 200 427 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2020-04-03 18:24:11
45.55.55.17 attackspam
*Port Scan* detected from 45.55.55.17 (US/United States/New Jersey/Clifton/-). 4 hits in the last 225 seconds
2020-04-03 18:19:49
46.238.53.245 attackspam
Apr  3 08:56:02 server sshd\[26919\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.238.53.245  user=root
Apr  3 08:56:04 server sshd\[26919\]: Failed password for root from 46.238.53.245 port 40930 ssh2
Apr  3 09:06:42 server sshd\[29335\]: Invalid user user from 46.238.53.245
Apr  3 09:06:42 server sshd\[29335\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.238.53.245 
Apr  3 09:06:44 server sshd\[29335\]: Failed password for invalid user user from 46.238.53.245 port 47896 ssh2
...
2020-04-03 18:47:23
37.72.187.2 attack
SSH bruteforce
2020-04-03 18:12:56
92.118.160.13 attackbotsspam
[portscan] tcp/993 [imaps]
*(RWIN=1024)(04031042)
2020-04-03 18:48:13
52.168.33.106 attackspambots
Trying ports that it shouldn't be.
2020-04-03 18:52:22
184.22.144.173 attackspambots
kp-sea2-01 recorded 2 login violations from 184.22.144.173 and was blocked at 2020-04-03 03:48:04. 184.22.144.173 has been blocked on 2 previous occasions. 184.22.144.173's first attempt was recorded at 2020-04-02 13:38:38
2020-04-03 18:42:54

Recently Reported IPs

139.247.224.25 244.89.27.143 26.87.56.151 238.33.75.54
188.120.168.62 198.115.105.134 240.61.178.133 239.31.147.88
48.152.123.62 211.30.180.112 6.225.85.4 17.236.92.36
54.28.248.112 148.103.141.86 96.147.18.149 134.77.53.77
59.190.183.78 210.169.25.94 2.199.8.73 46.208.169.248