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

;; QUESTION SECTION:
;166.168.14.197.			IN	A

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

;; Query time: 41 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 17 15:10:42 CST 2025
;; MSG SIZE  rcvd: 107
Host info
197.14.168.166.in-addr.arpa domain name pointer 197.sub-166-168-14.myvzw.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
197.14.168.166.in-addr.arpa	name = 197.sub-166-168-14.myvzw.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
148.72.232.164 attack
Automatic report - XMLRPC Attack
2019-10-04 08:51:27
222.186.15.65 attackspam
SSH authentication failure x 6 reported by Fail2Ban
...
2019-10-04 09:01:52
192.241.249.19 attack
Oct  4 02:31:33 mail sshd\[10950\]: Failed password for invalid user apollo from 192.241.249.19 port 35316 ssh2
Oct  4 02:36:06 mail sshd\[11364\]: Invalid user 8080 from 192.241.249.19 port 55932
Oct  4 02:36:06 mail sshd\[11364\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.241.249.19
Oct  4 02:36:07 mail sshd\[11364\]: Failed password for invalid user 8080 from 192.241.249.19 port 55932 ssh2
Oct  4 02:40:57 mail sshd\[11940\]: Invalid user aires from 192.241.249.19 port 48313
2019-10-04 08:52:40
106.75.165.187 attack
ssh failed login
2019-10-04 09:13:25
192.144.130.31 attack
Oct  3 13:32:57 auw2 sshd\[12696\]: Invalid user ftp from 192.144.130.31
Oct  3 13:32:57 auw2 sshd\[12696\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.144.130.31
Oct  3 13:32:59 auw2 sshd\[12696\]: Failed password for invalid user ftp from 192.144.130.31 port 34322 ssh2
Oct  3 13:37:18 auw2 sshd\[13085\]: Invalid user stagiaire from 192.144.130.31
Oct  3 13:37:18 auw2 sshd\[13085\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.144.130.31
2019-10-04 09:05:36
114.112.58.134 attack
Oct  3 22:38:29 heissa sshd\[22924\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.112.58.134  user=root
Oct  3 22:38:30 heissa sshd\[22924\]: Failed password for root from 114.112.58.134 port 45228 ssh2
Oct  3 22:43:09 heissa sshd\[23686\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.112.58.134  user=root
Oct  3 22:43:11 heissa sshd\[23686\]: Failed password for root from 114.112.58.134 port 57142 ssh2
Oct  3 22:47:47 heissa sshd\[24326\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.112.58.134  user=root
2019-10-04 09:13:52
139.99.98.248 attack
Lines containing failures of 139.99.98.248
Oct  3 00:15:42 MAKserver06 sshd[1593]: Invalid user hanover from 139.99.98.248 port 52754
Oct  3 00:15:42 MAKserver06 sshd[1593]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.99.98.248 
Oct  3 00:15:44 MAKserver06 sshd[1593]: Failed password for invalid user hanover from 139.99.98.248 port 52754 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=139.99.98.248
2019-10-04 09:13:06
79.172.3.78 attackspambots
[portscan] Port scan
2019-10-04 09:08:40
192.99.175.187 attackspam
Automatic report - Port Scan Attack
2019-10-04 09:08:27
222.186.173.180 attackbots
"Fail2Ban detected SSH brute force attempt"
2019-10-04 08:50:37
46.38.144.146 attackspam
Oct  4 05:56:13 relay postfix/smtpd\[17329\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  4 05:56:32 relay postfix/smtpd\[32674\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  4 05:58:03 relay postfix/smtpd\[32180\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  4 05:58:21 relay postfix/smtpd\[32673\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  4 05:59:52 relay postfix/smtpd\[17329\]: warning: unknown\[46.38.144.146\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-10-04 12:02:11
52.151.7.153 attack
python-requests/2.18.4
2019-10-04 08:49:29
220.85.104.202 attackspam
$f2bV_matches
2019-10-04 09:05:00
43.231.61.146 attackspambots
Oct  4 05:55:06 MK-Soft-Root2 sshd[27276]: Failed password for root from 43.231.61.146 port 40968 ssh2
...
2019-10-04 12:05:40
106.51.48.244 attack
RDP Bruteforce
2019-10-04 08:56:46

Recently Reported IPs

144.114.137.184 95.90.56.242 187.184.54.80 88.156.64.108
144.218.29.186 134.202.104.141 78.119.221.78 128.121.249.217
43.178.108.227 165.94.174.24 164.66.231.251 83.113.225.75
30.164.222.208 238.182.142.73 48.147.196.48 184.189.13.228
28.217.183.78 119.68.147.199 34.191.14.48 159.254.54.249