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

Region: Connecticut

Country: United States

Internet Service Provider: unknown

Hostname: unknown

Organization: Charter Communications

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;68.191.55.114.			IN	A

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

;; Query time: 2 msec
;; SERVER: 67.207.67.3#53(67.207.67.3)
;; WHEN: Fri Apr 26 02:54:04 +08 2019
;; MSG SIZE  rcvd: 117

Host info
114.55.191.68.in-addr.arpa domain name pointer 68-191-55-114.dhcp.nwtn.ct.charter.com.
Nslookup info:
Server:		67.207.67.3
Address:	67.207.67.3#53

Non-authoritative answer:
114.55.191.68.in-addr.arpa	name = 68-191-55-114.dhcp.nwtn.ct.charter.com.

Authoritative answers can be found from:

Related IP info:
Related comments:
IP Type Details Datetime
119.29.197.54 attack
Jun 25 00:02:38 server sshd\[124592\]: Invalid user db2 from 119.29.197.54
Jun 25 00:02:38 server sshd\[124592\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.197.54
Jun 25 00:02:40 server sshd\[124592\]: Failed password for invalid user db2 from 119.29.197.54 port 25020 ssh2
...
2019-07-17 08:31:18
119.29.15.124 attack
Jul 10 19:36:47 server sshd\[58491\]: Invalid user lorelei from 119.29.15.124
Jul 10 19:36:47 server sshd\[58491\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.15.124
Jul 10 19:36:49 server sshd\[58491\]: Failed password for invalid user lorelei from 119.29.15.124 port 40888 ssh2
...
2019-07-17 08:35:07
139.59.80.65 attackspam
Jul 16 20:36:56 vps200512 sshd\[16456\]: Invalid user support from 139.59.80.65
Jul 16 20:36:56 vps200512 sshd\[16456\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.80.65
Jul 16 20:36:57 vps200512 sshd\[16456\]: Failed password for invalid user support from 139.59.80.65 port 52700 ssh2
Jul 16 20:44:12 vps200512 sshd\[16635\]: Invalid user r from 139.59.80.65
Jul 16 20:44:12 vps200512 sshd\[16635\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.80.65
2019-07-17 08:47:45
223.202.201.220 attack
SSH Brute-Force reported by Fail2Ban
2019-07-17 08:36:05
66.64.43.162 attackbots
WordPress login Brute force / Web App Attack on client site.
2019-07-17 08:37:23
94.41.196.254 attackbots
2019-07-17T00:42:03.965935abusebot.cloudsearch.cf sshd\[13529\]: Invalid user backup2 from 94.41.196.254 port 58325
2019-07-17 08:54:28
119.204.246.89 attackbotsspam
2019-07-16T23:52:00.602977abusebot-8.cloudsearch.cf sshd\[12945\]: Invalid user odoo from 119.204.246.89 port 37152
2019-07-17 09:04:40
206.189.145.152 attackspam
2019-07-16 UTC: 2x - gennadi(2x)
2019-07-17 09:11:50
191.209.23.208 attack
@LucianNitescu Personal Honeypot Network <<<>>> Donate at paypal.me/LNitescu <<<>>> 2019-07-16 20:31:37,807 INFO [amun_request_handler] PortScan Detected on Port: 445 (191.209.23.208)
2019-07-17 08:40:26
119.205.221.146 attackspam
Apr 28 17:38:11 server sshd\[77766\]: Invalid user av from 119.205.221.146
Apr 28 17:38:11 server sshd\[77766\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.205.221.146
Apr 28 17:38:13 server sshd\[77766\]: Failed password for invalid user av from 119.205.221.146 port 33676 ssh2
...
2019-07-17 09:02:52
119.28.73.77 attackspambots
Jul  9 06:25:16 server sshd\[160503\]: Invalid user profile from 119.28.73.77
Jul  9 06:25:16 server sshd\[160503\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.28.73.77
Jul  9 06:25:18 server sshd\[160503\]: Failed password for invalid user profile from 119.28.73.77 port 47308 ssh2
...
2019-07-17 08:45:30
185.220.101.34 attackbotsspam
Jul 17 00:04:21 km20725 sshd\[25687\]: Invalid user admin1 from 185.220.101.34Jul 17 00:04:23 km20725 sshd\[25687\]: Failed password for invalid user admin1 from 185.220.101.34 port 39568 ssh2Jul 17 00:04:28 km20725 sshd\[25694\]: Invalid user admin from 185.220.101.34Jul 17 00:04:30 km20725 sshd\[25694\]: Failed password for invalid user admin from 185.220.101.34 port 38733 ssh2
...
2019-07-17 09:07:37
119.29.147.247 attackbots
2019-07-17T00:06:44.408573abusebot-4.cloudsearch.cf sshd\[32181\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.147.247  user=root
2019-07-17 08:36:20
119.29.156.13 attackbots
Apr 28 13:11:59 server sshd\[70990\]: Invalid user sybase from 119.29.156.13
Apr 28 13:11:59 server sshd\[70990\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.156.13
Apr 28 13:12:02 server sshd\[70990\]: Failed password for invalid user sybase from 119.29.156.13 port 38650 ssh2
...
2019-07-17 08:33:36
119.28.228.114 attack
May 20 13:26:47 server sshd\[12064\]: Invalid user ih from 119.28.228.114
May 20 13:26:47 server sshd\[12064\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.28.228.114
May 20 13:26:49 server sshd\[12064\]: Failed password for invalid user ih from 119.28.228.114 port 50076 ssh2
...
2019-07-17 08:49:51

Recently Reported IPs

27.218.120.25 118.151.220.198 14.163.101.211 42.117.110.88
151.8.129.73 115.178.219.217 111.227.22.180 111.75.51.54
49.70.248.242 89.252.133.90 14.161.71.94 73.210.14.225
179.75.183.189 14.161.11.69 40.139.162.71 5.189.140.113
217.184.233.126 107.33.233.56 113.161.1.111 201.221.197.227