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

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:
IP Type Details Datetime
119.42.68.155 attackbots
Aug 26 04:52:54 shivevps sshd[3965]: Bad protocol version identification '\024' from 119.42.68.155 port 58134
Aug 26 04:53:01 shivevps sshd[4632]: Bad protocol version identification '\024' from 119.42.68.155 port 58443
Aug 26 04:54:44 shivevps sshd[7837]: Bad protocol version identification '\024' from 119.42.68.155 port 34088
...
2020-08-26 13:15:13
119.42.68.15 attackspambots
Automatic report - Port Scan Attack
2020-03-01 00:54:15
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 119.42.68.104
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 43148
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;119.42.68.104.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 14:44:52 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 104.68.42.119.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 104.68.42.119.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
181.10.18.188 attack
Multiple SSH authentication failures from 181.10.18.188
2020-07-01 16:37:24
116.255.139.236 attack
Jun 30 16:16:10 *** sshd[1614]: User backup from 116.255.139.236 not allowed because not listed in AllowUsers
2020-07-01 16:35:55
184.105.139.116 attackspambots
" "
2020-07-01 17:04:01
36.237.210.107 attack
unauthorized connection attempt
2020-07-01 16:32:20
134.202.64.36 attackbotsspam
(From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across bompchiro.com a few minutes ago.

Looks great… but now what?

By that I mean, when someone like me finds your website – either through Search or just bouncing around – what happens next?  Do you get a lot of leads from your site, or at least enough to make you happy?

Honestly, most business websites fall a bit short when it comes to generating paying customers. Studies show that 70% of a site’s visitors disappear and are gone forever after just a moment.

Here’s an idea…
 
How about making it really EASY for every visitor who shows up to get a personal phone call you as soon as they hit your site…
 
You can –
  
Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number.  It signals you the moment they let you know they’re interested – so that you can talk to that lead while they’re literally looking over your site.

CLICK HERE http://www.talkwit
2020-07-01 16:55:07
106.51.73.204 attack
Multiple SSH authentication failures from 106.51.73.204
2020-07-01 17:07:19
5.196.198.147 attackspambots
2020-06-30T21:45:01.813073afi-git.jinr.ru sshd[3396]: Invalid user daniel from 5.196.198.147 port 54202
2020-06-30T21:45:01.816368afi-git.jinr.ru sshd[3396]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.196.198.147
2020-06-30T21:45:01.813073afi-git.jinr.ru sshd[3396]: Invalid user daniel from 5.196.198.147 port 54202
2020-06-30T21:45:03.455224afi-git.jinr.ru sshd[3396]: Failed password for invalid user daniel from 5.196.198.147 port 54202 ssh2
2020-06-30T21:47:42.440027afi-git.jinr.ru sshd[4157]: Invalid user oracle from 5.196.198.147 port 49082
...
2020-07-01 16:24:15
212.64.80.169 attackspambots
Icarus honeypot on github
2020-07-01 16:19:17
185.242.5.46 attackbots
 TCP (SYN) 185.242.5.46:57239 -> port 53, len 44
2020-07-01 16:50:37
61.147.103.136 attack
[MK-Root1] Blocked by UFW
2020-07-01 16:49:25
42.115.11.68 attackbots
400 BAD REQUEST
2020-07-01 16:27:20
49.233.196.186 attackbotsspam
Jun 29 19:59:04 garuda sshd[934160]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.233.196.186  user=r.r
Jun 29 19:59:06 garuda sshd[934160]: Failed password for r.r from 49.233.196.186 port 51908 ssh2
Jun 29 19:59:06 garuda sshd[934160]: Received disconnect from 49.233.196.186: 11: Bye Bye [preauth]
Jun 29 20:09:37 garuda sshd[936868]: Connection closed by 49.233.196.186 [preauth]
Jun 29 20:14:37 garuda sshd[938057]: Connection closed by 49.233.196.186 [preauth]
Jun 29 20:19:15 garuda sshd[939402]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.233.196.186  user=r.r
Jun 29 20:19:18 garuda sshd[939402]: Failed password for r.r from 49.233.196.186 port 58658 ssh2
Jun 29 20:19:18 garuda sshd[939402]: Received disconnect from 49.233.196.186: 11: Bye Bye [preauth]
Jun 29 20:24:16 garuda sshd[940775]: Connection closed by 49.233.196.186 [preauth]
Jun 29 20:28:49 garuda sshd[941972]: Inva........
-------------------------------
2020-07-01 16:31:37
45.162.216.10 attack
Multiple SSH authentication failures from 45.162.216.10
2020-07-01 16:51:48
158.69.226.175 attackspam
portscan
2020-07-01 16:37:51
84.208.137.213 attack
Jul  1 00:52:04 itv-usvr-02 sshd[22372]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.208.137.213  user=root
Jul  1 00:54:58 itv-usvr-02 sshd[22477]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.208.137.213  user=root
Jul  1 00:57:42 itv-usvr-02 sshd[22571]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.208.137.213
2020-07-01 16:43:48

Recently Reported IPs

119.42.68.103 119.42.68.106 79.23.172.146 119.42.68.109
119.42.68.11 119.42.68.110 119.42.68.112 119.42.68.114
119.42.68.116 119.42.68.118 119.42.68.12 119.42.68.120
119.42.68.122 119.42.68.124 119.42.68.126 119.42.68.128
119.42.68.141 119.42.69.104 119.42.69.122 119.42.69.129