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

;; QUESTION SECTION:
;74.199.63.14.			IN	A

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

;; Query time: 63 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Sep 15 11:50:27 CST 2022
;; MSG SIZE  rcvd: 105
Host info
14.63.199.74.in-addr.arpa domain name pointer d199-74-14-63.col.wideopenwest.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
14.63.199.74.in-addr.arpa	name = d199-74-14-63.col.wideopenwest.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
190.242.104.221 attackbotsspam
Honeypot attack, port: 445, PTR: PTR record not found
2020-02-10 06:15:25
122.51.234.86 attackspambots
Feb  9 19:42:30 XXX sshd[28687]: Invalid user mns from 122.51.234.86 port 36404
2020-02-10 05:45:51
125.77.81.82 attack
Feb  3 18:57:10 ns4 sshd[13966]: reveeclipse mapping checking getaddrinfo for 82.81.77.125.broad.fz.fj.dynamic.163data.com.cn [125.77.81.82] failed - POSSIBLE BREAK-IN ATTEMPT!
Feb  3 18:57:10 ns4 sshd[13966]: Invalid user test_ftp from 125.77.81.82
Feb  3 18:57:10 ns4 sshd[13966]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.77.81.82 
Feb  3 18:57:12 ns4 sshd[13966]: Failed password for invalid user test_ftp from 125.77.81.82 port 41599 ssh2
Feb  3 19:13:50 ns4 sshd[17175]: reveeclipse mapping checking getaddrinfo for 82.81.77.125.broad.fz.fj.dynamic.163data.com.cn [125.77.81.82] failed - POSSIBLE BREAK-IN ATTEMPT!
Feb  3 19:13:50 ns4 sshd[17175]: Invalid user shou from 125.77.81.82
Feb  3 19:13:50 ns4 sshd[17175]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.77.81.82 
Feb  3 19:13:52 ns4 sshd[17175]: Failed password for invalid user shou from 125.77.81.82 port 52061 ssh2
Feb ........
-------------------------------
2020-02-10 05:39:17
218.85.119.92 attackbots
Feb  9 19:51:28 sd-53420 sshd\[9368\]: Invalid user dii from 218.85.119.92
Feb  9 19:51:28 sd-53420 sshd\[9368\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.85.119.92
Feb  9 19:51:31 sd-53420 sshd\[9368\]: Failed password for invalid user dii from 218.85.119.92 port 20993 ssh2
Feb  9 19:52:22 sd-53420 sshd\[9439\]: Invalid user kmm from 218.85.119.92
Feb  9 19:52:22 sd-53420 sshd\[9439\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.85.119.92
...
2020-02-10 05:53:07
83.97.20.33 attackbots
firewall-block, port(s): 1080/tcp, 3128/tcp, 8089/tcp
2020-02-10 06:09:14
144.217.92.167 attack
pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.92.167 
Failed password for invalid user gwf from 144.217.92.167 port 50928 ssh2
pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.92.167
2020-02-10 05:44:47
222.186.180.6 attack
Feb  9 23:09:26 ns381471 sshd[20165]: Failed password for root from 222.186.180.6 port 18718 ssh2
Feb  9 23:09:39 ns381471 sshd[20165]: error: maximum authentication attempts exceeded for root from 222.186.180.6 port 18718 ssh2 [preauth]
2020-02-10 06:12:48
106.13.90.78 attackbotsspam
Feb  9 19:01:21 sd-53420 sshd\[4827\]: Invalid user rrf from 106.13.90.78
Feb  9 19:01:22 sd-53420 sshd\[4827\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.90.78
Feb  9 19:01:23 sd-53420 sshd\[4827\]: Failed password for invalid user rrf from 106.13.90.78 port 37076 ssh2
Feb  9 19:04:47 sd-53420 sshd\[5100\]: Invalid user kjv from 106.13.90.78
Feb  9 19:04:47 sd-53420 sshd\[5100\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.90.78
...
2020-02-10 05:43:57
54.39.147.2 attackbots
Ssh brute force
2020-02-10 05:58:57
119.252.143.102 attackspam
Ssh brute force
2020-02-10 05:39:04
61.18.127.9 attack
firewall-block, port(s): 5555/tcp
2020-02-10 05:40:19
162.243.130.252 attack
Unauthorized connection attempt detected from IP address 162.243.130.252 to port 2222
2020-02-10 06:21:20
91.138.202.148 attack
port scan and connect, tcp 8080 (http-proxy)
2020-02-10 05:50:19
132.232.93.48 attack
Feb  9 23:09:39 MK-Soft-Root2 sshd[27622]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=132.232.93.48 
Feb  9 23:09:41 MK-Soft-Root2 sshd[27622]: Failed password for invalid user pvp from 132.232.93.48 port 38813 ssh2
...
2020-02-10 06:10:49
163.172.87.232 attackbotsspam
Feb  9 14:21:00 ns382633 sshd\[342\]: Invalid user eg from 163.172.87.232 port 45422
Feb  9 14:21:00 ns382633 sshd\[342\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=163.172.87.232
Feb  9 14:21:02 ns382633 sshd\[342\]: Failed password for invalid user eg from 163.172.87.232 port 45422 ssh2
Feb  9 14:27:10 ns382633 sshd\[1348\]: Invalid user eg from 163.172.87.232 port 59117
Feb  9 14:27:10 ns382633 sshd\[1348\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=163.172.87.232
2020-02-10 06:06:01

Recently Reported IPs

157.245.110.22 170.245.201.126 143.244.143.40 45.9.122.221
112.133.218.180 206.189.149.208 173.231.216.93 114.32.81.114
45.221.11.29 132.148.121.26 74.75.182.60 147.192.177.114
158.170.35.87 172.105.218.46 157.245.105.1 1.190.199.152
18.222.147.249 109.206.241.59 125.106.139.70 93.55.236.85