City: unknown
Region: unknown
Country: China
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
| IP | Type | Details | Datetime |
|---|---|---|---|
| 121.206.49.9 | attackbotsspam | Jul 2 23:51:44 web1 postfix/smtpd[12928]: warning: unknown[121.206.49.9]: SASL LOGIN authentication failed: authentication failure ... |
2019-07-03 15:12:06 |
| 121.206.49.9 | attack | Jul 2 09:24:42 eola postfix/smtpd[20657]: warning: hostname 9.49.206.121.broad.zz.fj.dynamic.163data.com.cn does not resolve to address 121.206.49.9: Name or service not known Jul 2 09:24:42 eola postfix/smtpd[20657]: connect from unknown[121.206.49.9] Jul 2 09:24:42 eola postfix/smtpd[20659]: warning: hostname 9.49.206.121.broad.zz.fj.dynamic.163data.com.cn does not resolve to address 121.206.49.9: Name or service not known Jul 2 09:24:42 eola postfix/smtpd[20659]: connect from unknown[121.206.49.9] Jul 2 09:24:45 eola postfix/smtpd[20659]: lost connection after AUTH from unknown[121.206.49.9] Jul 2 09:24:45 eola postfix/smtpd[20659]: disconnect from unknown[121.206.49.9] ehlo=1 auth=0/1 commands=1/2 Jul 2 09:24:46 eola postfix/smtpd[20659]: warning: hostname 9.49.206.121.broad.zz.fj.dynamic.163data.com.cn does not resolve to address 121.206.49.9: Name or service not known Jul 2 09:24:46 eola postfix/smtpd[20659]: connect from unknown[121.206.49.9] Jul 2 09:24........ ------------------------------- |
2019-07-03 03:47:32 |
% [whois.apnic.net]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html
% Information related to '121.204.0.0 - 121.207.255.255'
% Abuse contact for '121.204.0.0 - 121.207.255.255' is 'anti-spam@chinatelecom.cn'
inetnum: 121.204.0.0 - 121.207.255.255
netname: CHINANET-FJ
descr: CHINANET Fujian province network
descr: China Telecom
descr: 7,East Street ,Fuzhou ,Fujian ,PRC
country: CN
admin-c: FH71-AP
tech-c: FH71-AP
abuse-c: AC1573-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-CHINANET-FJ
mnt-routes: MAINT-CHINANET-FJ
mnt-irt: IRT-CHINANET-CN
last-modified: 2021-06-15T08:05:32Z
source: APNIC
irt: IRT-CHINANET-CN
address: No.31 ,jingrong street,beijing
address: 100032
e-mail: anti-spam@chinatelecom.cn
abuse-mailbox: anti-spam@chinatelecom.cn
admin-c: CH93-AP
tech-c: CH93-AP
auth: # Filtered
remarks: anti-spam@chinatelecom.cn was validated on 2025-11-13
mnt-by: MAINT-CHINANET
last-modified: 2026-03-13T07:12:20Z
source: APNIC
role: ABUSE CHINANETCN
country: ZZ
address: No.31 ,jingrong street,beijing
address: 100032
phone: +000000000
e-mail: anti-spam@chinatelecom.cn
admin-c: CH93-AP
tech-c: CH93-AP
nic-hdl: AC1573-AP
remarks: Generated from irt object IRT-CHINANET-CN
remarks: anti-spam@chinatelecom.cn was validated on 2025-11-13
abuse-mailbox: anti-spam@chinatelecom.cn
mnt-by: APNIC-ABUSE
last-modified: 2025-11-13T14:15:15Z
source: APNIC
person: FUJIANNET HOSTMASTER
nic-hdl: FH71-AP
e-mail: fjnic@fjdcb.fz.fj.cn
address: 7,East Street ,Fuzhou ,Fujian ,PRC
phone: +86-591-83309761
fax-no: +86-591-83371954
country: CN
mnt-by: MAINT-CHINANET-FJ
last-modified: 2010-01-05T07:36:17Z
source: APNIC
% This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-AU5); <<>> DiG 9.10.3-P4-Ubuntu <<>> 121.206.49.105
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28162
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;121.206.49.105. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026042201 1800 900 604800 86400
;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Apr 23 02:30:07 CST 2026
;; MSG SIZE rcvd: 107105.49.206.121.in-addr.arpa domain name pointer 105.49.206.121.broad.zz.fj.dynamic.163data.com.cn.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
105.49.206.121.in-addr.arpa name = 105.49.206.121.broad.zz.fj.dynamic.163data.com.cn.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 5.178.87.186 | attackspam | Automatic report - Port Scan Attack |
2020-01-13 08:01:52 |
| 111.229.39.93 | attackbots | Unauthorized connection attempt detected from IP address 111.229.39.93 to port 2220 [J] |
2020-01-13 08:17:47 |
| 139.59.72.161 | attack | Jan 12 21:08:06 mx01 sshd[22255]: reveeclipse mapping checking getaddrinfo for cloud.imedihub.com [139.59.72.161] failed - POSSIBLE BREAK-IN ATTEMPT! Jan 12 21:08:06 mx01 sshd[22255]: Invalid user uftp from 139.59.72.161 Jan 12 21:08:06 mx01 sshd[22255]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.72.161 Jan 12 21:08:09 mx01 sshd[22255]: Failed password for invalid user uftp from 139.59.72.161 port 44900 ssh2 Jan 12 21:08:09 mx01 sshd[22255]: Received disconnect from 139.59.72.161: 11: Bye Bye [preauth] Jan 12 21:15:25 mx01 sshd[23493]: reveeclipse mapping checking getaddrinfo for cloud.imedihub.com [139.59.72.161] failed - POSSIBLE BREAK-IN ATTEMPT! Jan 12 21:15:25 mx01 sshd[23493]: Invalid user deploy from 139.59.72.161 Jan 12 21:15:25 mx01 sshd[23493]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.72.161 Jan 12 21:15:27 mx01 sshd[23493]: Failed password for invalid u........ ------------------------------- |
2020-01-13 08:14:38 |
| 216.126.239.124 | attackspam | (sshd) Failed SSH login from 216.126.239.124 (US/United States/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: Jan 12 16:23:10 host sshd[62926]: Did not receive identification string from 216.126.239.124 port 36612 |
2020-01-13 08:39:36 |
| 37.49.230.96 | attackspam | 37.49.230.96 was recorded 12 times by 1 hosts attempting to connect to the following ports: 65470,65472,65471,65473,65474,65466,65478,65479,65480,65410,65420,65430. Incident counter (4h, 24h, all-time): 12, 12, 163 |
2020-01-13 08:02:45 |
| 109.173.40.60 | attack | Unauthorized connection attempt detected from IP address 109.173.40.60 to port 2220 [J] |
2020-01-13 08:35:16 |
| 186.170.28.46 | attackbotsspam | Invalid user kaleb from 186.170.28.46 port 46510 |
2020-01-13 08:01:03 |
| 91.185.193.58 | attack | port scan and connect, tcp 1433 (ms-sql-s) |
2020-01-13 08:31:58 |
| 149.56.46.220 | attackspambots | Jan 12 21:41:12 XXX sshd[32682]: Invalid user server from 149.56.46.220 port 57268 |
2020-01-13 08:32:20 |
| 168.228.180.11 | attack | 1578864239 - 01/12/2020 22:23:59 Host: 168.228.180.11/168.228.180.11 Port: 445 TCP Blocked |
2020-01-13 08:18:50 |
| 112.85.42.176 | attack | Jan 13 00:09:36 unicornsoft sshd\[13679\]: User root from 112.85.42.176 not allowed because not listed in AllowUsers Jan 13 00:09:36 unicornsoft sshd\[13679\]: Failed none for invalid user root from 112.85.42.176 port 65149 ssh2 Jan 13 00:09:36 unicornsoft sshd\[13679\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.176 user=root |
2020-01-13 08:30:37 |
| 98.143.227.144 | attackbots | none |
2020-01-13 08:29:22 |
| 51.159.35.94 | attackbotsspam | Unauthorized connection attempt detected from IP address 51.159.35.94 to port 22 [T] |
2020-01-13 08:09:52 |
| 109.215.224.21 | attackbotsspam | 2020-01-13T00:13:08.1448691240 sshd\[7727\]: Invalid user user from 109.215.224.21 port 50686 2020-01-13T00:13:08.1681411240 sshd\[7727\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.215.224.21 2020-01-13T00:13:10.3555961240 sshd\[7727\]: Failed password for invalid user user from 109.215.224.21 port 50686 ssh2 ... |
2020-01-13 08:39:53 |
| 101.95.29.150 | attack | Unauthorized connection attempt detected from IP address 101.95.29.150 to port 2220 [J] |
2020-01-13 08:30:59 |