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

Region: Shaanxi

Country: China

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

;; QUESTION SECTION:
;113.143.92.164.			IN	A

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

;; Query time: 85 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Oct 04 15:15:27 CST 2024
;; MSG SIZE  rcvd: 107
Host info
Host 164.92.143.113.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 164.92.143.113.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
106.12.16.166 attack
Jul 26 14:14:18 server sshd\[28708\]: Invalid user appserver from 106.12.16.166 port 54578
Jul 26 14:14:18 server sshd\[28708\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.16.166
Jul 26 14:14:21 server sshd\[28708\]: Failed password for invalid user appserver from 106.12.16.166 port 54578 ssh2
Jul 26 14:18:10 server sshd\[27718\]: Invalid user admin from 106.12.16.166 port 60280
Jul 26 14:18:10 server sshd\[27718\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.16.166
2019-07-26 19:55:07
45.230.168.2 attackspambots
:
2019-07-26 20:15:59
122.114.168.143 attack
Jul 26 13:05:13 lnxded63 sshd[1421]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.114.168.143
2019-07-26 20:14:13
77.42.124.15 attackbotsspam
Honeypot attack, port: 23, PTR: PTR record not found
2019-07-26 19:44:30
103.249.181.28 attackspambots
Honeypot triggered via portsentry
2019-07-26 20:04:17
216.218.206.102 attackspambots
Splunk® : port scan detected:
Jul 26 05:58:51 testbed kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=82:c6:52:d1:6e:53:64:c3:d6:0b:ef:f0:08:00 SRC=216.218.206.102 DST=104.248.11.191 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=54321 PROTO=TCP SPT=49376 DPT=3389 WINDOW=65535 RES=0x00 SYN URGP=0
2019-07-26 19:57:34
197.232.39.97 attackbotsspam
firewall-block, port(s): 445/tcp
2019-07-26 20:11:28
203.88.158.74 attack
Unauthorized connection attempt from IP address 203.88.158.74 on Port 445(SMB)
2019-07-26 20:13:31
92.119.160.125 attackspambots
Jul 26 13:12:16 h2177944 kernel: \[2463570.256132\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=92.119.160.125 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=38549 PROTO=TCP SPT=45806 DPT=10094 WINDOW=1024 RES=0x00 SYN URGP=0 
Jul 26 13:16:34 h2177944 kernel: \[2463828.448151\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=92.119.160.125 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=10854 PROTO=TCP SPT=45806 DPT=10103 WINDOW=1024 RES=0x00 SYN URGP=0 
Jul 26 13:17:28 h2177944 kernel: \[2463882.616218\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=92.119.160.125 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=65156 PROTO=TCP SPT=45806 DPT=10024 WINDOW=1024 RES=0x00 SYN URGP=0 
Jul 26 13:23:45 h2177944 kernel: \[2464258.768062\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=92.119.160.125 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=61603 PROTO=TCP SPT=45806 DPT=10120 WINDOW=1024 RES=0x00 SYN URGP=0 
Jul 26 13:24:16 h2177944 kernel: \[2464289.743983\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=92.119.160.125 DST=85.
2019-07-26 19:45:32
192.162.237.36 attack
Jul 26 13:13:41 icinga sshd[29080]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.162.237.36
Jul 26 13:13:43 icinga sshd[29080]: Failed password for invalid user ubuntu from 192.162.237.36 port 49318 ssh2
...
2019-07-26 19:30:24
190.128.198.14 attack
Unauthorized connection attempt from IP address 190.128.198.14 on Port 445(SMB)
2019-07-26 19:52:13
42.51.195.155 attackspambots
:
2019-07-26 20:20:31
61.175.134.190 attackbotsspam
Jul 26 13:26:11 s64-1 sshd[26220]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.175.134.190
Jul 26 13:26:13 s64-1 sshd[26220]: Failed password for invalid user deploy from 61.175.134.190 port 37767 ssh2
Jul 26 13:32:12 s64-1 sshd[26297]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.175.134.190
...
2019-07-26 19:35:43
177.131.121.50 attackbots
Jul 26 11:13:59 ip-172-31-1-72 sshd\[20629\]: Invalid user loki from 177.131.121.50
Jul 26 11:13:59 ip-172-31-1-72 sshd\[20629\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.131.121.50
Jul 26 11:14:01 ip-172-31-1-72 sshd\[20629\]: Failed password for invalid user loki from 177.131.121.50 port 41266 ssh2
Jul 26 11:19:39 ip-172-31-1-72 sshd\[20720\]: Invalid user sergio from 177.131.121.50
Jul 26 11:19:39 ip-172-31-1-72 sshd\[20720\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.131.121.50
2019-07-26 19:30:42
60.14.147.241 attackbotsspam
Honeypot attack, port: 23, PTR: PTR record not found
2019-07-26 19:31:42

Recently Reported IPs

113.143.232.108 113.144.130.177 113.146.124.63 113.146.153.79
113.145.123.143 113.145.17.208 113.146.70.209 113.146.48.5
113.147.111.72 113.143.96.133 113.147.144.28 113.146.81.134
113.144.149.115 113.144.32.116 113.145.32.43 113.147.44.26
113.148.104.92 113.147.114.67 113.147.160.160 113.144.185.216