城市(city): unknown
省份(region): unknown
国家(country): Viet Nam
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 14.224.170.69
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 38602
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;14.224.170.69. IN A
;; AUTHORITY SECTION:
. 166 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022020700 1800 900 604800 86400
;; Query time: 80 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 07 18:32:16 CST 2022
;; MSG SIZE rcvd: 10669.170.224.14.in-addr.arpa domain name pointer static.vnpt.vn.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
69.170.224.14.in-addr.arpa name = static.vnpt.vn.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 216.244.66.248 | attackbotsspam | 21 attempts against mh-misbehave-ban on leaf |
2020-02-24 20:35:26 |
| 91.139.53.63 | attackspam | Lines containing failures of 91.139.53.63 /var/log/mail.err:Feb 24 05:32:18 server01 postfix/smtpd[30727]: warning: hostname 91-139-53-63.customers.tmcz.cz does not resolve to address 91.139.53.63: Name or service not known /var/log/apache/pucorp.org.log:Feb 24 05:32:18 server01 postfix/smtpd[30727]: warning: hostname 91-139-53-63.customers.tmcz.cz does not resolve to address 91.139.53.63: Name or service not known /var/log/apache/pucorp.org.log:Feb 24 05:32:18 server01 postfix/smtpd[30727]: connect from unknown[91.139.53.63] /var/log/apache/pucorp.org.log:Feb x@x /var/log/apache/pucorp.org.log:Feb x@x /var/log/apache/pucorp.org.log:Feb 24 05:32:19 server01 postfix/policy-spf[30735]: : Policy action=PREPEND Received-SPF: none (e4t.cz: No applicable sender policy available) receiver=x@x /var/log/apache/pucorp.org.log:Feb x@x /var/log/apache/pucorp.org.log:Feb 24 05:32:22 server01 postfix/smtpd[30727]: lost connection after DATA from unknown[91.139.53.63] /var/log/apache/p........ ------------------------------ |
2020-02-24 20:48:13 |
| 106.52.151.34 | attackbotsspam | Feb 23 20:35:25 host sshd[24582]: Invalid user zhangyan from 106.52.151.34 Feb 23 20:35:25 host sshd[24582]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.52.151.34 Feb 23 20:35:26 host sshd[24582]: Failed password for invalid user zhangyan from 106.52.151.34 port 47808 ssh2 Feb 23 20:35:27 host sshd[24582]: Received disconnect from 106.52.151.34: 11: Bye Bye [preauth] Feb 23 20:35:28 host sshd[24707]: Invalid user dff from 106.52.151.34 Feb 23 20:35:28 host sshd[24707]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.52.151.34 Feb 23 20:35:30 host sshd[24707]: Failed password for invalid user dff from 106.52.151.34 port 49852 ssh2 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=106.52.151.34 |
2020-02-24 20:59:02 |
| 59.127.165.230 | attackspambots | unauthorized connection attempt |
2020-02-24 21:02:36 |
| 218.92.0.207 | attackspam | Feb 23 21:54:03 cumulus sshd[28947]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.207 user=r.r Feb 23 21:54:04 cumulus sshd[28961]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.207 user=r.r Feb 23 21:54:04 cumulus sshd[28957]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.207 user=r.r Feb 23 21:54:04 cumulus sshd[28947]: Failed password for r.r from 218.92.0.207 port 42855 ssh2 Feb 23 21:54:05 cumulus sshd[28959]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.207 user=r.r Feb 23 21:54:05 cumulus sshd[28962]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.207 user=r.r Feb 23 21:54:06 cumulus sshd[28961]: Failed password for r.r from 218.92.0.207 port 40377 ssh2 Feb 23 21:54:06 cumulus sshd[28957]: Failed password f........ ------------------------------- |
2020-02-24 20:43:28 |
| 89.248.172.16 | attackbotsspam | Fail2Ban Ban Triggered |
2020-02-24 20:21:36 |
| 171.224.20.65 | attackbots | Email rejected due to spam filtering |
2020-02-24 20:31:22 |
| 59.127.133.205 | attackbots | firewall-block, port(s): 445/tcp |
2020-02-24 20:58:24 |
| 171.236.165.114 | attackbots | Email rejected due to spam filtering |
2020-02-24 20:39:06 |
| 119.27.165.134 | attackbots | suspicious action Mon, 24 Feb 2020 01:43:54 -0300 |
2020-02-24 20:26:00 |
| 122.117.63.58 | attackbotsspam | Port probing on unauthorized port 23 |
2020-02-24 20:21:15 |
| 172.105.201.117 | attackspam | Unauthorized connection attempt detected from IP address 172.105.201.117 to port 23 |
2020-02-24 20:53:20 |
| 59.126.109.145 | attackspam | unauthorized connection attempt |
2020-02-24 20:39:27 |
| 14.184.3.254 | attackspambots | DATE:2020-02-24 05:41:28, IP:14.184.3.254, PORT:1433 MSSQL brute force auth on honeypot server (epe-honey1-hq) |
2020-02-24 20:39:43 |
| 189.254.33.157 | attack | Feb 24 12:42:09 lnxweb61 sshd[24507]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.254.33.157 Feb 24 12:42:09 lnxweb61 sshd[24507]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.254.33.157 |
2020-02-24 20:30:38 |