城市(city): unknown
省份(region): unknown
国家(country): Germany
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 134.92.78.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 38448
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;134.92.78.1. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012501 1800 900 604800 86400
;; Query time: 34 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 26 09:40:56 CST 2025
;; MSG SIZE rcvd: 104Host 1.78.92.134.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 1.78.92.134.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 114.220.71.68 | attack | Aug 17 09:12:59 localhost postfix/smtpd\[3229\]: warning: unknown\[114.220.71.68\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Aug 17 09:13:07 localhost postfix/smtpd\[3228\]: warning: unknown\[114.220.71.68\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Aug 17 09:13:20 localhost postfix/smtpd\[2695\]: warning: unknown\[114.220.71.68\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Aug 17 09:13:39 localhost postfix/smtpd\[3235\]: warning: unknown\[114.220.71.68\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Aug 17 09:13:46 localhost postfix/smtpd\[3456\]: warning: unknown\[114.220.71.68\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2019-08-18 02:11:22 |
| 58.250.18.118 | attackbotsspam | Aug 17 17:17:13 ncomp sshd[27669]: Invalid user zimbra from 58.250.18.118 Aug 17 17:17:13 ncomp sshd[27669]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.250.18.118 Aug 17 17:17:13 ncomp sshd[27669]: Invalid user zimbra from 58.250.18.118 Aug 17 17:17:16 ncomp sshd[27669]: Failed password for invalid user zimbra from 58.250.18.118 port 55820 ssh2 |
2019-08-18 02:04:28 |
| 181.63.248.213 | attackspambots | Aug 17 14:02:21 XXX sshd[47987]: Invalid user olimex from 181.63.248.213 port 51908 |
2019-08-18 01:41:33 |
| 202.29.53.131 | attackspambots | "Fail2Ban detected SSH brute force attempt" |
2019-08-18 01:48:37 |
| 177.44.17.113 | attack | $f2bV_matches |
2019-08-18 02:19:37 |
| 171.235.40.246 | attackbots | Automatic report - Port Scan Attack |
2019-08-18 01:58:42 |
| 94.102.56.252 | attackbotsspam | Aug 17 19:55:14 h2177944 kernel: \[4388196.811489\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=94.102.56.252 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=250 ID=51832 PROTO=TCP SPT=44651 DPT=10196 WINDOW=1024 RES=0x00 SYN URGP=0 Aug 17 19:56:14 h2177944 kernel: \[4388256.829886\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=94.102.56.252 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=250 ID=40329 PROTO=TCP SPT=44794 DPT=10816 WINDOW=1024 RES=0x00 SYN URGP=0 Aug 17 19:58:35 h2177944 kernel: \[4388398.516621\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=94.102.56.252 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=250 ID=24827 PROTO=TCP SPT=44803 DPT=10965 WINDOW=1024 RES=0x00 SYN URGP=0 Aug 17 19:59:59 h2177944 kernel: \[4388481.879952\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=94.102.56.252 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=250 ID=31134 PROTO=TCP SPT=44681 DPT=10318 WINDOW=1024 RES=0x00 SYN URGP=0 Aug 17 20:05:04 h2177944 kernel: \[4388787.026112\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=94.102.56.252 DST=85.214.1 |
2019-08-18 02:14:36 |
| 120.27.6.97 | attackspambots | "GET /?author=2 HTTP/1.1" 404 "GET /?author=3 HTTP/1.1" 404 "GET /?author=4 HTTP/1.1" 404 "GET /?author=5 HTTP/1.1" 404 "GET /?author=6 HTTP/1.1" 404 "GET /?author=7 HTTP/1.1" 404 "GET /?author=8 HTTP/1.1" 404 "GET /?author=9 HTTP/1.1" 404 |
2019-08-18 01:55:32 |
| 222.255.146.19 | attack | 2019-08-17T13:56:30.998810abusebot-7.cloudsearch.cf sshd\[1459\]: Invalid user infra from 222.255.146.19 port 57648 |
2019-08-18 01:49:15 |
| 154.98.202.116 | attackbots | Splunk® : Brute-Force login attempt on SSH: Aug 17 03:31:11 testbed sshd[24907]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=static.154.98.202.116.clients.your-server.de |
2019-08-18 01:42:12 |
| 159.65.54.221 | attackspam | Aug 17 20:03:35 vmd17057 sshd\[32243\]: Invalid user support from 159.65.54.221 port 59318 Aug 17 20:03:35 vmd17057 sshd\[32243\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.54.221 Aug 17 20:03:37 vmd17057 sshd\[32243\]: Failed password for invalid user support from 159.65.54.221 port 59318 ssh2 ... |
2019-08-18 02:18:11 |
| 5.152.159.31 | attackspam | Automated report - ssh fail2ban: Aug 17 20:00:39 authentication failure Aug 17 20:00:42 wrong password, user=backlog, port=46405, ssh2 |
2019-08-18 02:13:00 |
| 128.199.133.249 | attack | Tried sshing with brute force. |
2019-08-18 02:09:35 |
| 174.138.22.214 | attack | Splunk® : port scan detected: Aug 17 13:58:41 testbed kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=82:c6:52:d1:6e:53:64:c3:d6:0b:ef:f0:08:00 SRC=174.138.22.214 DST=104.248.11.191 LEN=40 TOS=0x00 PREC=0x00 TTL=249 ID=54321 PROTO=TCP SPT=56385 DPT=8088 WINDOW=65535 RES=0x00 SYN URGP=0 |
2019-08-18 02:14:01 |
| 129.204.3.37 | attackspambots | Aug 17 18:59:23 mail sshd\[17685\]: Failed password for invalid user sam from 129.204.3.37 port 35660 ssh2 Aug 17 19:18:53 mail sshd\[18307\]: Invalid user user2 from 129.204.3.37 port 42598 Aug 17 19:18:53 mail sshd\[18307\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.3.37 ... |
2019-08-18 02:23:14 |