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: Republic of China (ROC)

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

;; QUESTION SECTION:
;1.163.118.55.			IN	A

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

;; Query time: 65 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 11:27:47 CST 2022
;; MSG SIZE  rcvd: 105
Host info
55.118.163.1.in-addr.arpa domain name pointer 1-163-118-55.dynamic-ip.hinet.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
55.118.163.1.in-addr.arpa	name = 1-163-118-55.dynamic-ip.hinet.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
94.185.52.98 attack
Feb 10 06:01:41 pl3server sshd[6843]: reveeclipse mapping checking getaddrinfo for dynamic.isp.ooredoo.om [94.185.52.98] failed - POSSIBLE BREAK-IN ATTEMPT!
Feb 10 06:01:41 pl3server sshd[6843]: Invalid user mother from 94.185.52.98
Feb 10 06:01:41 pl3server sshd[6843]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.185.52.98
Feb 10 06:01:44 pl3server sshd[6843]: Failed password for invalid user mother from 94.185.52.98 port 52452 ssh2
Feb 10 06:01:44 pl3server sshd[6843]: Connection closed by 94.185.52.98 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=94.185.52.98
2020-02-10 13:34:35
122.117.77.109 attack
Honeypot attack, port: 81, PTR: 122-117-77-109.HINET-IP.hinet.net.
2020-02-10 14:03:28
218.92.0.184 attackspambots
frenzy
2020-02-10 13:37:44
71.6.233.140 attackbots
Portscan or hack attempt detected by psad/fwsnort
2020-02-10 13:43:07
218.92.0.175 attackspam
SSH bruteforce (Triggered fail2ban)
2020-02-10 13:25:25
89.248.168.62 attackbotsspam
Feb 10 05:57:14 debian-2gb-nbg1-2 kernel: \[3569870.691221\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=89.248.168.62 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=42991 PROTO=TCP SPT=47893 DPT=81 WINDOW=1024 RES=0x00 SYN URGP=0
2020-02-10 13:35:09
103.89.252.123 attackbotsspam
Feb  9 19:18:10 server sshd\[17374\]: Invalid user yax from 103.89.252.123
Feb  9 19:18:10 server sshd\[17374\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.89.252.123 
Feb  9 19:18:12 server sshd\[17374\]: Failed password for invalid user yax from 103.89.252.123 port 38626 ssh2
Feb 10 07:57:25 server sshd\[6464\]: Invalid user jvt from 103.89.252.123
Feb 10 07:57:25 server sshd\[6464\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.89.252.123 
...
2020-02-10 13:23:24
37.187.146.134 attack
Feb 10 00:29:59 plusreed sshd[25750]: Invalid user vns from 37.187.146.134
...
2020-02-10 13:52:20
106.12.197.232 attack
Feb 10 01:54:03 firewall sshd[24602]: Invalid user gnf from 106.12.197.232
Feb 10 01:54:05 firewall sshd[24602]: Failed password for invalid user gnf from 106.12.197.232 port 49480 ssh2
Feb 10 01:57:29 firewall sshd[24738]: Invalid user jkn from 106.12.197.232
...
2020-02-10 13:19:34
83.143.148.11 attackbots
Feb 10 06:12:40 sd-53420 sshd\[12107\]: Invalid user dg from 83.143.148.11
Feb 10 06:12:40 sd-53420 sshd\[12107\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.143.148.11
Feb 10 06:12:41 sd-53420 sshd\[12107\]: Failed password for invalid user dg from 83.143.148.11 port 52257 ssh2
Feb 10 06:21:56 sd-53420 sshd\[19770\]: Invalid user tdb from 83.143.148.11
Feb 10 06:21:56 sd-53420 sshd\[19770\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=83.143.148.11
...
2020-02-10 13:36:37
122.53.125.250 attack
Honeypot attack, port: 445, PTR: 122.53.125.250.static.pldt.net.
2020-02-10 13:38:01
187.111.23.14 attackbotsspam
$f2bV_matches
2020-02-10 13:24:48
187.202.37.230 attackspam
(sshd) Failed SSH login from 187.202.37.230 (MX/Mexico/dsl-187-202-37-230-dyn.prod-infinitum.com.mx): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Feb 10 05:57:11 elude sshd[8922]: Invalid user cys from 187.202.37.230 port 48648
Feb 10 05:57:13 elude sshd[8922]: Failed password for invalid user cys from 187.202.37.230 port 48648 ssh2
Feb 10 06:16:16 elude sshd[10225]: Invalid user pet from 187.202.37.230 port 10676
Feb 10 06:16:18 elude sshd[10225]: Failed password for invalid user pet from 187.202.37.230 port 10676 ssh2
Feb 10 06:19:18 elude sshd[10389]: Invalid user bkg from 187.202.37.230 port 31681
2020-02-10 13:36:10
217.128.248.189 attackbots
Honeypot attack, port: 445, PTR: laubervilliers-656-1-17-189.w217-128.abo.wanadoo.fr.
2020-02-10 13:46:08
222.186.30.167 attackbots
Fail2Ban Ban Triggered (2)
2020-02-10 13:39:00

Recently Reported IPs

1.163.116.106 1.163.112.179 1.163.116.192 1.163.12.249
1.163.120.128 103.110.12.5 1.163.12.20 1.163.122.123
1.163.13.153 1.163.13.215 1.163.122.120 1.163.13.39
1.163.15.85 1.163.14.162 1.163.123.57 1.163.162.121
1.163.171.116 103.110.14.167 1.163.171.186 1.163.172.188