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.123.186 attack
20/6/25@08:24:45: FAIL: Alarm-Network address from=119.42.123.186
20/6/25@08:24:45: FAIL: Alarm-Network address from=119.42.123.186
...
2020-06-26 00:38:32
119.42.123.14 attack
1591501924 - 06/07/2020 05:52:04 Host: 119.42.123.14/119.42.123.14 Port: 445 TCP Blocked
2020-06-07 16:32:16
119.42.123.108 attack
2020-06-01T12:07:12.550475odie.crmd.co.za postfix/smtpd[11149]: warning: unknown[119.42.123.108]: SASL PLAIN authentication failed: authentication failure
2020-06-01T12:07:15.617829odie.crmd.co.za postfix/smtpd[11149]: warning: unknown[119.42.123.108]: SASL PLAIN authentication failed: authentication failure
2020-06-01T12:07:16.299207odie.crmd.co.za postfix/smtpd[11149]: warning: unknown[119.42.123.108]: SASL PLAIN authentication failed: authentication failure
...
2020-06-01 22:52:56
119.42.123.181 attackbotsspam
Automatic report - Port Scan Attack
2020-03-09 16:08:55
119.42.123.209 attack
1581742349 - 02/15/2020 05:52:29 Host: 119.42.123.209/119.42.123.209 Port: 445 TCP Blocked
2020-02-15 16:09:56
119.42.123.235 attack
" "
2019-12-24 23:14:26
119.42.123.123 attackbots
Unauthorized connection attempt from IP address 119.42.123.123 on Port 445(SMB)
2019-09-08 02:11:53
119.42.123.101 attack
19/8/6@07:20:42: FAIL: Alarm-Intrusion address from=119.42.123.101
...
2019-08-06 22:46:41
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 119.42.123.148
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 57685
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;119.42.123.148.			IN	A

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

;; Query time: 21 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 08 18:39:24 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 148.123.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 148.123.42.119.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
182.162.143.236 attack
Nov 28 00:18:55 vibhu-HP-Z238-Microtower-Workstation sshd\[28639\]: Invalid user applmgr1 from 182.162.143.236
Nov 28 00:18:55 vibhu-HP-Z238-Microtower-Workstation sshd\[28639\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.162.143.236
Nov 28 00:18:57 vibhu-HP-Z238-Microtower-Workstation sshd\[28639\]: Failed password for invalid user applmgr1 from 182.162.143.236 port 51874 ssh2
Nov 28 00:23:13 vibhu-HP-Z238-Microtower-Workstation sshd\[28853\]: Invalid user monkey from 182.162.143.236
Nov 28 00:23:13 vibhu-HP-Z238-Microtower-Workstation sshd\[28853\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.162.143.236
...
2019-11-28 03:54:17
118.126.108.213 attackspambots
Nov 27 18:59:13 MK-Soft-VM8 sshd[19679]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.126.108.213 
Nov 27 18:59:15 MK-Soft-VM8 sshd[19679]: Failed password for invalid user zhanghua123 from 118.126.108.213 port 41466 ssh2
...
2019-11-28 03:52:23
89.248.174.3 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-28 03:37:12
177.220.188.59 attackspambots
Nov 27 20:07:47 sso sshd[11743]: Failed password for mysql from 177.220.188.59 port 35084 ssh2
Nov 27 20:11:41 sso sshd[12214]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.220.188.59
...
2019-11-28 03:47:32
94.153.212.65 attackspam
Nov 27 05:01:48 km20725 sshd[29740]: Did not receive identification string from 94.153.212.65
Nov 27 05:02:17 km20725 sshd[29752]: reveeclipse mapping checking getaddrinfo for 94-153-212-65.ip.kyivstar.net [94.153.212.65] failed - POSSIBLE BREAK-IN ATTEMPT!
Nov 27 05:02:17 km20725 sshd[29752]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.153.212.65  user=r.r
Nov 27 05:02:18 km20725 sshd[29754]: reveeclipse mapping checking getaddrinfo for 94-153-212-65.ip.kyivstar.net [94.153.212.65] failed - POSSIBLE BREAK-IN ATTEMPT!
Nov 27 05:02:18 km20725 sshd[29754]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.153.212.65  user=r.r
Nov 27 05:02:18 km20725 sshd[29756]: reveeclipse mapping checking getaddrinfo for 94-153-212-65.ip.kyivstar.net [94.153.212.65] failed - POSSIBLE BREAK-IN ATTEMPT!
Nov 27 05:02:18 km20725 sshd[29756]: pam_unix(sshd:auth): authentication failure; logname= uid=0 eui........
-------------------------------
2019-11-28 03:45:58
218.92.0.175 attack
Nov 27 20:05:20 odroid64 sshd\[18467\]: User root from 218.92.0.175 not allowed because not listed in AllowUsers
Nov 27 20:05:21 odroid64 sshd\[18467\]: Failed none for invalid user root from 218.92.0.175 port 54656 ssh2
...
2019-11-28 03:28:25
217.61.1.141 attackspam
Fail2Ban Ban Triggered
2019-11-28 03:26:58
195.31.160.73 attackbotsspam
Nov 27 20:17:49 dedicated sshd[21734]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.31.160.73  user=root
Nov 27 20:17:51 dedicated sshd[21734]: Failed password for root from 195.31.160.73 port 60066 ssh2
2019-11-28 03:32:49
134.175.36.138 attack
Nov 27 10:41:13 ny01 sshd[8627]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.36.138
Nov 27 10:41:15 ny01 sshd[8627]: Failed password for invalid user lauren from 134.175.36.138 port 42912 ssh2
Nov 27 10:45:54 ny01 sshd[9042]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.36.138
2019-11-28 03:45:37
177.131.31.70 attack
firewall-block, port(s): 445/tcp
2019-11-28 03:20:19
37.49.231.107 attackbotsspam
firewall-block, port(s): 5060/udp
2019-11-28 03:31:52
118.24.23.196 attackspambots
Nov 17 00:47:10 vtv3 sshd[25089]: Invalid user guest from 118.24.23.196 port 45384
Nov 17 00:47:10 vtv3 sshd[25089]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.23.196
Nov 27 12:10:06 vtv3 sshd[4567]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.23.196 
Nov 27 12:10:08 vtv3 sshd[4567]: Failed password for invalid user named from 118.24.23.196 port 48186 ssh2
Nov 27 12:18:04 vtv3 sshd[8284]: Failed password for backup from 118.24.23.196 port 55344 ssh2
Nov 27 12:33:30 vtv3 sshd[15872]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.23.196 
Nov 27 12:33:32 vtv3 sshd[15872]: Failed password for invalid user zenon from 118.24.23.196 port 41414 ssh2
Nov 27 12:42:13 vtv3 sshd[20064]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.23.196 
Nov 27 12:59:00 vtv3 sshd[27959]: Failed password for root from 118.24.23.196 port 34
2019-11-28 03:37:33
218.92.0.133 attackspambots
SSH Bruteforce attempt
2019-11-28 03:27:45
138.68.165.102 attackbotsspam
Nov 27 09:10:41 hpm sshd\[13882\]: Invalid user ftpuser from 138.68.165.102
Nov 27 09:10:41 hpm sshd\[13882\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.165.102
Nov 27 09:10:43 hpm sshd\[13882\]: Failed password for invalid user ftpuser from 138.68.165.102 port 48806 ssh2
Nov 27 09:16:47 hpm sshd\[14390\]: Invalid user wwwrun from 138.68.165.102
Nov 27 09:16:47 hpm sshd\[14390\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.165.102
2019-11-28 03:22:31
193.47.63.106 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-28 03:46:24

Recently Reported IPs

119.42.123.147 119.42.123.149 119.42.123.150 119.42.123.152
119.42.123.156 119.42.123.155 119.42.123.160 119.42.123.159
119.42.123.16 119.42.123.166 119.42.123.168 119.42.123.161
117.150.166.156 119.42.123.169 119.42.123.170 119.42.123.172
119.42.123.174 119.42.123.179 119.42.123.176 119.42.123.18