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

Region: Jakarta

Country: Indonesia

Internet Service Provider: Esia

Hostname: unknown

Organization: PT Telekomunikasi Indonesia

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
IP Type Details Datetime
125.160.112.250 attackbots
1596974823 - 08/09/2020 14:07:03 Host: 125.160.112.250/125.160.112.250 Port: 445 TCP Blocked
2020-08-10 02:42:09
125.160.112.82 attackbotsspam
report
2020-07-09 03:14:56
125.160.112.92 attackspam
1593864743 - 07/04/2020 14:12:23 Host: 125.160.112.92/125.160.112.92 Port: 445 TCP Blocked
2020-07-04 22:38:41
125.160.112.13 attackspam
1586750320 - 04/13/2020 05:58:40 Host: 125.160.112.13/125.160.112.13 Port: 445 TCP Blocked
2020-04-13 13:08:03
125.160.112.83 attackspam
Attempt to attack host OS, exploiting network vulnerabilities, on 01-04-2020 13:35:15.
2020-04-01 21:10:09
125.160.112.149 attackbots
Unauthorized connection attempt from IP address 125.160.112.149 on Port 445(SMB)
2020-03-23 21:42:48
125.160.112.143 attackspam
Port probing on unauthorized port 8080
2020-02-21 18:05:33
125.160.112.237 attack
Feb 14 14:19:46 l02a sshd[7177]: Invalid user admin from 125.160.112.237
Feb 14 14:19:47 l02a sshd[7177]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.160.112.237 
Feb 14 14:19:46 l02a sshd[7177]: Invalid user admin from 125.160.112.237
Feb 14 14:19:49 l02a sshd[7177]: Failed password for invalid user admin from 125.160.112.237 port 18667 ssh2
2020-02-14 23:25:59
125.160.112.154 attack
1581569635 - 02/13/2020 05:53:55 Host: 125.160.112.154/125.160.112.154 Port: 445 TCP Blocked
2020-02-13 14:26:08
125.160.112.244 attackbots
Unauthorized connection attempt from IP address 125.160.112.244 on Port 445(SMB)
2020-01-08 18:00:48
125.160.112.204 attack
1577686876 - 12/30/2019 07:21:16 Host: 125.160.112.204/125.160.112.204 Port: 445 TCP Blocked
2019-12-30 21:16:35
125.160.112.157 attack
1576212982 - 12/13/2019 05:56:22 Host: 125.160.112.157/125.160.112.157 Port: 445 TCP Blocked
2019-12-13 13:04:23
125.160.112.71 attack
Automatic report - Port Scan Attack
2019-11-03 03:38:21
125.160.112.78 attack
19/10/30@23:51:46: FAIL: Alarm-Intrusion address from=125.160.112.78
...
2019-10-31 15:37:50
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 125.160.112.119
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 36766
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

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

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

;; Query time: 2 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Thu Jun 20 17:30:00 CST 2019
;; MSG SIZE  rcvd: 119
Host info
119.112.160.125.in-addr.arpa domain name pointer 119.subnet125-160-112.speedy.telkom.net.id.
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

Non-authoritative answer:
119.112.160.125.in-addr.arpa	name = 119.subnet125-160-112.speedy.telkom.net.id.

Authoritative answers can be found from:

Related IP info:
Related comments:
IP Type Details Datetime
196.52.43.110 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-11-28 01:57:46
157.45.123.37 attack
Tries to login WordPress (wp-login.php)
2019-11-28 01:55:10
5.160.128.107 attackbots
UTC: 2019-11-26 port: 81/tcp
2019-11-28 02:10:00
36.230.17.117 attack
UTC: 2019-11-26 port: 26/tcp
2019-11-28 02:16:08
106.12.176.53 attackbots
Nov 27 12:21:40 TORMINT sshd\[7954\]: Invalid user guest from 106.12.176.53
Nov 27 12:21:40 TORMINT sshd\[7954\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.176.53
Nov 27 12:21:43 TORMINT sshd\[7954\]: Failed password for invalid user guest from 106.12.176.53 port 52916 ssh2
...
2019-11-28 01:42:51
122.160.167.110 attack
Automatic report - Port Scan Attack
2019-11-28 02:15:45
167.71.159.129 attack
Nov 27 17:16:38 server sshd\[21422\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.159.129  user=root
Nov 27 17:16:40 server sshd\[21422\]: Failed password for root from 167.71.159.129 port 46638 ssh2
Nov 27 17:44:54 server sshd\[28186\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.159.129  user=root
Nov 27 17:44:56 server sshd\[28186\]: Failed password for root from 167.71.159.129 port 52884 ssh2
Nov 27 17:51:36 server sshd\[30170\]: Invalid user trade from 167.71.159.129
Nov 27 17:51:36 server sshd\[30170\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.159.129 
...
2019-11-28 02:17:57
181.30.27.11 attackbotsspam
Nov 26 22:49:36 server sshd\[3401\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.30.27.11  user=root
Nov 26 22:49:38 server sshd\[3401\]: Failed password for root from 181.30.27.11 port 57302 ssh2
Nov 27 17:52:08 server sshd\[30252\]: Invalid user savoie from 181.30.27.11
Nov 27 17:52:08 server sshd\[30252\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.30.27.11 
Nov 27 17:52:10 server sshd\[30252\]: Failed password for invalid user savoie from 181.30.27.11 port 57252 ssh2
...
2019-11-28 01:50:29
167.88.114.249 attack
Nov 27 08:02:09 hpm sshd\[7431\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=irc.chatasia.net  user=root
Nov 27 08:02:11 hpm sshd\[7431\]: Failed password for root from 167.88.114.249 port 46560 ssh2
Nov 27 08:05:16 hpm sshd\[7719\]: Invalid user asistin from 167.88.114.249
Nov 27 08:05:16 hpm sshd\[7719\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=irc.chatasia.net
Nov 27 08:05:18 hpm sshd\[7719\]: Failed password for invalid user asistin from 167.88.114.249 port 57416 ssh2
2019-11-28 02:10:55
182.61.54.14 attack
"Fail2Ban detected SSH brute force attempt"
2019-11-28 02:15:15
150.95.105.63 attackbots
150.95.105.63 - - \[27/Nov/2019:17:49:58 +0000\] "POST /wp-login.php HTTP/1.1" 200 6393 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
150.95.105.63 - - \[27/Nov/2019:17:50:00 +0000\] "POST /xmlrpc.php HTTP/1.1" 200 403 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
...
2019-11-28 01:53:30
208.109.54.127 attackspam
xmlrpc attack
2019-11-28 01:55:23
115.224.32.159 attackbotsspam
UTC: 2019-11-26 port: 23/tcp
2019-11-28 01:55:49
222.186.175.147 attackspambots
Nov 27 18:07:17 localhost sshd\[50534\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.147  user=root
Nov 27 18:07:19 localhost sshd\[50534\]: Failed password for root from 222.186.175.147 port 23366 ssh2
Nov 27 18:07:23 localhost sshd\[50534\]: Failed password for root from 222.186.175.147 port 23366 ssh2
Nov 27 18:07:26 localhost sshd\[50534\]: Failed password for root from 222.186.175.147 port 23366 ssh2
Nov 27 18:07:29 localhost sshd\[50534\]: Failed password for root from 222.186.175.147 port 23366 ssh2
...
2019-11-28 02:17:06
189.125.2.234 attackspam
Nov 27 18:05:54 icinga sshd[20784]: Failed password for root from 189.125.2.234 port 9175 ssh2
...
2019-11-28 01:48:26

Recently Reported IPs

85.25.155.80 217.139.240.132 123.21.33.64 133.11.172.128
51.158.109.172 72.65.9.148 215.100.200.86 223.130.29.109
208.114.84.15 197.51.238.3 153.246.121.30 123.22.173.245
66.249.64.131 184.25.22.230 183.83.166.160 141.203.176.173
109.219.204.135 213.199.188.207 36.114.67.86 162.144.193.18