城市(city): unknown
省份(region): unknown
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 147.242.61.172
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 36961
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;147.242.61.172. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025031700 1800 900 604800 86400
;; Query time: 52 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Mar 17 20:47:21 CST 2025
;; MSG SIZE rcvd: 107Host 172.61.242.147.in-addr.arpa not found: 2(SERVFAIL)
server can't find 147.242.61.172.in-addr.arpa: SERVFAIL| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 42.200.66.164 | attack | SSH Brute Force, server-1 sshd[29191]: Failed password for invalid user 2010 from 42.200.66.164 port 58288 ssh2 |
2019-10-28 06:26:36 |
| 54.38.81.106 | attackbots | Oct 27 17:58:38 plusreed sshd[21559]: Invalid user corp from 54.38.81.106 ... |
2019-10-28 06:09:18 |
| 106.12.111.201 | attackspambots | 2019-10-27T21:35:35.553104abusebot-4.cloudsearch.cf sshd\[18319\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.111.201 user=root |
2019-10-28 05:56:37 |
| 92.118.37.97 | attack | 20191027 1451 UTC - Security Warning Intrusion - Port: 37566 |
2019-10-28 06:22:24 |
| 92.207.211.120 | attackspambots | RDP Bruteforce |
2019-10-28 05:53:36 |
| 193.188.22.229 | attackbotsspam | Oct 27 15:02:21 server1 sshd\[19538\]: Invalid user admin from 193.188.22.229 Oct 27 15:02:21 server1 sshd\[19538\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.188.22.229 Oct 27 15:02:24 server1 sshd\[19538\]: Failed password for invalid user admin from 193.188.22.229 port 18907 ssh2 Oct 27 15:02:25 server1 sshd\[19559\]: Invalid user admin from 193.188.22.229 Oct 27 15:02:25 server1 sshd\[19559\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.188.22.229 ... |
2019-10-28 06:05:35 |
| 178.128.223.243 | attack | 2019-10-27T21:34:03.457847abusebot-5.cloudsearch.cf sshd\[6867\]: Invalid user acceptable from 178.128.223.243 port 35068 |
2019-10-28 06:05:49 |
| 222.186.173.142 | attackspambots | Oct 27 22:16:45 ip-172-31-1-72 sshd\[3594\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.142 user=root Oct 27 22:16:47 ip-172-31-1-72 sshd\[3594\]: Failed password for root from 222.186.173.142 port 14150 ssh2 Oct 27 22:17:04 ip-172-31-1-72 sshd\[3594\]: Failed password for root from 222.186.173.142 port 14150 ssh2 Oct 27 22:17:15 ip-172-31-1-72 sshd\[3624\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.142 user=root Oct 27 22:17:17 ip-172-31-1-72 sshd\[3624\]: Failed password for root from 222.186.173.142 port 25618 ssh2 |
2019-10-28 06:27:25 |
| 185.62.85.150 | attack | Oct 27 22:15:09 vtv3 sshd\[25267\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.62.85.150 user=root Oct 27 22:15:11 vtv3 sshd\[25267\]: Failed password for root from 185.62.85.150 port 43436 ssh2 Oct 27 22:19:58 vtv3 sshd\[27405\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.62.85.150 user=root Oct 27 22:20:01 vtv3 sshd\[27405\]: Failed password for root from 185.62.85.150 port 33646 ssh2 Oct 27 22:23:22 vtv3 sshd\[29575\]: Invalid user Administrator from 185.62.85.150 port 44098 Oct 27 22:23:22 vtv3 sshd\[29575\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.62.85.150 Oct 27 22:33:53 vtv3 sshd\[2518\]: Invalid user smboracle from 185.62.85.150 port 47210 Oct 27 22:33:53 vtv3 sshd\[2518\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.62.85.150 Oct 27 22:33:55 vtv3 sshd\[2518\]: Failed password for invalid use |
2019-10-28 06:25:08 |
| 46.38.144.32 | attackbots | Oct 27 22:56:52 relay postfix/smtpd\[748\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 27 22:57:14 relay postfix/smtpd\[11476\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 27 22:57:51 relay postfix/smtpd\[7906\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 27 22:58:14 relay postfix/smtpd\[13073\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Oct 27 22:58:52 relay postfix/smtpd\[720\]: warning: unknown\[46.38.144.32\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2019-10-28 06:11:03 |
| 198.41.85.5 | attackspam | WordPress brute force |
2019-10-28 06:11:23 |
| 78.81.179.132 | attackbotsspam | Chat Spam |
2019-10-28 05:58:44 |
| 140.115.53.154 | attackbots | Oct 26 23:24:44 srv01 sshd[10436]: reveeclipse mapping checking getaddrinfo for sml-54-154.csie.ncu.edu.tw [140.115.53.154] failed - POSSIBLE BREAK-IN ATTEMPT! Oct 26 23:24:44 srv01 sshd[10436]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.115.53.154 user=r.r Oct 26 23:24:46 srv01 sshd[10436]: Failed password for r.r from 140.115.53.154 port 52928 ssh2 Oct 26 23:24:46 srv01 sshd[10436]: Received disconnect from 140.115.53.154: 11: Bye Bye [preauth] Oct 26 23:43:42 srv01 sshd[11194]: reveeclipse mapping checking getaddrinfo for sml-54-154.csie.ncu.edu.tw [140.115.53.154] failed - POSSIBLE BREAK-IN ATTEMPT! Oct 26 23:43:42 srv01 sshd[11194]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.115.53.154 user=r.r Oct 26 23:43:44 srv01 sshd[11194]: Failed password for r.r from 140.115.53.154 port 60122 ssh2 Oct 26 23:43:45 srv01 sshd[11194]: Received disconnect from 140.115.53.154: 11: ........ ------------------------------- |
2019-10-28 06:06:10 |
| 41.238.46.8 | attackbotsspam | Fail2Ban Ban Triggered |
2019-10-28 05:53:50 |
| 23.129.64.189 | attackspambots | detected by Fail2Ban |
2019-10-28 06:12:31 |