城市(city): unknown
省份(region): unknown
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.21.70.109
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51499
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.21.70.109. IN A
;; AUTHORITY SECTION:
. 580 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022021701 1800 900 604800 86400
;; Query time: 85 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 02:48:30 CST 2022
;; MSG SIZE rcvd: 106Host 109.70.21.104.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 109.70.21.104.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 104.227.121.224 | attackbotsspam | (From eric@talkwithwebvisitor.com) Good day, My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations What for? Part of my job is to check out websites and the work you’ve done with andoverspinecenter.com definitely stands out. It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality. There is, however, a catch… more accurately, a question… So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know? More importantly, how do you make a connection with that person? Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind. Here’s a way to create INSTANT engagement that you may not have known about… Talk With Web Visitor is a software widget that’s works on your site, ready to capture |
2020-08-08 17:30:37 |
| 154.204.25.158 | attack | DATE:2020-08-08 11:00:15,IP:154.204.25.158,MATCHES:10,PORT:ssh |
2020-08-08 17:58:42 |
| 178.32.124.74 | attackbots | Unauthorized connection attempt detected from IP address 178.32.124.74 to port 8080 |
2020-08-08 17:46:37 |
| 128.199.212.194 | attackspam | 128.199.212.194 - - \[08/Aug/2020:09:15:18 +0200\] "POST /wp-login.php HTTP/1.0" 200 6400 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" 128.199.212.194 - - \[08/Aug/2020:09:15:26 +0200\] "POST /wp-login.php HTTP/1.0" 200 6267 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" 128.199.212.194 - - \[08/Aug/2020:09:15:29 +0200\] "POST /wp-login.php HTTP/1.0" 200 6263 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" |
2020-08-08 17:29:40 |
| 123.24.8.138 | attackbotsspam | Unauthorized IMAP connection attempt |
2020-08-08 17:52:34 |
| 51.79.161.170 | attackbotsspam | Cowrie Honeypot: 3 unauthorised SSH/Telnet login attempts between 2020-08-08T09:36:15Z and 2020-08-08T09:43:40Z |
2020-08-08 18:01:45 |
| 145.239.78.143 | attack | 145.239.78.143 - - \[08/Aug/2020:10:37:45 +0200\] "POST /wp-login.php HTTP/1.0" 200 6400 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" 145.239.78.143 - - \[08/Aug/2020:10:37:46 +0200\] "POST /wp-login.php HTTP/1.0" 200 6267 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" 145.239.78.143 - - \[08/Aug/2020:10:37:46 +0200\] "POST /wp-login.php HTTP/1.0" 200 6263 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" |
2020-08-08 17:33:29 |
| 101.231.166.39 | attack | $f2bV_matches |
2020-08-08 17:58:27 |
| 192.99.34.42 | attack | 192.99.34.42 - - [08/Aug/2020:10:29:37 +0100] "POST /wp-login.php HTTP/1.1" 200 5874 "-" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36" 192.99.34.42 - - [08/Aug/2020:10:31:08 +0100] "POST /wp-login.php HTTP/1.1" 200 5874 "-" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36" 192.99.34.42 - - [08/Aug/2020:10:32:31 +0100] "POST /wp-login.php HTTP/1.1" 200 5874 "-" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36" ... |
2020-08-08 17:36:09 |
| 106.69.206.155 | attack | Honeypot hit. |
2020-08-08 17:43:11 |
| 137.74.199.180 | attack | sshd: Failed password for .... from 137.74.199.180 port 57354 ssh2 (12 attempts) |
2020-08-08 17:50:43 |
| 218.18.101.84 | attack | Banned for a week because repeated abuses, for example SSH, but not only |
2020-08-08 18:06:16 |
| 142.90.1.45 | attackbotsspam | Lines containing failures of 142.90.1.45 Aug 6 05:21:50 mx-in-01 sshd[14141]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.90.1.45 user=r.r Aug 6 05:21:51 mx-in-01 sshd[14141]: Failed password for r.r from 142.90.1.45 port 49622 ssh2 Aug 6 05:21:52 mx-in-01 sshd[14141]: Received disconnect from 142.90.1.45 port 49622:11: Bye Bye [preauth] Aug 6 05:21:52 mx-in-01 sshd[14141]: Disconnected from authenticating user r.r 142.90.1.45 port 49622 [preauth] Aug 6 05:38:32 mx-in-01 sshd[15622]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.90.1.45 user=r.r ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=142.90.1.45 |
2020-08-08 18:07:34 |
| 129.211.33.59 | attackbots | Aug 8 10:16:37 ovpn sshd\[22261\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.33.59 user=root Aug 8 10:16:39 ovpn sshd\[22261\]: Failed password for root from 129.211.33.59 port 60136 ssh2 Aug 8 10:23:02 ovpn sshd\[23927\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.33.59 user=root Aug 8 10:23:04 ovpn sshd\[23927\]: Failed password for root from 129.211.33.59 port 47430 ssh2 Aug 8 10:29:32 ovpn sshd\[25625\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.33.59 user=root |
2020-08-08 17:55:41 |
| 130.185.155.34 | attackbots | Aug 8 08:12:06 server sshd[42408]: Failed password for root from 130.185.155.34 port 60612 ssh2 Aug 8 08:16:22 server sshd[43883]: Failed password for root from 130.185.155.34 port 44654 ssh2 Aug 8 08:20:43 server sshd[45382]: Failed password for root from 130.185.155.34 port 56932 ssh2 |
2020-08-08 17:47:08 |