112.80.136.192

Basic Info

City: unknown

Region: unknown

Country: China

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:

Make a comment on this IP

No discussion about this IP yet. Click above link to make one.

Comments on same subnet:

IP	Type	Details	Datetime
112.80.136.135	attackspam	Unauthorized connection attempt detected from IP address 112.80.136.135 to port 8088	2020-06-01 00:45:42
112.80.136.245	attack	Unauthorized connection attempt detected from IP address 112.80.136.245 to port 3389 [J]	2020-03-02 21:35:54
112.80.136.176	attack	Unauthorized connection attempt detected from IP address 112.80.136.176 to port 8081 [J]	2020-03-02 18:41:32
112.80.136.214	attackbotsspam	Unauthorized connection attempt detected from IP address 112.80.136.214 to port 9999 [T]	2020-01-10 09:22:18
112.80.136.219	attackspam	Unauthorized connection attempt detected from IP address 112.80.136.219 to port 8118	2020-01-02 21:21:29
112.80.136.25	attack	The IP has triggered Cloudflare WAF. CF-Ray: 543405f8ef3b6cfe \| WAF_Rule_ID: 1112824 \| WAF_Kind: firewall \| CF_Action: challenge \| Country: CN \| CF_IPClass: noRecord \| Protocol: HTTP/1.1 \| Method: GET \| Host: blog.skk.moe \| User-Agent: Mozilla/5.0 (Linux; U; Android 4.3; en-us; SM-N900T Build/JSS15J) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30 \| CF_DC: SJC. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).	2019-12-12 03:33:44
112.80.136.8	attackspambots	The IP has triggered Cloudflare WAF. CF-Ray: 5415f75a7ae2288c \| WAF_Rule_ID: 3b40188685924a32bf11d40edea05a27 \| WAF_Kind: firewall \| CF_Action: challenge \| Country: CN \| CF_IPClass: noRecord \| Protocol: HTTP/1.1 \| Method: GET \| Host: disqus.skk.moe \| User-Agent: Mozilla/5.077692140 Mozilla/5.0 (Windows NT 6.1; Trident/7.0; rv:11.0) like Gecko \| CF_DC: SJC. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).	2019-12-08 04:38:18

Whois info:

Dig info:

; <<>> DiG 9.10.3-P4-Ubuntu <<>> 112.80.136.192
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 57040
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;112.80.136.192.			IN	A

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

;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 14 06:39:45 CST 2022
;; MSG SIZE  rcvd: 107

Host info

Host 192.136.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 192.136.80.112.in-addr.arpa: NXDOMAIN

Related IP info:

Related comments:

IP	Type	Details	Datetime
201.221.134.74	attack	2019-12-21 16:57:05 H=(201-221-134-74.telebucaramanga.net.co) [201.221.134.74]:45980 I=[192.147.25.65]:25 F= rejected RCPT : RBL: found in thrukfz5b56tq6xao6odgdyjrq.zen.dq.spamhaus.net (127.0.0.4, 127.0.0.3) (https://www.spamhaus.org/sbl/query/SBLCSS) 2019-12-21 16:57:05 H=(201-221-134-74.telebucaramanga.net.co) [201.221.134.74]:45980 I=[192.147.25.65]:25 F= rejected RCPT : RBL: found in thrukfz5b56tq6xao6odgdyjrq.zen.dq.spamhaus.net (127.0.0.4, 127.0.0.3) (https://www.spamhaus.org/sbl/query/SBLCSS) 2019-12-21 16:57:06 H=(201-221-134-74.telebucaramanga.net.co) [201.221.134.74]:45980 I=[192.147.25.65]:25 F= rejected RCPT : RBL: found in thrukfz5b56tq6xao6odgdyjrq.zen.dq.spamhaus.net (127.0.0.3, 127.0.0.4) (https://www.spamhaus.org/query/ip/201.221.134.74) ...	2019-12-22 08:41:22
128.199.95.163	attackspam	Dec 22 00:58:57 tux-35-217 sshd\[12455\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.95.163 user=root Dec 22 00:58:59 tux-35-217 sshd\[12455\]: Failed password for root from 128.199.95.163 port 35796 ssh2 Dec 22 01:04:47 tux-35-217 sshd\[12520\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.95.163 user=root Dec 22 01:04:49 tux-35-217 sshd\[12520\]: Failed password for root from 128.199.95.163 port 38890 ssh2 ...	2019-12-22 08:39:58
124.61.206.234	attack	$f2bV_matches	2019-12-22 08:28:16
203.125.145.58	attack	Dec 22 00:58:59 icinga sshd[3651]: Failed password for root from 203.125.145.58 port 58558 ssh2 ...	2019-12-22 08:39:22
223.202.201.166	attackspambots	Dec 22 00:38:13 lnxmysql61 sshd[10330]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.202.201.166 Dec 22 00:38:13 lnxmysql61 sshd[10330]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.202.201.166	2019-12-22 08:46:18
128.199.95.60	attackbots	Invalid user webadmin from 128.199.95.60 port 54918	2019-12-22 08:17:08
106.37.72.234	attackbotsspam	Dec 21 23:57:15 pornomens sshd\[27301\]: Invalid user biotech from 106.37.72.234 port 50642 Dec 21 23:57:15 pornomens sshd\[27301\]: pam_unix$sshd:auth$: authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.37.72.234 Dec 21 23:57:16 pornomens sshd\[27301\]: Failed password for invalid user biotech from 106.37.72.234 port 50642 ssh2 ...	2019-12-22 08:31:38
163.172.109.61	attackspambots	Attempted to connect 2 times to port 80 TCP	2019-12-22 08:11:52
114.219.56.124	attackbotsspam	Dec 22 00:47:50 microserver sshd[64591]: Invalid user haskin from 114.219.56.124 port 56130 Dec 22 00:47:50 microserver sshd[64591]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.219.56.124 Dec 22 00:47:52 microserver sshd[64591]: Failed password for invalid user haskin from 114.219.56.124 port 56130 ssh2 Dec 22 00:53:26 microserver sshd[65374]: Invalid user hinton from 114.219.56.124 port 52894 Dec 22 00:53:26 microserver sshd[65374]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.219.56.124 Dec 22 01:26:15 microserver sshd[5391]: Invalid user lisa from 114.219.56.124 port 36622 Dec 22 01:26:15 microserver sshd[5391]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.219.56.124 Dec 22 01:26:17 microserver sshd[5391]: Failed password for invalid user lisa from 114.219.56.124 port 36622 ssh2 Dec 22 01:32:45 microserver sshd[6262]: pam_unix(sshd:auth): authentication failure; logn	2019-12-22 08:22:28
179.217.5.25	attack	Honeypot attack, port: 23, PTR: b3d90519.virtua.com.br.	2019-12-22 08:38:03
45.141.86.103	attackbots	Dec 22 01:31:09 debian-2gb-nbg1-2 kernel: \[627423.386911\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=45.141.86.103 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=54037 PROTO=TCP SPT=58147 DPT=20000 WINDOW=1024 RES=0x00 SYN URGP=0	2019-12-22 08:43:03
95.110.159.28	attackbotsspam	Dec 21 19:33:15 ny01 sshd[27002]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.110.159.28 Dec 21 19:33:16 ny01 sshd[27002]: Failed password for invalid user steinmann from 95.110.159.28 port 44050 ssh2 Dec 21 19:39:05 ny01 sshd[27613]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.110.159.28	2019-12-22 08:40:30
197.44.136.33	attackbotsspam	Unauthorized IMAP connection attempt	2019-12-22 08:27:01
90.150.87.199	attackspam	'IP reached maximum auth failures for a one day block'	2019-12-22 08:23:00
90.71.180.43	attack	Honeypot attack, port: 445, PTR: 43.pool90-71-180.dynamic.orange.es.	2019-12-22 08:10:31

Recently Reported IPs

112.80.136.178	112.80.136.241	112.80.136.29	112.80.136.37
112.80.136.52	112.80.136.72	112.80.137.101	112.80.137.133
112.80.137.132	112.80.137.146	112.80.137.165	112.80.137.229
112.80.137.200	112.80.137.243	112.80.137.25	112.80.138.10
112.80.137.70	112.80.138.108	112.80.137.253	112.80.138.127