城市(city): Witbank
省份(region): Mpumalanga
国家(country): South Africa
运营商(isp): Vodacom
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 41.1.85.116
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24449
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;41.1.85.116. IN A
;; AUTHORITY SECTION:
. 170 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022022202 1800 900 604800 86400
;; Query time: 67 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 23 11:17:26 CST 2022
;; MSG SIZE rcvd: 104Host 116.85.1.41.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 116.85.1.41.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 139.28.223.142 | attackbots | Dec 25 07:05:51 web01 postfix/smtpd[18756]: connect from unknown[139.28.223.142] Dec 25 07:05:51 web01 policyd-spf[20379]: None; identhostnamey=helo; client-ip=139.28.223.142; helo=deer.elevotal.com; envelope-from=x@x Dec 25 07:05:51 web01 policyd-spf[20379]: Pass; identhostnamey=mailfrom; client-ip=139.28.223.142; helo=deer.elevotal.com; envelope-from=x@x Dec x@x Dec 25 07:05:51 web01 postfix/smtpd[18756]: disconnect from unknown[139.28.223.142] Dec 25 07:08:03 web01 postfix/smtpd[20713]: connect from unknown[139.28.223.142] Dec 25 07:08:03 web01 policyd-spf[20715]: None; identhostnamey=helo; client-ip=139.28.223.142; helo=deer.elevotal.com; envelope-from=x@x Dec 25 07:08:03 web01 policyd-spf[20715]: Pass; identhostnamey=mailfrom; client-ip=139.28.223.142; helo=deer.elevotal.com; envelope-from=x@x Dec x@x Dec 25 07:08:03 web01 postfix/smtpd[20713]: disconnect from unknown[139.28.223.142] Dec 25 07:10:40 web01 postfix/smtpd[20713]: connect from unknown[139.28.223.142] D........ ------------------------------- |
2019-12-25 17:00:07 |
| 198.23.206.155 | attackbotsspam | (From edwardfrankish32@gmail.com) Hi! Did you know that the first page of Goggle search results is where all potential clients will be looking at if they're searching for products/services? Does your website appear on the first page of Google search results when you try searching for your products/services? Most of the time, they would just ignore page 2 and so on since the results listed on the first page seem more relevant and are more credible. I'm very familiar with all the algorithms and methods that search engines use and I am an expert on how to get the most out of it. I'm a freelance online marketing specialist, and I have helped my clients bring their websites to the first page of web searches for more than 10 years now. Also, the cost of my services is something that small businesses can afford. I can give you a free consultation so you can be better informed of how your website is doing right now, what can be done and what to expect after if this is something that interests you. Kindly wri |
2019-12-25 17:28:59 |
| 45.134.179.57 | attackbotsspam | Dec 25 09:59:22 debian-2gb-nbg1-2 kernel: \[917097.542678\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=45.134.179.57 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=63933 PROTO=TCP SPT=50593 DPT=8707 WINDOW=1024 RES=0x00 SYN URGP=0 |
2019-12-25 17:01:00 |
| 82.81.12.247 | attackspam | Automatic report - Banned IP Access |
2019-12-25 16:59:21 |
| 196.52.43.103 | attackspam | " " |
2019-12-25 16:50:28 |
| 184.105.139.84 | attackbotsspam | " " |
2019-12-25 16:56:57 |
| 191.54.61.50 | attack | Automatic report - Port Scan Attack |
2019-12-25 16:54:42 |
| 95.167.150.10 | attack | Unauthorized connection attempt detected from IP address 95.167.150.10 to port 445 |
2019-12-25 17:24:29 |
| 81.28.173.7 | attackbots | Unauthorized connection attempt detected from IP address 81.28.173.7 to port 445 |
2019-12-25 16:52:01 |
| 81.182.254.124 | attackbotsspam | [Aegis] @ 2019-12-25 09:44:15 0000 -> Attempted Administrator Privilege Gain: ET SCAN LibSSH Based Frequent SSH Connections Likely BruteForce Attack |
2019-12-25 17:17:24 |
| 42.55.180.112 | attackbotsspam | Dec 25 01:13:55 esmtp postfix/smtpd[1358]: lost connection after AUTH from unknown[42.55.180.112] Dec 25 01:14:00 esmtp postfix/smtpd[1341]: lost connection after AUTH from unknown[42.55.180.112] Dec 25 01:14:17 esmtp postfix/smtpd[1358]: lost connection after AUTH from unknown[42.55.180.112] Dec 25 01:14:26 esmtp postfix/smtpd[1358]: lost connection after AUTH from unknown[42.55.180.112] Dec 25 01:14:30 esmtp postfix/smtpd[1341]: lost connection after AUTH from unknown[42.55.180.112] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=42.55.180.112 |
2019-12-25 17:07:43 |
| 116.239.254.100 | attackspambots | 2019-12-25 00:26:08 H=(ylmf-pc) [116.239.254.100]:50653 I=[192.147.25.65]:25 rejected EHLO or HELO ylmf-pc: CHECK_HELO: ylmf-pc 2019-12-25 00:26:14 H=(ylmf-pc) [116.239.254.100]:50186 I=[192.147.25.65]:25 rejected EHLO or HELO ylmf-pc: CHECK_HELO: ylmf-pc 2019-12-25 00:26:20 H=(ylmf-pc) [116.239.254.100]:50703 I=[192.147.25.65]:25 rejected EHLO or HELO ylmf-pc: CHECK_HELO: ylmf-pc ... |
2019-12-25 17:12:43 |
| 221.215.203.218 | attackspam | Dec 24 11:29:46 vpxxxxxxx22308 sshd[17418]: Invalid user www from 221.215.203.218 Dec 24 11:29:46 vpxxxxxxx22308 sshd[17418]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.215.203.218 Dec 24 11:29:48 vpxxxxxxx22308 sshd[17418]: Failed password for invalid user www from 221.215.203.218 port 21024 ssh2 Dec 24 11:32:34 vpxxxxxxx22308 sshd[17850]: Invalid user takadasa from 221.215.203.218 Dec 24 11:32:34 vpxxxxxxx22308 sshd[17850]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.215.203.218 Dec 24 11:32:37 vpxxxxxxx22308 sshd[17850]: Failed password for invalid user takadasa from 221.215.203.218 port 43042 ssh2 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=221.215.203.218 |
2019-12-25 17:18:51 |
| 196.196.39.199 | attackbots | Automatic report - Banned IP Access |
2019-12-25 16:51:23 |
| 128.71.241.67 | attackspam | Unauthorized connection attempt detected from IP address 128.71.241.67 to port 139 |
2019-12-25 17:16:46 |