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: AT&T

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

;; QUESTION SECTION:
;199.69.104.166.			IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 14:23:38 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 166.104.69.199.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 166.104.69.199.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
24.20.244.45 attackspambots
Mar 18 22:13:05 *** sshd[15559]: Invalid user sinusbot from 24.20.244.45
2020-03-19 09:07:20
37.120.12.212 attackbotsspam
(sshd) Failed SSH login from 37.120.12.212 (DE/Germany/cable-37-120-12-212.cust.telecolumbus.net): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Mar 19 00:15:54 amsweb01 sshd[25335]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.120.12.212  user=root
Mar 19 00:15:56 amsweb01 sshd[25335]: Failed password for root from 37.120.12.212 port 35096 ssh2
Mar 19 00:19:56 amsweb01 sshd[25821]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.120.12.212  user=root
Mar 19 00:19:59 amsweb01 sshd[25821]: Failed password for root from 37.120.12.212 port 46192 ssh2
Mar 19 00:23:47 amsweb01 sshd[26315]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.120.12.212  user=root
2020-03-19 08:56:38
137.118.22.77 attackbotsspam
Received: from mailproxy12.neonova.net ([137.118.22.77])
          by smtp.email-protect.gosecure.net ({b5689ac8-335f-11ea-a228-691fa47b4314})
          via TCP (outbound) with ESMTP id 20200318195910888_00000620;
          Wed, 18 Mar 2020 12:59:10 -0700
X-RC-FROM: 
Received: from nvl-mbs60.neonova.net (nvl-mbs60.neonova.net [137.118.23.60])
	by mailproxy12.neonova.net (Postfix) with ESMTP id 2F51A365917;
	Wed, 18 Mar 2020 15:58:15 -0400 (EDT)
Date: Wed, 18 Mar 2020 15:58:15 -0400 (EDT)
From: "ibank.nbg.gr" 
Reply-To: "ibank.nbg.gr" 
To: Upstart Team 
Message-ID: <154744878.289354838.1584561495076.JavaMail.zimbra@hancock.net>

Pretending n.b.g bank to hack login passwords - account
2020-03-19 08:58:30
178.128.255.8 attackspam
Mar 19 01:18:51 serwer sshd\[21300\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.255.8  user=root
Mar 19 01:18:52 serwer sshd\[21300\]: Failed password for root from 178.128.255.8 port 42588 ssh2
Mar 19 01:24:15 serwer sshd\[21851\]: User nobody from 178.128.255.8 not allowed because not listed in AllowUsers
Mar 19 01:24:15 serwer sshd\[21851\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.255.8  user=nobody
...
2020-03-19 09:02:59
106.12.177.27 attackbotsspam
Mar 19 00:45:01 ns382633 sshd\[14571\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.177.27  user=root
Mar 19 00:45:03 ns382633 sshd\[14571\]: Failed password for root from 106.12.177.27 port 60276 ssh2
Mar 19 01:01:01 ns382633 sshd\[17669\]: Invalid user ts3server from 106.12.177.27 port 43410
Mar 19 01:01:01 ns382633 sshd\[17669\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.177.27
Mar 19 01:01:03 ns382633 sshd\[17669\]: Failed password for invalid user ts3server from 106.12.177.27 port 43410 ssh2
2020-03-19 09:14:20
119.29.10.25 attackspam
Ssh brute force
2020-03-19 09:09:35
196.52.43.61 attackspam
" "
2020-03-19 09:17:10
152.136.37.135 attackspambots
$f2bV_matches
2020-03-19 08:37:41
120.70.102.16 attackbots
Invalid user hyperic from 120.70.102.16 port 34580
2020-03-19 08:35:09
223.166.74.238 attackbots
Fail2Ban Ban Triggered
2020-03-19 09:16:36
178.142.123.103 attackspambots
DATE:2020-03-18 23:09:43, IP:178.142.123.103, PORT:ssh SSH brute force auth on honeypot server (epe-honey1-hq)
2020-03-19 09:04:28
93.26.237.177 attackspambots
DATE:2020-03-18 23:13:07, IP:93.26.237.177, PORT:1433 MSSQL brute force auth on honeypot server (honey-neo-dc)
2020-03-19 09:09:55
222.186.42.75 attackbots
Mar 18 22:10:46 firewall sshd[9890]: Failed password for root from 222.186.42.75 port 22040 ssh2
Mar 18 22:10:49 firewall sshd[9890]: Failed password for root from 222.186.42.75 port 22040 ssh2
Mar 18 22:10:51 firewall sshd[9890]: Failed password for root from 222.186.42.75 port 22040 ssh2
...
2020-03-19 09:18:06
181.30.28.201 attackspam
Mar 18 23:44:25 haigwepa sshd[31802]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.30.28.201 
Mar 18 23:44:27 haigwepa sshd[31802]: Failed password for invalid user astec from 181.30.28.201 port 48514 ssh2
...
2020-03-19 09:16:06
106.12.59.49 attackspambots
SASL PLAIN auth failed: ruser=...
2020-03-19 08:33:51

Recently Reported IPs

94.127.66.159 62.53.66.105 21.15.148.136 26.52.191.74
32.253.81.144 213.214.155.20 34.253.125.145 65.16.121.106
123.153.12.231 159.170.6.206 172.109.91.80 72.203.200.53
192.136.89.7 131.17.179.48 157.74.203.139 97.76.210.156
127.254.19.46 42.138.195.118 120.112.220.44 220.106.8.80