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: South Africa

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

;; QUESTION SECTION:
;105.228.48.122.			IN	A

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

;; Query time: 62 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 21:04:39 CST 2022
;; MSG SIZE  rcvd: 107
Host info
122.48.228.105.in-addr.arpa domain name pointer 105-228-48-122.south.dsl.telkomsa.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
122.48.228.105.in-addr.arpa	name = 105-228-48-122.south.dsl.telkomsa.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
66.249.155.244 attackbotsspam
Feb 10 06:13:45 tuxlinux sshd[60915]: Invalid user ups from 66.249.155.244 port 42484
Feb 10 06:13:45 tuxlinux sshd[60915]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.249.155.244 
Feb 10 06:13:45 tuxlinux sshd[60915]: Invalid user ups from 66.249.155.244 port 42484
Feb 10 06:13:45 tuxlinux sshd[60915]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.249.155.244 
Feb 10 06:13:45 tuxlinux sshd[60915]: Invalid user ups from 66.249.155.244 port 42484
Feb 10 06:13:45 tuxlinux sshd[60915]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.249.155.244 
Feb 10 06:13:47 tuxlinux sshd[60915]: Failed password for invalid user ups from 66.249.155.244 port 42484 ssh2
...
2020-02-10 15:49:34
116.105.199.176 attackbots
2020-02-10T04:53:58Z - RDP login failed multiple times. (116.105.199.176)
2020-02-10 16:26:02
49.205.96.223 attackspambots
Honeypot attack, port: 445, PTR: broadband.actcorp.in.
2020-02-10 15:57:38
128.199.219.108 attackbots
$f2bV_matches
2020-02-10 15:58:30
14.232.208.247 attackbotsspam
20/2/9@23:54:01: FAIL: Alarm-Network address from=14.232.208.247
20/2/9@23:54:01: FAIL: Alarm-Network address from=14.232.208.247
...
2020-02-10 16:20:37
117.107.133.162 attackbots
Feb  9 20:48:15 web1 sshd\[3227\]: Invalid user gcm from 117.107.133.162
Feb  9 20:48:15 web1 sshd\[3227\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.107.133.162
Feb  9 20:48:17 web1 sshd\[3227\]: Failed password for invalid user gcm from 117.107.133.162 port 42794 ssh2
Feb  9 20:50:48 web1 sshd\[3434\]: Invalid user jvp from 117.107.133.162
Feb  9 20:50:48 web1 sshd\[3434\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.107.133.162
2020-02-10 16:04:04
103.196.46.251 attackspambots
Portscan or hack attempt detected by psad/fwsnort
2020-02-10 16:35:03
200.57.199.14 attack
Automatic report - Port Scan
2020-02-10 16:00:17
162.243.233.102 attackspam
Feb 10 00:10:04 plusreed sshd[20462]: Invalid user xbj from 162.243.233.102
...
2020-02-10 15:52:43
88.208.236.214 attackspambots
postfix (unknown user, SPF fail or relay access denied)
2020-02-10 16:21:51
106.12.199.74 attack
20 attempts against mh-ssh on cloud
2020-02-10 15:54:02
103.217.217.122 attackbotsspam
Feb 10 05:54:05 h2177944 kernel: \[4508466.835336\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=103.217.217.122 DST=85.214.117.9 LEN=48 TOS=0x00 PREC=0x00 TTL=117 ID=21359 DF PROTO=TCP SPT=49227 DPT=8291 WINDOW=8192 RES=0x00 SYN URGP=0 
Feb 10 05:54:05 h2177944 kernel: \[4508466.835349\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=103.217.217.122 DST=85.214.117.9 LEN=48 TOS=0x00 PREC=0x00 TTL=117 ID=21359 DF PROTO=TCP SPT=49227 DPT=8291 WINDOW=8192 RES=0x00 SYN URGP=0 
Feb 10 05:54:08 h2177944 kernel: \[4508470.000002\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=103.217.217.122 DST=85.214.117.9 LEN=48 TOS=0x00 PREC=0x00 TTL=117 ID=32350 DF PROTO=TCP SPT=49227 DPT=8291 WINDOW=8192 RES=0x00 SYN URGP=0 
Feb 10 05:54:08 h2177944 kernel: \[4508470.000016\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=103.217.217.122 DST=85.214.117.9 LEN=48 TOS=0x00 PREC=0x00 TTL=117 ID=32350 DF PROTO=TCP SPT=49227 DPT=8291 WINDOW=8192 RES=0x00 SYN URGP=0 
Feb 10 05:54:27 h2177944 kernel: \[4508489.591324\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=103.217.21
2020-02-10 16:00:39
169.61.64.13 attackbots
2020-02-10T02:03:06.8773021495-001 sshd[14731]: Invalid user yxf from 169.61.64.13 port 36934
2020-02-10T02:03:06.8805981495-001 sshd[14731]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=d.40.3da9.ip4.static.sl-reverse.com
2020-02-10T02:03:06.8773021495-001 sshd[14731]: Invalid user yxf from 169.61.64.13 port 36934
2020-02-10T02:03:09.1854161495-001 sshd[14731]: Failed password for invalid user yxf from 169.61.64.13 port 36934 ssh2
2020-02-10T02:05:12.5075661495-001 sshd[14861]: Invalid user eyd from 169.61.64.13 port 57070
2020-02-10T02:05:12.5178921495-001 sshd[14861]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=d.40.3da9.ip4.static.sl-reverse.com
2020-02-10T02:05:12.5075661495-001 sshd[14861]: Invalid user eyd from 169.61.64.13 port 57070
2020-02-10T02:05:14.4571141495-001 sshd[14861]: Failed password for invalid user eyd from 169.61.64.13 port 57070 ssh2
2020-02-10T02:07:14.7100241495-001 sshd[14
...
2020-02-10 16:12:41
119.40.99.60 attackbots
2020-02-10T05:53:48.117394jannga.de sshd[29412]: Invalid user tech from 119.40.99.60 port 37010
2020-02-10T05:53:50.262550jannga.de sshd[29412]: Failed password for invalid user tech from 119.40.99.60 port 37010 ssh2
...
2020-02-10 16:33:33
122.228.19.80 attackbots
122.228.19.80 was recorded 12 times by 5 hosts attempting to connect to the following ports: 515,79,4022,1025,123,4410,3299,179,6379,666,4730,37215. Incident counter (4h, 24h, all-time): 12, 111, 25214
2020-02-10 16:30:03

Recently Reported IPs

105.228.49.11 101.200.49.221 105.228.50.89 105.228.52.219
105.228.52.101 105.228.52.99 105.228.51.144 105.228.55.230
105.228.64.75 105.228.54.21 241.35.239.22 105.228.47.98
105.228.67.193 105.228.7.176 101.200.50.18 105.228.69.227
105.228.65.17 105.228.65.162 105.228.78.52 105.228.77.243