City: Guangzhou
Region: Guangdong
Country: China
Internet Service Provider: 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 '27.47.128.0 - 27.47.255.255'
% Abuse contact for '27.47.128.0 - 27.47.255.255' is 'hqs-ipabuse@chinaunicom.cn'
inetnum: 27.47.128.0 - 27.47.255.255
netname: GuangZhou-unicom
descr: United-Communications-Network-Technology-Co-Ltd, GuangZhou
country: CN
admin-c: CG272-AP
tech-c: CG272-AP
abuse-c: AC1718-AP
status: ASSIGNED NON-PORTABLE
mnt-by: MAINT-CNCGROUP-GD
mnt-irt: IRT-CU-CN
last-modified: 2025-01-22T13:11:41Z
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
role: CNCGROUP GD
nic-hdl: CG272-AP
e-mail: gdipnoc@chinaunicom.cn
address: XinShiKong Plaza,No 666 Huangpu Rd. Guangzhou 510627,China
phone: +86-20-22214226
fax-no: +86-20-22214228
admin-c: RP181-AP
tech-c: RP181-AP
country: CN
mnt-by: MAINT-CNCGROUP-GD
last-modified: 2009-04-14T08:33:40Z
source: APNIC
% Information related to '27.47.0.0/16AS17622'
route: 27.47.0.0/16
descr: China Unicom Guangdong Province Network
country: CN
origin: AS17622
mnt-by: MAINT-CNCGROUP-RR
last-modified: 2011-05-11T01:22:02Z
source: APNIC
% This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-AU5); <<>> DiG 9.10.3-P4-Ubuntu <<>> 27.47.230.251
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46754
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;27.47.230.251. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026101201 1800 900 604800 86400
;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Oct 13 13:01:35 CST 2026
;; MSG SIZE rcvd: 106Host 251.230.47.27.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 251.230.47.27.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 141.98.9.159 | attackspam | IP attempted unauthorised action |
2020-04-17 07:40:11 |
| 62.210.203.12 | attackspambots | port scan |
2020-04-17 07:55:29 |
| 148.70.32.179 | attack | [ssh] SSH attack |
2020-04-17 07:54:41 |
| 141.98.9.157 | attackspambots | IP attempted unauthorised action |
2020-04-17 07:44:19 |
| 78.128.113.99 | attackspambots | Apr 17 00:19:01 mail postfix/smtpd\[11895\]: warning: unknown\[78.128.113.99\]: SASL PLAIN authentication failed: \ Apr 17 01:02:23 mail postfix/smtpd\[12625\]: warning: unknown\[78.128.113.99\]: SASL PLAIN authentication failed: \ Apr 17 01:02:50 mail postfix/smtpd\[12551\]: warning: unknown\[78.128.113.99\]: SASL PLAIN authentication failed: \ Apr 17 01:09:19 mail postfix/smtpd\[12625\]: warning: unknown\[78.128.113.99\]: SASL PLAIN authentication failed: \ |
2020-04-17 07:30:53 |
| 200.105.173.98 | attackspambots | 20/4/16@19:31:45: FAIL: Alarm-Network address from=200.105.173.98 20/4/16@19:31:45: FAIL: Alarm-Network address from=200.105.173.98 ... |
2020-04-17 07:56:11 |
| 167.99.71.160 | attackspam | Apr 16 17:23:34 server1 sshd\[32638\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.71.160 user=root Apr 16 17:23:36 server1 sshd\[32638\]: Failed password for root from 167.99.71.160 port 58986 ssh2 Apr 16 17:27:49 server1 sshd\[1352\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.71.160 user=root Apr 16 17:27:51 server1 sshd\[1352\]: Failed password for root from 167.99.71.160 port 36634 ssh2 Apr 16 17:32:01 server1 sshd\[2713\]: Invalid user ansible from 167.99.71.160 ... |
2020-04-17 07:37:18 |
| 31.46.16.95 | attack | Apr 17 01:30:04 vps647732 sshd[21909]: Failed password for root from 31.46.16.95 port 36344 ssh2 Apr 17 01:31:57 vps647732 sshd[22084]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.46.16.95 ... |
2020-04-17 07:44:50 |
| 14.248.83.163 | attack | Bruteforce detected by fail2ban |
2020-04-17 07:52:04 |
| 218.240.137.68 | attackbots | Apr 17 01:23:15 prox sshd[16810]: Failed password for root from 218.240.137.68 port 43630 ssh2 Apr 17 01:33:54 prox sshd[10969]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.240.137.68 |
2020-04-17 07:45:45 |
| 112.85.42.188 | attackspam | 04/16/2020-19:45:52.854174 112.85.42.188 Protocol: 6 ET SCAN Potential SSH Scan |
2020-04-17 07:46:34 |
| 111.229.199.67 | attack | Apr 17 01:31:42 host sshd[13365]: Invalid user ru from 111.229.199.67 port 49108 ... |
2020-04-17 08:01:01 |
| 180.164.126.13 | attackbotsspam | 20 attempts against mh-ssh on echoip |
2020-04-17 07:27:36 |
| 220.135.203.77 | attack | Port probing on unauthorized port 8080 |
2020-04-17 07:47:28 |
| 210.210.165.45 | attackbotsspam | port scan and connect, tcp 23 (telnet) |
2020-04-17 07:29:18 |