城市(city): unknown
省份(region): unknown
国家(country): unknown
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
b'
; <<>> DiG 9.11.3-1ubuntu1.15-Ubuntu <<>> 2001:8d8:97d:3800::41:65d8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 42271
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;2001:8d8:97d:3800::41:65d8. IN A
;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Sat Feb 19 00:36:00 CST 2022
;; MSG SIZE rcvd: 55
'
8.d.5.6.1.4.0.0.0.0.0.0.0.0.0.0.0.0.8.3.d.7.9.0.8.d.8.0.1.0.0.2.ip6.arpa domain name pointer kino-zeit.de.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
8.d.5.6.1.4.0.0.0.0.0.0.0.0.0.0.0.0.8.3.d.7.9.0.8.d.8.0.1.0.0.2.ip6.arpa name = kino-zeit.de.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 191.23.113.164 | attack | Oct 2 22:34:06 mx01 sshd[15750]: reveeclipse mapping checking getaddrinfo for 191-23-113-164.user.vivozap.com.br [191.23.113.164] failed - POSSIBLE BREAK-IN ATTEMPT! Oct 2 22:34:06 mx01 sshd[15750]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=191.23.113.164 user=r.r Oct 2 22:34:08 mx01 sshd[15750]: Failed password for r.r from 191.23.113.164 port 53720 ssh2 Oct 2 22:34:08 mx01 sshd[15750]: Received disconnect from 191.23.113.164: 11: Bye Bye [preauth] Oct 2 22:34:10 mx01 sshd[15754]: reveeclipse mapping checking getaddrinfo for 191-23-113-164.user.vivozap.com.br [191.23.113.164] failed - POSSIBLE BREAK-IN ATTEMPT! Oct 2 22:34:11 mx01 sshd[15754]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=191.23.113.164 user=r.r Oct 2 22:34:12 mx01 sshd[15754]: Failed password for r.r from 191.23.113.164 port 53804 ssh2 Oct 2 22:34:12 mx01 sshd[15754]: Received disconnect from 191.23.113.1........ ------------------------------- |
2020-10-03 21:10:38 |
| 131.196.216.39 | attack | 20 attempts against mh-ssh on ice |
2020-10-03 20:46:01 |
| 51.254.32.102 | attack | SSH brutforce |
2020-10-03 21:08:05 |
| 190.167.244.87 | attack | Lines containing failures of 190.167.244.87 Oct 2 22:27:15 shared04 sshd[2191]: Did not receive identification string from 190.167.244.87 port 3192 Oct 2 22:27:17 shared04 sshd[2195]: Invalid user user1 from 190.167.244.87 port 3994 Oct 2 22:27:17 shared04 sshd[2195]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.167.244.87 Oct 2 22:27:19 shared04 sshd[2195]: Failed password for invalid user user1 from 190.167.244.87 port 3994 ssh2 Oct 2 22:27:20 shared04 sshd[2195]: Connection closed by invalid user user1 190.167.244.87 port 3994 [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=190.167.244.87 |
2020-10-03 20:53:20 |
| 46.101.5.144 | attack | 20 attempts against mh-ssh on soil |
2020-10-03 21:13:46 |
| 83.97.20.35 | attack | IP was detected trying to Brute-Force SSH, FTP, Web Apps, Port-Scan or Hacking. |
2020-10-03 22:00:50 |
| 42.234.238.34 | attackspambots | 404 NOT FOUND |
2020-10-03 22:04:06 |
| 114.129.168.188 | attackspam | [MK-VM5] Blocked by UFW |
2020-10-03 21:11:24 |
| 46.101.8.39 | attackbots | 20 attempts against mh-ssh on comet |
2020-10-03 20:58:32 |
| 119.45.46.159 | attackbots | Oct 3 00:00:36 vpn01 sshd[11557]: Failed password for root from 119.45.46.159 port 48192 ssh2 ... |
2020-10-03 20:55:04 |
| 176.109.184.235 | attack | Automated report (2020-10-03T00:30:09+02:00). Spambot detected. |
2020-10-03 20:44:20 |
| 103.57.220.28 | attackspambots | Automatic report - Banned IP Access |
2020-10-03 20:59:32 |
| 104.131.110.155 | attackbots | Invalid user oracle from 104.131.110.155 port 45714 |
2020-10-03 20:51:43 |
| 122.51.248.76 | attackbotsspam | Invalid user toor from 122.51.248.76 port 48458 |
2020-10-03 20:47:50 |
| 1.255.48.197 | attack | (From annabelle@merchantpay.top) I have a quick question about working with your business. Like most business owners you just want to survive through to 2021. In order for that to happen you need to save every dollar possible right? This is an honest question, would you continue with the high credit card processing fees if there was another way? New laws are on your side. Test this newly released card processing model this October - just send a phone number and we'll call. $24.99/mo Flat Fee Credit Card Processing (Unlimited) 1) As a small business owner accepting credit/debit, recently passed State Laws are on your side. - Were you aware? New state regulations now in effect, the law was successfully passed in 46 states - effective since August 2019. Since that date you shouldn't be paying above 0.75% Credit Card Processing Fees. 2) You're legally able to demand this new option. Bottom Line: Your processor isn't telling you everything. Why are they hiding the lower fee options? We repre |
2020-10-03 20:52:07 |