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: Switzerland

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

;; QUESTION SECTION:
;159.232.166.94.			IN	A

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

;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 05 23:11:31 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 94.166.232.159.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 94.166.232.159.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
207.154.218.16 attackspam
SSH Bruteforce attack
2019-10-22 13:22:50
180.164.105.163 attackspambots
UTC: 2019-10-21 port: 443/tcp
2019-10-22 13:14:10
103.79.141.126 attackspam
UTC: 2019-10-21 port: 1010/tcp
2019-10-22 13:19:55
210.177.54.141 attackbotsspam
Oct 22 04:54:30 game-panel sshd[2191]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.177.54.141
Oct 22 04:54:32 game-panel sshd[2191]: Failed password for invalid user set from 210.177.54.141 port 51078 ssh2
Oct 22 05:02:31 game-panel sshd[2451]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.177.54.141
2019-10-22 13:11:34
31.17.26.190 attack
2019-10-22T03:57:21.213627abusebot-5.cloudsearch.cf sshd\[14037\]: Invalid user robert from 31.17.26.190 port 55966
2019-10-22 13:01:41
106.124.131.70 attackbots
2019-10-22T05:14:48.166654homeassistant sshd[28961]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.124.131.70  user=root
2019-10-22T05:14:49.856939homeassistant sshd[28961]: Failed password for root from 106.124.131.70 port 35014 ssh2
...
2019-10-22 13:46:24
148.3.149.116 attack
UTC: 2019-10-21 port: 88/tcp
2019-10-22 13:10:29
104.131.22.72 attack
Brute force SMTP login attempted.
...
2019-10-22 13:20:09
106.13.125.248 attack
2019-10-22T04:30:08.253828abusebot-2.cloudsearch.cf sshd\[3601\]: Invalid user shanzae from 106.13.125.248 port 53264
2019-10-22 13:00:40
119.204.168.61 attackspam
Oct 21 23:56:20 Tower sshd[13572]: Connection from 119.204.168.61 port 52650 on 192.168.10.220 port 22
Oct 21 23:56:21 Tower sshd[13572]: Failed password for root from 119.204.168.61 port 52650 ssh2
Oct 21 23:56:21 Tower sshd[13572]: Received disconnect from 119.204.168.61 port 52650:11: Bye Bye [preauth]
Oct 21 23:56:21 Tower sshd[13572]: Disconnected from authenticating user root 119.204.168.61 port 52650 [preauth]
2019-10-22 13:24:51
159.203.201.1 attackbots
UTC: 2019-10-21 port: 465/tcp
2019-10-22 13:41:58
113.9.65.210 attackbots
Unauthorised access (Oct 22) SRC=113.9.65.210 LEN=40 TTL=49 ID=39209 TCP DPT=23 WINDOW=8929 SYN
2019-10-22 12:55:40
191.178.166.39 attack
UTC: 2019-10-21 port: 23/tcp
2019-10-22 13:29:41
178.150.216.229 attackspambots
2019-10-22T03:56:26.354169abusebot.cloudsearch.cf sshd\[21700\]: Invalid user viable from 178.150.216.229 port 35310
2019-10-22 13:42:52
14.187.65.14 attackbots
UTC: 2019-10-21 port: 23/tcp
2019-10-22 12:59:26

Recently Reported IPs

93.243.23.87 107.165.39.113 104.158.211.194 151.204.129.5
104.130.114.200 195.167.207.240 172.18.87.34 219.75.106.68
29.225.174.229 162.175.181.249 246.101.50.214 27.153.150.160
235.85.45.9 130.158.47.62 146.32.71.172 244.115.115.103
250.248.94.187 16.71.248.180 192.94.232.59 114.207.114.209