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: 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:
IP Type Details Datetime
112.80.138.90 attack
Unauthorized connection attempt detected from IP address 112.80.138.90 to port 1022 [T]
2020-05-20 10:22:53
112.80.138.255 attackbots
Unauthorized connection attempt detected from IP address 112.80.138.255 to port 3389 [J]
2020-03-02 21:35:30
112.80.138.109 attackspam
Unauthorized connection attempt detected from IP address 112.80.138.109 to port 80 [J]
2020-01-19 14:19:47
112.80.138.223 attackbots
Unauthorized connection attempt detected from IP address 112.80.138.223 to port 2095
2019-12-31 08:57:15
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 112.80.138.160
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24534
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;112.80.138.160.			IN	A

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

;; Query time: 100 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 16:08:54 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 160.138.80.112.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 160.138.80.112.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
191.35.164.218 attackspambots
Port Scan: TCP/1433
2019-10-20 18:46:07
190.2.156.118 attack
DATE:2019-10-20 05:47:27, IP:190.2.156.118, PORT:telnet Telnet brute force auth on honeypot server (honey-neo-dc)
2019-10-20 18:18:04
206.81.8.14 attackbotsspam
Oct 20 11:57:20 localhost sshd\[25711\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.81.8.14  user=root
Oct 20 11:57:23 localhost sshd\[25711\]: Failed password for root from 206.81.8.14 port 50398 ssh2
Oct 20 12:00:54 localhost sshd\[26092\]: Invalid user admin from 206.81.8.14 port 44324
2019-10-20 18:15:10
212.48.71.182 attackbots
C2,WP GET /2017/wp-login.php
2019-10-20 18:54:57
121.15.140.178 attackbotsspam
Oct 19 21:51:11 sachi sshd\[21416\]: Invalid user ackmann from 121.15.140.178
Oct 19 21:51:11 sachi sshd\[21416\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.15.140.178
Oct 19 21:51:13 sachi sshd\[21416\]: Failed password for invalid user ackmann from 121.15.140.178 port 37976 ssh2
Oct 19 21:56:31 sachi sshd\[21784\]: Invalid user 123456 from 121.15.140.178
Oct 19 21:56:31 sachi sshd\[21784\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.15.140.178
2019-10-20 18:23:39
112.78.1.86 attack
Attempted WordPress login: "GET /2017/wp-login.php"
2019-10-20 18:49:53
14.161.8.40 attack
scan z
2019-10-20 18:24:28
184.105.139.67 attackspambots
PORT-SCAN
2019-10-20 18:41:42
43.224.249.224 attack
Oct 20 06:15:45 localhost sshd\[28628\]: Invalid user 12 from 43.224.249.224
Oct 20 06:15:45 localhost sshd\[28628\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.224.249.224
Oct 20 06:15:47 localhost sshd\[28628\]: Failed password for invalid user 12 from 43.224.249.224 port 33231 ssh2
Oct 20 06:24:22 localhost sshd\[28880\]: Invalid user established from 43.224.249.224
Oct 20 06:24:22 localhost sshd\[28880\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.224.249.224
...
2019-10-20 18:37:54
89.248.174.214 attackbots
10/20/2019-06:05:46.832298 89.248.174.214 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-10-20 18:35:29
139.99.78.208 attack
Oct 20 10:46:50 localhost sshd\[75769\]: Invalid user adminuser from 139.99.78.208 port 58416
Oct 20 10:46:50 localhost sshd\[75769\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.99.78.208
Oct 20 10:46:52 localhost sshd\[75769\]: Failed password for invalid user adminuser from 139.99.78.208 port 58416 ssh2
Oct 20 10:51:27 localhost sshd\[75919\]: Invalid user test from 139.99.78.208 port 42080
Oct 20 10:51:27 localhost sshd\[75919\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.99.78.208
...
2019-10-20 18:52:04
117.34.72.226 attackbotsspam
SMB Server BruteForce Attack
2019-10-20 18:30:24
159.203.201.224 attackspambots
firewall-block, port(s): 52047/tcp
2019-10-20 18:40:36
223.202.201.138 attackspambots
Oct 20 07:24:37 server sshd\[30466\]: Invalid user kit from 223.202.201.138 port 18624
Oct 20 07:24:37 server sshd\[30466\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.202.201.138
Oct 20 07:24:39 server sshd\[30466\]: Failed password for invalid user kit from 223.202.201.138 port 18624 ssh2
Oct 20 07:29:40 server sshd\[9985\]: Invalid user wapidc from 223.202.201.138 port 38057
Oct 20 07:29:40 server sshd\[9985\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.202.201.138
2019-10-20 18:35:50
175.137.26.128 attack
C1,WP GET /manga/wp-login.php
2019-10-20 18:15:26

Recently Reported IPs

112.80.138.149 112.80.138.201 112.80.138.186 112.80.138.205
112.80.138.207 112.80.138.215 112.80.138.241 112.80.138.229
112.80.138.31 112.80.138.44 112.80.138.45 112.80.138.55
112.80.138.52 112.80.138.58 112.80.138.61 112.80.138.73
112.80.138.97 112.80.138.74 112.80.138.78 112.80.139.106