城市(city): unknown
省份(region): unknown
国家(country): Sweden
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 85.194.152.91
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 5384
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;85.194.152.91. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021400 1800 900 604800 86400
;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 15 00:02:18 CST 2025
;; MSG SIZE rcvd: 10691.152.194.85.in-addr.arpa domain name pointer 91.152.194.85.sta.ac-net.se.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
91.152.194.85.in-addr.arpa name = 91.152.194.85.sta.ac-net.se.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 190.120.191.13 | attackspam | 20/6/3@07:48:46: FAIL: Alarm-Network address from=190.120.191.13 20/6/3@07:48:47: FAIL: Alarm-Network address from=190.120.191.13 ... |
2020-06-04 02:42:11 |
| 68.183.146.249 | attackbots | Automatic report - Banned IP Access |
2020-06-04 02:49:37 |
| 176.95.138.32 | attackspam | Jun 3 17:16:51 xeon sshd[55954]: Failed password for root from 176.95.138.32 port 50616 ssh2 |
2020-06-04 02:43:05 |
| 185.171.156.4 | attackbotsspam | Lines containing failures of 185.171.156.4 Jun 1 07:16:22 kmh-wsh-001-nbg01 sshd[30982]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.171.156.4 user=r.r Jun 1 07:16:24 kmh-wsh-001-nbg01 sshd[30982]: Failed password for r.r from 185.171.156.4 port 50616 ssh2 Jun 1 07:16:24 kmh-wsh-001-nbg01 sshd[30982]: Received disconnect from 185.171.156.4 port 50616:11: Bye Bye [preauth] Jun 1 07:16:24 kmh-wsh-001-nbg01 sshd[30982]: Disconnected from authenticating user r.r 185.171.156.4 port 50616 [preauth] Jun 1 07:34:51 kmh-wsh-001-nbg01 sshd[427]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.171.156.4 user=r.r Jun 1 07:34:53 kmh-wsh-001-nbg01 sshd[427]: Failed password for r.r from 185.171.156.4 port 55932 ssh2 Jun 1 07:34:53 kmh-wsh-001-nbg01 sshd[427]: Received disconnect from 185.171.156.4 port 55932:11: Bye Bye [preauth] Jun 1 07:34:53 kmh-wsh-001-nbg01 sshd[427]: Disconnecte........ ------------------------------ |
2020-06-04 02:48:21 |
| 54.37.68.191 | attack | Jun 3 19:30:28 localhost sshd\[31951\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.68.191 user=root Jun 3 19:30:30 localhost sshd\[31951\]: Failed password for root from 54.37.68.191 port 37930 ssh2 Jun 3 19:33:11 localhost sshd\[32011\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.68.191 user=root Jun 3 19:33:13 localhost sshd\[32011\]: Failed password for root from 54.37.68.191 port 56040 ssh2 Jun 3 19:35:48 localhost sshd\[32269\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.68.191 user=root ... |
2020-06-04 02:39:23 |
| 116.127.231.17 | attackbots | $f2bV_matches |
2020-06-04 02:51:30 |
| 89.252.232.82 | attack | Jun 3 21:15:25 debian kernel: [110689.511143] [UFW BLOCK] IN=eth0 OUT= MAC=52:54:00:be:e4:65:08:e8:4f:6e:48:0c:08:00 SRC=89.252.232.82 DST=89.252.131.35 LEN=44 TOS=0x00 PREC=0x00 TTL=237 ID=2587 DF PROTO=TCP SPT=1089 DPT=8291 WINDOW=14600 RES=0x00 SYN URGP=0 |
2020-06-04 02:36:33 |
| 39.98.92.52 | attackbotsspam | 39.98.92.52 - - [03/Jun/2020:17:45:07 +0200] "GET /wp-login.php HTTP/1.1" 200 6225 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 39.98.92.52 - - [03/Jun/2020:17:45:17 +0200] "POST /wp-login.php HTTP/1.1" 200 6390 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 39.98.92.52 - - [03/Jun/2020:17:45:25 +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-06-04 02:56:35 |
| 114.40.98.132 | attackbots | GET http://api.gxout.com/proxy/check.aspx : ET POLICY Proxy GET Request |
2020-06-04 03:04:35 |
| 106.52.236.23 | attackbots | SSH brute force attempt |
2020-06-04 03:12:20 |
| 175.6.102.248 | attackspam | 2020-06-03T14:33:56.774075dmca.cloudsearch.cf sshd[8871]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.6.102.248 user=root 2020-06-03T14:33:58.439933dmca.cloudsearch.cf sshd[8871]: Failed password for root from 175.6.102.248 port 50998 ssh2 2020-06-03T14:36:22.869141dmca.cloudsearch.cf sshd[9034]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.6.102.248 user=root 2020-06-03T14:36:24.909592dmca.cloudsearch.cf sshd[9034]: Failed password for root from 175.6.102.248 port 49792 ssh2 2020-06-03T14:38:54.441171dmca.cloudsearch.cf sshd[9222]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.6.102.248 user=root 2020-06-03T14:38:56.683577dmca.cloudsearch.cf sshd[9222]: Failed password for root from 175.6.102.248 port 48588 ssh2 2020-06-03T14:41:20.425756dmca.cloudsearch.cf sshd[9391]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ... |
2020-06-04 02:58:49 |
| 183.88.216.27 | attack | Unauthorized connection attempt from IP address 183.88.216.27 on Port 143(IMAP) |
2020-06-04 03:02:46 |
| 187.18.108.73 | attackbots | Jun 3 14:51:22 vpn01 sshd[5242]: Failed password for root from 187.18.108.73 port 60883 ssh2 ... |
2020-06-04 02:38:18 |
| 13.209.68.44 | attack | Jun 1 05:41:30 host2 sshd[7911]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-13-209-68-44.ap-northeast-2.compute.amazonaws.com user=r.r Jun 1 05:41:32 host2 sshd[7911]: Failed password for r.r from 13.209.68.44 port 54332 ssh2 Jun 1 05:41:32 host2 sshd[7911]: Received disconnect from 13.209.68.44: 11: Bye Bye [preauth] Jun 1 06:20:00 host2 sshd[27410]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-13-209-68-44.ap-northeast-2.compute.amazonaws.com user=r.r Jun 1 06:20:03 host2 sshd[27410]: Failed password for r.r from 13.209.68.44 port 47168 ssh2 Jun 1 06:20:03 host2 sshd[27410]: Received disconnect from 13.209.68.44: 11: Bye Bye [preauth] Jun 1 06:27:06 host2 sshd[23221]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=em3-13-209-68-44.ap-northeast-2.compute.amazonaws.com user=r.r Jun 1 06:27:09 host2 sshd[23221]: Failed passwo........ ------------------------------- |
2020-06-04 03:10:10 |
| 45.61.163.175 | attack | (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 advancedchirosolutions.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 capt |
2020-06-04 03:11:31 |