必须是合法有效的IP地址, 可以是IPv4或者是IPv6, 例如127.0.0.1或者2001:DB8:0:0:8:800:200C:417A
基本信息:

城市(city): unknown

省份(region): unknown

国家(country): China

运营商(isp): China Unicom

主机名(hostname): unknown

机构(organization): unknown

使用类型(Usage Type): unknown

用户上报:
暂无关于此IP的讨论, 沙发请点上方按钮
相同子网IP讨论:
暂无关于此IP所属子网相关IP的讨论.
WHOIS信息:
% [whois.apnic.net]
% Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html

% Information related to '182.112.0.0 - 182.127.255.255'

% Abuse contact for '182.112.0.0 - 182.127.255.255' is 'hqs-ipabuse@chinaunicom.cn'

inetnum:        182.112.0.0 - 182.127.255.255
netname:        UNICOM-HA
descr:          China Unicom Henan province network
descr:          China Unicom
descr:          No.21,Ji-Rong Street,
descr:          Beijing 100032
country:        CN
admin-c:        CH1302-AP
tech-c:         WW444-AP
abuse-c:        AC1718-AP
status:         ALLOCATED PORTABLE
remarks:        service provider
remarks:        --------------------------------------------------------
remarks:        To report network abuse, please contact mnt-irt
remarks:        For troubleshooting, please contact tech-c and admin-c
remarks:        Report invalid contact via www.apnic.net/invalidcontact
remarks:        --------------------------------------------------------
mnt-by:         APNIC-HM
mnt-lower:      MAINT-CNCGROUP-HA
mnt-routes:     MAINT-CNCGROUP-RR
mnt-irt:        IRT-CU-CN
last-modified:  2023-10-21T03:39:30Z
source:         APNIC

irt:            IRT-CU-CN
address:        No.21,Financial Street
address:        Beijing,100033
address:        P.R.China
e-mail:         hqs-ipabuse@chinaunicom.cn
abuse-mailbox:  hqs-ipabuse@chinaunicom.cn
admin-c:        CH1302-AP
tech-c:         CH1302-AP
auth:           # Filtered
remarks:        hqs-ipabuse@chinaunicom.cn was validated on 2026-08-19
mnt-by:         MAINT-CNCGROUP
last-modified:  2026-08-19T00:57:22Z
source:         APNIC

role:           ABUSE CUCN
country:        ZZ
address:        No.21,Financial Street
address:        Beijing,100033
address:        P.R.China
phone:          +000000000
e-mail:         hqs-ipabuse@chinaunicom.cn
admin-c:        CH1302-AP
tech-c:         CH1302-AP
nic-hdl:        AC1718-AP
remarks:        Generated from irt object IRT-CU-CN
remarks:        hqs-ipabuse@chinaunicom.cn was validated on 2026-08-19
abuse-mailbox:  hqs-ipabuse@chinaunicom.cn
mnt-by:         APNIC-ABUSE
last-modified:  2026-08-20T03:22:23Z
source:         APNIC

person:         ChinaUnicom Hostmaster
nic-hdl:        CH1302-AP
e-mail:         hqs-ipabuse@chinaunicom.cn
address:        No.21,Jin-Rong Street
address:        Beijing,100033
address:        P.R.China
phone:          +86-10-66259764
fax-no:         +86-10-66259764
country:        CN
mnt-by:         MAINT-CNCGROUP
last-modified:  2017-08-17T06:13:16Z
source:         APNIC

person:         Wei Wang
nic-hdl:        WW444-AP
e-mail:         abuse@public.zz.ha.cn
address:        #55 San Quan Road, Zhengzhou, Henan Provice
phone:          +86-371-65952358
fax-no:         +86-371-65968952
country:        CN
mnt-by:         MAINT-CNCGROUP-HA
last-modified:  2010-03-05T08:20:01Z
source:         APNIC

% Information related to '182.112.0.0/12AS4837'

route:          182.112.0.0/12
descr:          China Unicom Henan Province Network
country:        CN
origin:         AS4837
mnt-by:         MAINT-CNCGROUP-RR
last-modified:  2010-03-02T01:06:01Z
source:         APNIC

% This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-AU5)
DIG信息:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 182.119.133.159
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 61363
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;182.119.133.159.		IN	A

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

;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Oct 27 15:02:20 CST 2026
;; MSG SIZE  rcvd: 108
HOST信息:
159.133.119.182.in-addr.arpa domain name pointer hn.kd.ny.adsl.
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
159.133.119.182.in-addr.arpa	name = hn.kd.ny.adsl.

Authoritative answers can be found from:
相关IP信息:
最新评论:
IP 类型 评论内容 时间
49.235.1.23 attackbots
Sep  7 15:27:14 [host] sshd[8425]: pam_unix(sshd:a
Sep  7 15:27:16 [host] sshd[8425]: Failed password
Sep  7 15:31:09 [host] sshd[8563]: pam_unix(sshd:a
2020-09-07 23:41:14
61.177.172.61 attackbotsspam
2020-09-07T15:30:19.700078abusebot-8.cloudsearch.cf sshd[10098]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.177.172.61  user=root
2020-09-07T15:30:21.452927abusebot-8.cloudsearch.cf sshd[10098]: Failed password for root from 61.177.172.61 port 64770 ssh2
2020-09-07T15:30:24.892921abusebot-8.cloudsearch.cf sshd[10098]: Failed password for root from 61.177.172.61 port 64770 ssh2
2020-09-07T15:30:19.700078abusebot-8.cloudsearch.cf sshd[10098]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.177.172.61  user=root
2020-09-07T15:30:21.452927abusebot-8.cloudsearch.cf sshd[10098]: Failed password for root from 61.177.172.61 port 64770 ssh2
2020-09-07T15:30:24.892921abusebot-8.cloudsearch.cf sshd[10098]: Failed password for root from 61.177.172.61 port 64770 ssh2
2020-09-07T15:30:19.700078abusebot-8.cloudsearch.cf sshd[10098]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruse
...
2020-09-07 23:33:25
222.186.175.163 attackbots
2020-09-07T17:31:04.833123 sshd[2886563]: Unable to negotiate with 222.186.175.163 port 8396: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1 [preauth]
2020-09-07T17:31:04.929882 sshd[2886565]: Unable to negotiate with 222.186.175.163 port 52780: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1 [preauth]
2020-09-07T17:37:51.778206 sshd[2890730]: Unable to negotiate with 222.186.175.163 port 27732: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1 [preauth]
2020-09-07 23:44:17
109.64.66.118 attack
Unauthorised login to NAS
2020-09-07 23:48:21
145.239.82.87 attack
Sep  7 16:49:14 rotator sshd\[25214\]: Failed password for root from 145.239.82.87 port 44189 ssh2Sep  7 16:49:16 rotator sshd\[25214\]: Failed password for root from 145.239.82.87 port 44189 ssh2Sep  7 16:49:18 rotator sshd\[25214\]: Failed password for root from 145.239.82.87 port 44189 ssh2Sep  7 16:49:21 rotator sshd\[25214\]: Failed password for root from 145.239.82.87 port 44189 ssh2Sep  7 16:49:23 rotator sshd\[25214\]: Failed password for root from 145.239.82.87 port 44189 ssh2Sep  7 16:49:25 rotator sshd\[25214\]: Failed password for root from 145.239.82.87 port 44189 ssh2
...
2020-09-07 23:27:53
111.207.207.97 attackspam
Sep  7 14:58:39 pornomens sshd\[12265\]: Invalid user tta from 111.207.207.97 port 6664
Sep  7 14:58:39 pornomens sshd\[12265\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.207.207.97
Sep  7 14:58:41 pornomens sshd\[12265\]: Failed password for invalid user tta from 111.207.207.97 port 6664 ssh2
...
2020-09-07 23:26:33
23.108.46.43 attackbotsspam
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found drmichaeltwalsh.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well.

So here’s my question – what happens AFTER someone lands on your site?  Anything?

Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever.

That means that all the work and effort you put into getting them to show up, goes down the tubes.

Why would you want all that good work – and the great site you’ve built – go to waste?

Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry.

But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket?
  
You can – thanks to revolutionary new software tha
2020-09-07 23:42:31
49.234.56.138 attackbots
Sep  5 17:53:56 woof sshd[13292]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.56.138  user=r.r
Sep  5 17:53:58 woof sshd[13292]: Failed password for r.r from 49.234.56.138 port 50218 ssh2
Sep  5 17:53:58 woof sshd[13292]: Received disconnect from 49.234.56.138: 11: Bye Bye [preauth]
Sep  5 18:02:13 woof sshd[13854]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.56.138  user=r.r
Sep  5 18:02:15 woof sshd[13854]: Failed password for r.r from 49.234.56.138 port 35694 ssh2
Sep  5 18:02:16 woof sshd[13854]: Received disconnect from 49.234.56.138: 11: Bye Bye [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=49.234.56.138
2020-09-07 23:46:15
106.13.141.110 attack
Sep  7 14:53:33 mavik sshd[24909]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.141.110
Sep  7 14:53:36 mavik sshd[24909]: Failed password for invalid user volition from 106.13.141.110 port 36598 ssh2
Sep  7 14:57:01 mavik sshd[25041]: Invalid user mada from 106.13.141.110
Sep  7 14:57:01 mavik sshd[25041]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.141.110
Sep  7 14:57:03 mavik sshd[25041]: Failed password for invalid user mada from 106.13.141.110 port 47344 ssh2
...
2020-09-08 00:00:22
109.110.167.217 attackbots
Honeypot attack, port: 445, PTR: 109-110-167-217-dynamic.shabdiznet.com.
2020-09-07 23:47:41
192.3.199.170 attackbots
Sep  7 16:34:36 router sshd[5355]: Failed password for root from 192.3.199.170 port 47253 ssh2
Sep  7 16:34:36 router sshd[5357]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.199.170 
...
2020-09-07 23:25:06
191.102.156.164 attack
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found wattfamilychiropractic.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well.

So here’s my question – what happens AFTER someone lands on your site?  Anything?

Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever.

That means that all the work and effort you put into getting them to show up, goes down the tubes.

Why would you want all that good work – and the great site you’ve built – go to waste?

Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry.

But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket?
  
You can – thanks to revolutionary new softw
2020-09-07 23:31:53
222.89.70.216 attack
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: tcp cat: Potentially Bad Trafficbytes: 60
2020-09-07 23:47:20
222.186.42.7 attackspambots
Sep  7 17:34:20 minden010 sshd[25009]: Failed password for root from 222.186.42.7 port 13823 ssh2
Sep  7 17:34:24 minden010 sshd[25009]: Failed password for root from 222.186.42.7 port 13823 ssh2
Sep  7 17:34:26 minden010 sshd[25009]: Failed password for root from 222.186.42.7 port 13823 ssh2
...
2020-09-07 23:35:50
190.199.246.243 attackbots
Icarus honeypot on github
2020-09-07 23:27:25

最近上报的IP列表

1.14.93.143 134.122.16.198 42.228.115.198 39.184.22.100
39.154.11.186 39.148.87.76 223.91.40.164 183.199.184.45
183.197.74.237 182.51.86.68 171.35.86.46 120.239.27.172
119.112.149.29 112.9.1.191 103.116.123.203 198.65.60.74
149.165.153.135 122.177.105.45 199.165.159.9 199.165.159.14