城市(city): unknown
省份(region): unknown
国家(country): United States of America (the)
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 52.91.213.113
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9156
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;52.91.213.113. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012600 1800 900 604800 86400
;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 27 01:30:46 CST 2025
;; MSG SIZE rcvd: 106113.213.91.52.in-addr.arpa domain name pointer ec2-52-91-213-113.compute-1.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
113.213.91.52.in-addr.arpa name = ec2-52-91-213-113.compute-1.amazonaws.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 141.98.80.67 | attackspambots | Aug 8 06:29:40 relay postfix/smtpd\[2976\]: warning: unknown\[141.98.80.67\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Aug 8 06:29:59 relay postfix/smtpd\[631\]: warning: unknown\[141.98.80.67\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Aug 8 06:37:49 relay postfix/smtpd\[2969\]: warning: unknown\[141.98.80.67\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Aug 8 06:38:02 relay postfix/smtpd\[2971\]: warning: unknown\[141.98.80.67\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Aug 8 06:44:56 relay postfix/smtpd\[2970\]: warning: unknown\[141.98.80.67\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-08-08 17:49:06 |
| 23.95.97.228 | attackspam | (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:41:04 |
| 178.32.163.249 | attack | Aug 8 06:50:53 ns37 sshd[3128]: Failed password for root from 178.32.163.249 port 32770 ssh2 Aug 8 06:50:53 ns37 sshd[3128]: Failed password for root from 178.32.163.249 port 32770 ssh2 |
2020-08-08 18:00:30 |
| 14.229.146.0 | attackspam | SMB Server BruteForce Attack |
2020-08-08 18:11:17 |
| 120.203.160.18 | attack | Aug 8 11:33:30 lukav-desktop sshd\[13768\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.203.160.18 user=root Aug 8 11:33:32 lukav-desktop sshd\[13768\]: Failed password for root from 120.203.160.18 port 55125 ssh2 Aug 8 11:38:31 lukav-desktop sshd\[22602\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.203.160.18 user=root Aug 8 11:38:33 lukav-desktop sshd\[22602\]: Failed password for root from 120.203.160.18 port 28474 ssh2 Aug 8 11:43:26 lukav-desktop sshd\[31336\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.203.160.18 user=root |
2020-08-08 18:10:29 |
| 193.91.103.106 | attack | Unauthorized connection attempt detected from IP address 193.91.103.106 to port 22 |
2020-08-08 17:48:31 |
| 103.219.112.48 | attackbotsspam | Aug 8 10:30:36 kh-dev-server sshd[3207]: Failed password for root from 103.219.112.48 port 56396 ssh2 ... |
2020-08-08 17:40:37 |
| 222.186.173.226 | attackspam | [MK-VM6] SSH login failed |
2020-08-08 17:55:21 |
| 175.139.3.41 | attack | Bruteforce detected by fail2ban |
2020-08-08 17:56:58 |
| 51.68.228.127 | attackbotsspam | Connection to SSH Honeypot - Detected by HoneypotDB |
2020-08-08 17:56:03 |
| 93.158.66.41 | attackbots | Automatic report - Banned IP Access |
2020-08-08 18:05:25 |
| 112.85.42.104 | attack | Aug 8 05:26:17 plusreed sshd[19471]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.104 user=root Aug 8 05:26:19 plusreed sshd[19471]: Failed password for root from 112.85.42.104 port 54750 ssh2 ... |
2020-08-08 17:35:18 |
| 49.232.43.192 | attack | Aug 8 11:41:53 abendstille sshd\[5755\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.43.192 user=root Aug 8 11:41:55 abendstille sshd\[5755\]: Failed password for root from 49.232.43.192 port 60498 ssh2 Aug 8 11:45:47 abendstille sshd\[9641\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.43.192 user=root Aug 8 11:45:49 abendstille sshd\[9641\]: Failed password for root from 49.232.43.192 port 47352 ssh2 Aug 8 11:49:41 abendstille sshd\[13256\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.43.192 user=root ... |
2020-08-08 18:03:00 |
| 193.32.161.145 | attackbots | 08/08/2020-03:49:36.008537 193.32.161.145 Protocol: 6 ET SCAN NMAP -sS window 1024 |
2020-08-08 17:59:56 |
| 34.91.145.211 | attackspam | 34.91.145.211 - - \[08/Aug/2020:11:13:56 +0200\] "POST /wp-login.php HTTP/1.1" 200 9954 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" 34.91.145.211 - - \[08/Aug/2020:11:13:56 +0200\] "POST /wp-login.php HTTP/1.1" 200 9789 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0" ... |
2020-08-08 17:38:52 |