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

城市(city): Hangzhou

省份(region): Zhejiang

国家(country): China

运营商(isp): China Mobile

主机名(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 '39.128.0.0 - 39.191.255.255'

% Abuse contact for '39.128.0.0 - 39.191.255.255' is 'abuse@chinamobile.com'

inetnum:        39.128.0.0 - 39.191.255.255
netname:        CMNET
descr:          China Mobile Communications Corporation
descr:          Mobile Communications Network Operator in China
descr:          Internet Service Provider in China
country:        CN
org:            ORG-CM1-AP
admin-c:        ct74-AP
tech-c:         HL1318-AP
abuse-c:        AC2006-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-CN-CMCC
mnt-routes:     MAINT-CN-CMCC
mnt-irt:        IRT-CHINAMOBILE-CN
last-modified:  2020-10-20T00:58:36Z
source:         APNIC

irt:            IRT-CHINAMOBILE-CN
address:        China Mobile Communications Corporation
address:        29, Jinrong Ave., Xicheng District, Beijing, 100032
e-mail:         abuse@chinamobile.com
abuse-mailbox:  abuse@chinamobile.com
admin-c:        CT74-AP
tech-c:         CT74-AP
auth:           # Filtered
remarks:        abuse@chinamobile.com was validated on 2026-09-30
mnt-by:         MAINT-CN-CMCC
last-modified:  2026-09-30T02:37:06Z
source:         APNIC

organisation:   ORG-CM1-AP
org-name:       China Mobile Communications Group Co., Ltd
org-type:       LIR
country:        CN
address:        29, Jinrong Ave.
phone:          +86-10-5268-6688
fax-no:         +86-10-5261-6187
e-mail:         hostmaster@chinamobile.com
mnt-ref:        APNIC-HM
mnt-by:         APNIC-HM
last-modified:  2026-07-31T13:46:41Z
source:         APNIC

role:           ABUSE CHINAMOBILECN
country:        ZZ
address:        China Mobile Communications Corporation
address:        29, Jinrong Ave., Xicheng District, Beijing, 100032
phone:          +000000000
e-mail:         abuse@chinamobile.com
admin-c:        CT74-AP
tech-c:         CT74-AP
nic-hdl:        AC2006-AP
remarks:        Generated from irt object IRT-CHINAMOBILE-CN
remarks:        abuse@chinamobile.com was validated on 2026-09-30
abuse-mailbox:  abuse@chinamobile.com
mnt-by:         APNIC-ABUSE
last-modified:  2026-09-30T02:37:41Z
source:         APNIC

role:           chinamobile tech
address:        29, Jinrong Ave.,Xicheng district
address:        Beijing
country:        CN
phone:          +86 5268 6688
fax-no:         +86 5261 6187
e-mail:         hostmaster@chinamobile.com
admin-c:        HL1318-AP
tech-c:         HL1318-AP
nic-hdl:        ct74-AP
notify:         hostmaster@chinamobile.com
mnt-by:         MAINT-cn-cmcc
abuse-mailbox:  abuse@chinamobile.com
last-modified:  2016-11-29T09:37:27Z
source:         APNIC

person:         haijun li
nic-hdl:        HL1318-AP
e-mail:         hostmaster@chinamobile.com
address:        29,Jinrong Ave, Xicheng district,beijing,100032
phone:          +86 1052686688
fax-no:         +86 10 52616187
country:        CN
mnt-by:         MAINT-CN-CMCC
abuse-mailbox:  abuse@chinamobile.com
last-modified:  2016-11-29T09:38:38Z
source:         APNIC

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

;; QUESTION SECTION:
;39.182.25.158.			IN	A

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

;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Oct 13 16:01:28 CST 2026
;; MSG SIZE  rcvd: 106
HOST信息:
Host 158.25.182.39.in-addr.arpa. not found: 3(NXDOMAIN)
NSLOOKUP信息:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 158.25.182.39.in-addr.arpa: NXDOMAIN
相关IP信息:
最新评论:
IP 类型 评论内容 时间
193.106.31.130 attack
[Mon May 04 06:59:48.888601 2020] [:error] [pid 5814:tid 140405012096768] [client 193.106.31.130:58933] [client 193.106.31.130] ModSecurity: Access denied with code 403 (phase 1). Match of "within %{tx.allowed_http_versions}" against "REQUEST_PROTOCOL" required. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "972"] [id "920430"] [msg "HTTP protocol version is not allowed by policy"] [data "HTTP/1.0"] [severity "CRITICAL"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/POLICY/PROTOCOL_NOT_ALLOWED"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A6"] [tag "PCI/6.5.10"] [hostname "karangploso.jatim.bmkg.go.id"] [uri "/administrator/index.php"] [unique_id "Xq9a9G4FUIT0i81cNYS77AAAAWk"]
...
2020-05-04 08:01:54
203.147.72.106 attackbotsspam
Brute force attempt
2020-05-04 07:50:58
186.113.18.109 attack
May  4 02:30:55 lukav-desktop sshd\[6438\]: Invalid user wedding from 186.113.18.109
May  4 02:30:55 lukav-desktop sshd\[6438\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.113.18.109
May  4 02:30:57 lukav-desktop sshd\[6438\]: Failed password for invalid user wedding from 186.113.18.109 port 44704 ssh2
May  4 02:35:10 lukav-desktop sshd\[11223\]: Invalid user visual from 186.113.18.109
May  4 02:35:10 lukav-desktop sshd\[11223\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.113.18.109
2020-05-04 08:13:22
118.24.20.171 attackbotsspam
2020-05-04T01:45:13.608702vps751288.ovh.net sshd\[4569\]: Invalid user hung from 118.24.20.171 port 42000
2020-05-04T01:45:13.617897vps751288.ovh.net sshd\[4569\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.20.171
2020-05-04T01:45:15.843565vps751288.ovh.net sshd\[4569\]: Failed password for invalid user hung from 118.24.20.171 port 42000 ssh2
2020-05-04T01:53:21.338679vps751288.ovh.net sshd\[4611\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.20.171  user=root
2020-05-04T01:53:23.223473vps751288.ovh.net sshd\[4611\]: Failed password for root from 118.24.20.171 port 55602 ssh2
2020-05-04 07:57:44
114.249.253.68 attackspambots
May  3 22:35:57 zimbra postfix/smtpd[13311]: lost connection after EHLO from unknown[114.249.253.68]
May  3 22:35:58 zimbra postfix/smtpd[18885]: lost connection after EHLO from unknown[114.249.253.68]
May  3 22:35:59 zimbra postfix/smtpd[13311]: lost connection after EHLO from unknown[114.249.253.68]
May  3 22:36:00 zimbra postfix/smtpd[18885]: lost connection after EHLO from unknown[114.249.253.68]
...
2020-05-04 08:16:54
183.245.99.59 attack
invalid user
2020-05-04 07:52:24
49.232.51.60 attack
May  4 01:51:45 mail1 sshd\[31268\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.51.60  user=root
May  4 01:51:48 mail1 sshd\[31268\]: Failed password for root from 49.232.51.60 port 52040 ssh2
May  4 01:57:10 mail1 sshd\[31331\]: Invalid user trash from 49.232.51.60 port 59082
May  4 01:57:10 mail1 sshd\[31331\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.51.60
May  4 01:57:13 mail1 sshd\[31331\]: Failed password for invalid user trash from 49.232.51.60 port 59082 ssh2
...
2020-05-04 08:31:00
59.10.5.156 attackspam
May  4 00:40:15 vpn01 sshd[18479]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.10.5.156
May  4 00:40:17 vpn01 sshd[18479]: Failed password for invalid user ks from 59.10.5.156 port 46706 ssh2
...
2020-05-04 08:00:32
179.106.82.142 attackbotsspam
23/tcp
[2020-05-03]1pkt
2020-05-04 07:52:51
168.138.144.172 attackspambots
Hacking
2020-05-04 08:21:01
190.198.40.212 attack
1588538200 - 05/03/2020 22:36:40 Host: 190.198.40.212/190.198.40.212 Port: 445 TCP Blocked
2020-05-04 07:46:46
115.29.12.78 attack
May  3 20:43:22 vps46666688 sshd[15473]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.29.12.78
May  3 20:43:24 vps46666688 sshd[15473]: Failed password for invalid user 123456 from 115.29.12.78 port 45775 ssh2
...
2020-05-04 08:09:56
167.99.115.204 attackspambots
May  4 00:38:01 vpn01 sshd[18408]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.115.204
May  4 00:38:02 vpn01 sshd[18408]: Failed password for invalid user test1 from 167.99.115.204 port 40598 ssh2
...
2020-05-04 07:58:31
37.49.230.13 attackspambots
Triggered: repeated knocking on closed ports.
2020-05-04 07:55:53
132.232.32.228 attackspam
May  4 00:26:48 markkoudstaal sshd[5273]: Failed password for root from 132.232.32.228 port 56576 ssh2
May  4 00:30:23 markkoudstaal sshd[6001]: Failed password for root from 132.232.32.228 port 42970 ssh2
2020-05-04 08:13:42

最近上报的IP列表

39.154.172.224 39.154.15.220 39.154.14.30 39.146.239.16
27.209.34.236 223.88.30.136 223.87.52.191 223.74.233.17
223.73.0.13 20.83.36.20 20.168.124.32 183.199.0.205
180.233.66.46 175.188.167.49 1.30.48.48 124.240.95.201
120.230.24.158 120.230.21.31 120.229.104.159 120.228.40.146