城市(city): unknown
省份(region): unknown
国家(country): Germany
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 93.135.124.242
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10553
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;93.135.124.242. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012100 1800 900 604800 86400
;; Query time: 38 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 21 23:08:50 CST 2025
;; MSG SIZE rcvd: 107
242.124.135.93.in-addr.arpa domain name pointer dynamic-093-135-124-242.93.135.pool.telefonica.de.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
242.124.135.93.in-addr.arpa name = dynamic-093-135-124-242.93.135.pool.telefonica.de.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 213.32.23.58 | attackspam | Aug 8 08:39:00 game-panel sshd[14936]: Failed password for root from 213.32.23.58 port 57248 ssh2 Aug 8 08:43:01 game-panel sshd[15188]: Failed password for root from 213.32.23.58 port 40116 ssh2 |
2020-08-08 17:04:58 |
| 148.163.82.221 | attackbots | Fail2Ban Ban Triggered HTTP SQL Injection Attempt |
2020-08-08 17:04:24 |
| 52.152.233.48 | attackbotsspam | Unauthorized IMAP connection attempt |
2020-08-08 17:00:09 |
| 122.152.196.222 | attackspam | SSH Brute Force |
2020-08-08 17:39:12 |
| 167.172.235.94 | attackbots | Aug 8 08:42:49 vps sshd[18320]: Failed password for root from 167.172.235.94 port 40744 ssh2 Aug 8 08:53:24 vps sshd[18989]: Failed password for root from 167.172.235.94 port 46328 ssh2 ... |
2020-08-08 17:21:28 |
| 107.172.49.134 | attackbotsspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found mechiroassist.org after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well. So here’s my question – what happens AFTER someone lands on your site? Anything? Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever. That means that all the work and effort you put into getting them to show up, goes down the tubes. Why would you want all that good work – and the great site you’ve built – go to waste? Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry. But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket? You can – thanks to revolutionary new software that |
2020-08-08 17:27:47 |
| 138.197.175.236 | attackspam |
|
2020-08-08 17:03:13 |
| 106.54.123.84 | attack | SSH Brute Force |
2020-08-08 16:54:19 |
| 107.180.71.116 | attackspambots | 107.180.71.116 - - [08/Aug/2020:06:24:55 +0200] "GET /wp-login.php HTTP/1.1" 200 6310 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 107.180.71.116 - - [08/Aug/2020:06:24:57 +0200] "POST /wp-login.php HTTP/1.1" 200 6561 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 107.180.71.116 - - [08/Aug/2020:06:24:58 +0200] "POST /xmlrpc.php HTTP/1.1" 200 427 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" |
2020-08-08 17:22:25 |
| 8.208.76.187 | attackspambots | Aug 8 05:53:34 rancher-0 sshd[901192]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=8.208.76.187 user=root Aug 8 05:53:35 rancher-0 sshd[901192]: Failed password for root from 8.208.76.187 port 36572 ssh2 ... |
2020-08-08 17:11:55 |
| 139.59.211.245 | attackbots | 2020-08-08T05:31:19.239393ns386461 sshd\[5799\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.211.245 user=root 2020-08-08T05:31:21.498539ns386461 sshd\[5799\]: Failed password for root from 139.59.211.245 port 39116 ssh2 2020-08-08T05:43:34.794550ns386461 sshd\[16402\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.211.245 user=root 2020-08-08T05:43:36.288399ns386461 sshd\[16402\]: Failed password for root from 139.59.211.245 port 40886 ssh2 2020-08-08T05:53:04.061468ns386461 sshd\[25563\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.211.245 user=root ... |
2020-08-08 17:36:49 |
| 212.19.99.12 | attack | 212.19.99.12 - - [08/Aug/2020:09:35:46 +0100] "POST /wp-login.php HTTP/1.1" 200 2435 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 212.19.99.12 - - [08/Aug/2020:09:35:47 +0100] "POST /wp-login.php HTTP/1.1" 200 2415 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 212.19.99.12 - - [08/Aug/2020:09:35:48 +0100] "POST /wp-login.php HTTP/1.1" 200 2415 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" ... |
2020-08-08 17:37:33 |
| 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 |
| 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 |
| 110.78.153.234 | attackspam | Unauthorized IMAP connection attempt |
2020-08-08 17:11:06 |