城市(city): Changsha
省份(region): Hunan
国家(country): China
运营商(isp): China Unicom
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
% [whois.apnic.net]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html
% Information related to '119.39.184.0 - 119.39.187.255'
% Abuse contact for '119.39.184.0 - 119.39.187.255' is 'zhaoyz3@chinaunicom.cn'
inetnum: 119.39.184.0 - 119.39.187.255
netname: shaoyang
country: CN
descr: CNC Group HuNan ShaoYang network
descr: NO.182 , BaoQing East Road,
descr: ShaoYang 422000
admin-c: CH444-AP
tech-c: CH444-AP
status: ASSIGNED NON-PORTABLE
mnt-by: MAINT-CNCGROUP-HN
last-modified: 2008-12-16T01:15:35Z
source: APNIC
person: CNCGroup Hostmaster
nic-hdl: CH444-AP
e-mail: hqs-ipabuse@chinaunicom.cn
address: No.21,Financial Street
address: Beijing,100033,P.R.China
phone: +86-10-66259764
fax-no: +86-10-66259764
country: CN
mnt-by: MAINT-CN-CUCGROUP
last-modified: 2017-09-05T06:36:14Z
source: APNIC
% Information related to '119.39.0.0/16AS4837'
route: 119.39.0.0/16
descr: CNC Group CHINA169 Hunan Province Network
country: CN
origin: AS4837
mnt-by: MAINT-CNCGROUP-RR
last-modified: 2008-09-04T07:55:11Z
source: APNIC
% This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-AU4)
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 119.39.184.67
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30353
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;119.39.184.67. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026051401 1800 900 604800 86400
;; Query time: 30 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri May 15 11:01:41 CST 2026
;; MSG SIZE rcvd: 106
Host 67.184.39.119.in-addr.arpa not found: 2(SERVFAIL)
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server: 183.60.82.98
Address: 183.60.82.98#53
** server can't find 67.184.39.119.in-addr.arpa: SERVFAIL
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 207.154.224.103 | attack | 207.154.224.103 - - [03/May/2020:11:11:16 +0200] "GET /wp-login.php HTTP/1.1" 200 6435 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 207.154.224.103 - - [03/May/2020:11:11:19 +0200] "POST /wp-login.php HTTP/1.1" 200 6686 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 207.154.224.103 - - [03/May/2020:11:11:20 +0200] "POST /xmlrpc.php HTTP/1.1" 200 427 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" |
2020-05-03 17:43:17 |
| 123.207.99.211 | attack | 05/02/2020-23:50:17.482972 123.207.99.211 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433 |
2020-05-03 17:23:00 |
| 68.183.236.92 | attackbots | 2020-05-03T07:29:31.586069abusebot-2.cloudsearch.cf sshd[14770]: Invalid user uap from 68.183.236.92 port 45040 2020-05-03T07:29:31.592586abusebot-2.cloudsearch.cf sshd[14770]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.236.92 2020-05-03T07:29:31.586069abusebot-2.cloudsearch.cf sshd[14770]: Invalid user uap from 68.183.236.92 port 45040 2020-05-03T07:29:33.353789abusebot-2.cloudsearch.cf sshd[14770]: Failed password for invalid user uap from 68.183.236.92 port 45040 ssh2 2020-05-03T07:34:43.859365abusebot-2.cloudsearch.cf sshd[14904]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.236.92 user=root 2020-05-03T07:34:45.450415abusebot-2.cloudsearch.cf sshd[14904]: Failed password for root from 68.183.236.92 port 35908 ssh2 2020-05-03T07:39:04.996794abusebot-2.cloudsearch.cf sshd[15110]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=68.183.236.92 u ... |
2020-05-03 17:21:41 |
| 194.26.29.203 | attackspam | May 3 11:28:03 mail kernel: [503701.908588] [UFW BLOCK] IN=eth0 OUT= MAC=00:16:3c:05:0d:89:f8:66:f2:68:66:ff:08:00 SRC=194.26.29.203 DST=77.73.69.240 LEN=40 TOS=0x00 PREC=0x00 TTL=250 ID=56007 PROTO=TCP SPT=52424 DPT=499 WINDOW=1024 RES=0x00 SYN URGP=0 ... |
2020-05-03 17:31:46 |
| 123.150.47.142 | attackspambots | Unauthorized connection attempt detected from IP address 123.150.47.142 to port 1433 |
2020-05-03 17:08:20 |
| 35.229.45.205 | attack | Attempt to hack Wordpress Login, XMLRPC or other login |
2020-05-03 17:36:25 |
| 141.98.81.253 | attackspam | Unauthorized connection attempt detected from IP address 141.98.81.253 to port 3389 [T] |
2020-05-03 17:29:45 |
| 128.199.253.146 | attackbotsspam | May 3 08:22:51 l02a sshd[11525]: Invalid user alex from 128.199.253.146 May 3 08:22:51 l02a sshd[11525]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.253.146 May 3 08:22:51 l02a sshd[11525]: Invalid user alex from 128.199.253.146 May 3 08:22:53 l02a sshd[11525]: Failed password for invalid user alex from 128.199.253.146 port 59323 ssh2 |
2020-05-03 17:30:02 |
| 45.55.210.248 | attackspam | May 3 12:01:54 ift sshd\[12583\]: Failed password for root from 45.55.210.248 port 54712 ssh2May 3 12:04:06 ift sshd\[12745\]: Failed password for root from 45.55.210.248 port 45193 ssh2May 3 12:06:18 ift sshd\[13200\]: Invalid user jun from 45.55.210.248May 3 12:06:20 ift sshd\[13200\]: Failed password for invalid user jun from 45.55.210.248 port 35674 ssh2May 3 12:08:38 ift sshd\[13519\]: Invalid user ota from 45.55.210.248 ... |
2020-05-03 17:42:07 |
| 51.178.78.152 | attackspambots | May 3 11:39:49 debian-2gb-nbg1-2 kernel: \[10757693.153826\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=51.178.78.152 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=54321 PROTO=TCP SPT=50609 DPT=1434 WINDOW=65535 RES=0x00 SYN URGP=0 |
2020-05-03 17:41:38 |
| 185.234.217.193 | attackspam | $f2bV_matches |
2020-05-03 17:26:29 |
| 213.32.67.160 | attackbots | Invalid user test from 213.32.67.160 port 41156 |
2020-05-03 17:03:03 |
| 139.99.121.6 | attack | Automatic report - Banned IP Access |
2020-05-03 17:19:20 |
| 106.12.175.38 | attackbots | k+ssh-bruteforce |
2020-05-03 17:18:11 |
| 109.123.117.233 | attack | firewall-block, port(s): 9000/tcp |
2020-05-03 17:33:57 |