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

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

;; QUESTION SECTION:
;119.42.68.49.			IN	A

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

;; Query time: 71 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 08 18:42:08 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 49.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 49.68.42.119.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
159.205.82.134 attackspam
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/159.205.82.134/ 
 
 AU - 1H : (46)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : AU 
 NAME ASN : ASN12741 
 
 IP : 159.205.82.134 
 
 CIDR : 159.205.0.0/16 
 
 PREFIX COUNT : 95 
 
 UNIQUE IP COUNT : 1590528 
 
 
 ATTACKS DETECTED ASN12741 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 4 
 24H - 5 
 
 DateTime : 2019-11-01 04:55:33 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-11-01 13:21:04
138.197.5.224 attack
WordPress login Brute force / Web App Attack on client site.
2019-11-01 14:07:41
1.71.129.108 attackbots
Nov  1 07:04:04 server sshd\[1404\]: Invalid user ki from 1.71.129.108
Nov  1 07:04:04 server sshd\[1404\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.71.129.108 
Nov  1 07:04:06 server sshd\[1404\]: Failed password for invalid user ki from 1.71.129.108 port 37475 ssh2
Nov  1 07:24:48 server sshd\[6150\]: Invalid user vera from 1.71.129.108
Nov  1 07:24:48 server sshd\[6150\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.71.129.108 
...
2019-11-01 14:03:45
220.133.148.28 attackbots
23/tcp 9001/tcp 34567/tcp
[2019-09-21/11-01]3pkt
2019-11-01 13:15:21
67.53.47.54 attackbotsspam
port scan and connect, tcp 1433 (ms-sql-s)
2019-11-01 13:56:55
95.123.94.182 attackbotsspam
Oct 30 17:28:38 shadeyouvpn sshd[10997]: Invalid user applmgr from 95.123.94.182
Oct 30 17:28:39 shadeyouvpn sshd[10997]: Failed password for invalid user applmgr from 95.123.94.182 port 40148 ssh2
Oct 30 17:28:40 shadeyouvpn sshd[10997]: Received disconnect from 95.123.94.182: 11: Bye Bye [preauth]
Oct 30 17:39:08 shadeyouvpn sshd[19145]: Failed password for r.r from 95.123.94.182 port 58690 ssh2
Oct 30 17:39:08 shadeyouvpn sshd[19145]: Received disconnect from 95.123.94.182: 11: Bye Bye [preauth]
Oct 30 17:43:16 shadeyouvpn sshd[23629]: Failed password for r.r from 95.123.94.182 port 42502 ssh2
Oct 30 17:43:16 shadeyouvpn sshd[23629]: Received disconnect from 95.123.94.182: 11: Bye Bye [preauth]
Oct 30 17:47:20 shadeyouvpn sshd[27871]: Invalid user login from 95.123.94.182
Oct 30 17:47:22 shadeyouvpn sshd[27871]: Failed password for invalid user login from 95.123.94.182 port 54546 ssh2
Oct 30 17:47:22 shadeyouvpn sshd[27871]: Received disconnect from 95.123.94.182: 11........
-------------------------------
2019-11-01 13:41:50
2001:41d0:303:adda:: attackbots
xmlrpc attack
2019-11-01 14:04:42
188.166.163.98 attack
Nov  1 07:17:52 server2 sshd\[7669\]: Invalid user baker from 188.166.163.98
Nov  1 07:17:52 server2 sshd\[7674\]: Invalid user baker from 188.166.163.98
Nov  1 07:17:52 server2 sshd\[7671\]: Invalid user baker from 188.166.163.98
Nov  1 07:17:52 server2 sshd\[7672\]: Invalid user baker from 188.166.163.98
Nov  1 07:17:52 server2 sshd\[7677\]: Invalid user baker from 188.166.163.98
Nov  1 07:17:52 server2 sshd\[7679\]: Invalid user bitrix from 188.166.163.98
2019-11-01 13:48:20
58.210.219.5 attackspam
Helo
2019-11-01 13:52:38
159.65.30.66 attack
Nov  1 06:13:44 lnxded63 sshd[11910]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.30.66
2019-11-01 13:54:55
124.156.172.11 attack
k+ssh-bruteforce
2019-11-01 14:08:22
62.2.148.66 attackbots
Nov  1 06:03:30 legacy sshd[9458]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.2.148.66
Nov  1 06:03:32 legacy sshd[9458]: Failed password for invalid user aleksandir from 62.2.148.66 port 57529 ssh2
Nov  1 06:07:51 legacy sshd[9585]: Failed password for root from 62.2.148.66 port 50285 ssh2
...
2019-11-01 13:22:35
109.202.117.114 attackspambots
ET SCAN Potential SSH Scan - port: 22 proto: TCP cat: Attempted Information Leak
2019-11-01 13:16:39
159.203.197.148 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-01 13:56:09
173.241.21.82 attack
2019-11-01T05:30:40.469010abusebot-2.cloudsearch.cf sshd\[7201\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.241.21.82  user=root
2019-11-01 13:54:33

Recently Reported IPs

119.42.68.57 119.42.68.60 119.42.68.58 119.42.68.66
119.42.68.64 119.42.68.7 119.42.68.63 117.152.40.77
119.42.68.74 119.42.68.76 119.42.68.73 119.42.68.79
119.42.68.8 119.42.68.82 119.42.68.87 119.42.68.80
119.42.68.89 119.42.68.90 119.42.68.92 119.42.68.94