城市(city): Boardman
省份(region): Oregon
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 54.245.85.213
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3284
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;54.245.85.213. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025022000 1800 900 604800 86400
;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 18:18:09 CST 2025
;; MSG SIZE rcvd: 106213.85.245.54.in-addr.arpa domain name pointer ec2-54-245-85-213.us-west-2.compute.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
213.85.245.54.in-addr.arpa name = ec2-54-245-85-213.us-west-2.compute.amazonaws.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 107.183.168.189 | attackspam | (From eric@talkwithwebvisitor.com) Hello, my name’s Eric and I just ran across your website at mcleodchiropractic.com... I found it after a quick search, so your SEO’s working out… Content looks pretty good… One thing’s missing though… A QUICK, EASY way to connect with you NOW. Because studies show that a web lead like me will only hang out a few seconds – 7 out of 10 disappear almost instantly, Surf Surf Surf… then gone forever. I have the solution: Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number. You’ll know immediately they’re interested and you can call them directly to TALK with them - literally while they’re still on the web looking at your site. CLICK HERE http://www.talkwithwebvisitor.com to try out a Live Demo with Talk With Web Visitor now to see exactly how it works and even give it a try… it could be huge for your business. Plus, now that you’ve got that phone number, with our new |
2020-06-03 02:14:33 |
| 157.230.19.72 | attackbots | prod6 ... |
2020-06-03 02:13:50 |
| 111.186.57.98 | attack | SSH Brute-Forcing (server1) |
2020-06-03 02:28:04 |
| 89.151.186.173 | attackspambots | Automatic report - Port Scan Attack |
2020-06-03 02:14:58 |
| 105.247.34.121 | attack | 1591099308 - 06/02/2020 14:01:48 Host: 105.247.34.121/105.247.34.121 Port: 445 TCP Blocked |
2020-06-03 02:35:18 |
| 115.231.231.3 | attackspam | Jun 2 14:07:29 Tower sshd[33935]: Connection from 115.231.231.3 port 56678 on 192.168.10.220 port 22 rdomain "" Jun 2 14:07:31 Tower sshd[33935]: Failed password for root from 115.231.231.3 port 56678 ssh2 Jun 2 14:07:31 Tower sshd[33935]: Received disconnect from 115.231.231.3 port 56678:11: Bye Bye [preauth] Jun 2 14:07:31 Tower sshd[33935]: Disconnected from authenticating user root 115.231.231.3 port 56678 [preauth] |
2020-06-03 02:24:59 |
| 129.211.171.24 | attackbots | 2020-06-02T17:55:30.998879abusebot-2.cloudsearch.cf sshd[20011]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.171.24 user=root 2020-06-02T17:55:32.413013abusebot-2.cloudsearch.cf sshd[20011]: Failed password for root from 129.211.171.24 port 55664 ssh2 2020-06-02T17:58:13.697811abusebot-2.cloudsearch.cf sshd[20066]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.171.24 user=root 2020-06-02T17:58:15.819668abusebot-2.cloudsearch.cf sshd[20066]: Failed password for root from 129.211.171.24 port 42072 ssh2 2020-06-02T18:01:05.312311abusebot-2.cloudsearch.cf sshd[20103]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.171.24 user=root 2020-06-02T18:01:07.047708abusebot-2.cloudsearch.cf sshd[20103]: Failed password for root from 129.211.171.24 port 56716 ssh2 2020-06-02T18:03:59.113514abusebot-2.cloudsearch.cf sshd[20181]: pam_unix(sshd:auth): ... |
2020-06-03 02:18:22 |
| 104.203.108.218 | attack | Unauthorized connection attempt from IP address 104.203.108.218 on Port 445(SMB) |
2020-06-03 02:12:47 |
| 178.128.123.111 | attackbotsspam | Jun 2 18:36:31 ns382633 sshd\[32042\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.123.111 user=root Jun 2 18:36:33 ns382633 sshd\[32042\]: Failed password for root from 178.128.123.111 port 43642 ssh2 Jun 2 18:51:30 ns382633 sshd\[2431\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.123.111 user=root Jun 2 18:51:31 ns382633 sshd\[2431\]: Failed password for root from 178.128.123.111 port 51976 ssh2 Jun 2 18:55:21 ns382633 sshd\[3298\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.123.111 user=root |
2020-06-03 02:09:54 |
| 222.186.175.167 | attackspam | Jun 2 20:12:00 abendstille sshd\[11999\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.167 user=root Jun 2 20:12:03 abendstille sshd\[11999\]: Failed password for root from 222.186.175.167 port 56274 ssh2 Jun 2 20:12:05 abendstille sshd\[12145\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.167 user=root Jun 2 20:12:06 abendstille sshd\[11999\]: Failed password for root from 222.186.175.167 port 56274 ssh2 Jun 2 20:12:08 abendstille sshd\[12145\]: Failed password for root from 222.186.175.167 port 53616 ssh2 ... |
2020-06-03 02:19:36 |
| 36.65.59.236 | attackspam | port scan and connect, tcp 23 (telnet) |
2020-06-03 02:06:03 |
| 62.148.137.91 | attackspambots | Unauthorized connection attempt from IP address 62.148.137.91 on Port 445(SMB) |
2020-06-03 02:24:42 |
| 106.13.57.178 | attackspambots | Brute-Force,SSH |
2020-06-03 02:20:15 |
| 177.104.126.50 | attackspam | Unauthorized connection attempt detected from IP address 177.104.126.50 to port 445 |
2020-06-03 02:36:45 |
| 46.218.85.69 | attackspambots | Unauthorised connection attempt detected at AUO MAIN. System is sshd. Protected by AUO Stack Web Application Firewall (WAF) |
2020-06-03 02:11:14 |