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

Region: Central Java

Country: Indonesia

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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 103.105.55.226
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 57796
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;103.105.55.226.			IN	A

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

;; Query time: 83 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Apr 03 04:18:12 CST 2022
;; MSG SIZE  rcvd: 107
Host info
226.55.105.103.in-addr.arpa domain name pointer 103-105-55-226.megadata.net.id.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
226.55.105.103.in-addr.arpa	name = 103-105-55-226.megadata.net.id.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
91.121.7.155 attack
Nov 27 06:39:11 lnxweb61 sshd[25989]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.121.7.155
Nov 27 06:39:11 lnxweb61 sshd[25989]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.121.7.155
2019-11-27 13:43:39
111.68.104.156 attack
2019-11-27T06:00:22.451832scmdmz1 sshd\[10028\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.68.104.156  user=root
2019-11-27T06:00:24.336488scmdmz1 sshd\[10028\]: Failed password for root from 111.68.104.156 port 19254 ssh2
2019-11-27T06:09:42.808102scmdmz1 sshd\[10791\]: Invalid user tiem3394 from 111.68.104.156 port 27356
2019-11-27T06:09:42.810790scmdmz1 sshd\[10791\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.68.104.156
...
2019-11-27 13:11:50
182.61.26.50 attackspam
Nov 27 07:34:25 sauna sshd[36918]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.26.50
Nov 27 07:34:27 sauna sshd[36918]: Failed password for invalid user egland from 182.61.26.50 port 34042 ssh2
...
2019-11-27 13:40:33
82.207.23.43 attackspambots
Nov 26 19:11:36 web9 sshd\[29082\]: Invalid user kamatari from 82.207.23.43
Nov 26 19:11:36 web9 sshd\[29082\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.207.23.43
Nov 26 19:11:37 web9 sshd\[29082\]: Failed password for invalid user kamatari from 82.207.23.43 port 47029 ssh2
Nov 26 19:18:39 web9 sshd\[29962\]: Invalid user grahan from 82.207.23.43
Nov 26 19:18:39 web9 sshd\[29962\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=82.207.23.43
2019-11-27 13:35:43
72.167.190.50 attackspambots
Automatic report - Banned IP Access
2019-11-27 13:37:32
106.13.105.77 attackbotsspam
Nov 27 07:57:46 hosting sshd[17987]: Invalid user jersy from 106.13.105.77 port 56652
...
2019-11-27 13:25:11
1.53.16.133 attackspam
Nov 27 05:57:32 mc1 kernel: \[6116880.985384\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=1.53.16.133 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=51 ID=48847 PROTO=TCP SPT=9375 DPT=23 WINDOW=12665 RES=0x00 SYN URGP=0 
Nov 27 05:57:32 mc1 kernel: \[6116880.992996\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=1.53.16.133 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=51 ID=48847 PROTO=TCP SPT=9375 DPT=23 WINDOW=12665 RES=0x00 SYN URGP=0 
Nov 27 05:57:32 mc1 kernel: \[6116881.014639\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=1.53.16.133 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=51 ID=48847 PROTO=TCP SPT=9375 DPT=23 WINDOW=12665 RES=0x00 SYN URGP=0 
Nov 27 05:57:32 mc1 kernel: \[6116881.062390\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=1.53.16.133 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=51 ID=48847 PROTO=TCP SPT=9375 DPT=23 WINDOW=126
...
2019-11-27 13:38:55
190.182.179.11 attack
Autoban   190.182.179.11 ABORTED AUTH
2019-11-27 13:12:51
132.232.52.48 attackspam
Automatic report - Banned IP Access
2019-11-27 13:11:37
193.32.163.74 attack
Fail2Ban Ban Triggered
2019-11-27 13:20:21
45.64.132.33 attack
Unauthorised access (Nov 27) SRC=45.64.132.33 LEN=52 TTL=118 ID=30390 DF TCP DPT=445 WINDOW=8192 SYN
2019-11-27 13:47:10
39.67.194.80 attack
Fail2Ban - FTP Abuse Attempt
2019-11-27 13:22:06
103.49.249.42 attack
Nov 27 06:17:58 sd-53420 sshd\[17186\]: User root from 103.49.249.42 not allowed because none of user's groups are listed in AllowGroups
Nov 27 06:17:58 sd-53420 sshd\[17186\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.49.249.42  user=root
Nov 27 06:18:00 sd-53420 sshd\[17186\]: Failed password for invalid user root from 103.49.249.42 port 54612 ssh2
Nov 27 06:18:02 sd-53420 sshd\[17186\]: Failed password for invalid user root from 103.49.249.42 port 54612 ssh2
Nov 27 06:18:04 sd-53420 sshd\[17186\]: Failed password for invalid user root from 103.49.249.42 port 54612 ssh2
...
2019-11-27 13:36:15
104.131.29.92 attackbotsspam
Nov 27 05:54:57 tux-35-217 sshd\[15385\]: Invalid user ortoljo from 104.131.29.92 port 56545
Nov 27 05:54:57 tux-35-217 sshd\[15385\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.29.92
Nov 27 05:54:59 tux-35-217 sshd\[15385\]: Failed password for invalid user ortoljo from 104.131.29.92 port 56545 ssh2
Nov 27 06:01:00 tux-35-217 sshd\[15445\]: Invalid user pos02 from 104.131.29.92 port 45793
Nov 27 06:01:00 tux-35-217 sshd\[15445\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.29.92
...
2019-11-27 13:35:22
209.17.96.170 attackspam
209.17.96.170 was recorded 13 times by 10 hosts attempting to connect to the following ports: 5985,5910,5906,135,2323,44818,5901,5289,5000,5902. Incident counter (4h, 24h, all-time): 13, 46, 783
2019-11-27 13:50:16

Recently Reported IPs

103.105.49.159 103.105.64.33 103.105.66.99 103.105.76.111
103.105.97.22 103.106.192.204 103.106.194.130 103.106.195.154
103.106.239.238 103.106.239.239 103.106.243.118 103.106.246.139
103.106.28.204 103.106.74.101 103.106.78.86 103.107.101.196
103.107.12.203 103.107.132.173 103.107.132.177 103.107.181.231