城市(city): unknown
省份(region): unknown
国家(country): Korea (the Republic of)
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 54.116.155.46
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 7487
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;54.116.155.46. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020600 1800 900 604800 86400
;; Query time: 194 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 07 00:29:07 CST 2025
;; MSG SIZE rcvd: 10646.155.116.54.in-addr.arpa domain name pointer ec2-54-116-155-46.ap-northeast-2.compute.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
46.155.116.54.in-addr.arpa name = ec2-54-116-155-46.ap-northeast-2.compute.amazonaws.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 212.227.17.22 | attackspam | Opportunities to relax more often! |
2020-08-10 07:46:07 |
| 104.227.121.166 | attackbots | (From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across middletonchiropractic.net a few minutes ago. Looks great… but now what? By that I mean, when someone like me finds your website – either through Search or just bouncing around – what happens next? Do you get a lot of leads from your site, or at least enough to make you happy? Honestly, most business websites fall a bit short when it comes to generating paying customers. Studies show that 70% of a site’s visitors disappear and are gone forever after just a moment. Here’s an idea… How about making it really EASY for every visitor who shows up to get a personal phone call you as soon as they hit your site… You can – 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. It signals you the moment they let you know they’re interested – so that you can talk to that lead while they’re literally looking over your site. CLICK HERE http:/ |
2020-08-10 07:39:47 |
| 140.143.248.32 | attackbots | Aug 9 22:13:29 vserver sshd\[3074\]: Failed password for root from 140.143.248.32 port 49392 ssh2Aug 9 22:18:30 vserver sshd\[3119\]: Failed password for root from 140.143.248.32 port 52094 ssh2Aug 9 22:20:40 vserver sshd\[3157\]: Failed password for root from 140.143.248.32 port 44970 ssh2Aug 9 22:22:44 vserver sshd\[3204\]: Failed password for root from 140.143.248.32 port 37850 ssh2 ... |
2020-08-10 07:43:16 |
| 42.51.40.73 | attack | Aug 9 06:03:23 UTC__SANYALnet-Labs__cac14 sshd[12608]: Connection from 42.51.40.73 port 34918 on 64.137.176.112 port 22 Aug 9 06:03:27 UTC__SANYALnet-Labs__cac14 sshd[12608]: Address 42.51.40.73 maps to idc.ly.ha, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! Aug 9 06:03:27 UTC__SANYALnet-Labs__cac14 sshd[12608]: User r.r from 42.51.40.73 not allowed because not listed in AllowUsers Aug 9 06:03:27 UTC__SANYALnet-Labs__cac14 sshd[12608]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.51.40.73 user=r.r Aug 9 06:03:29 UTC__SANYALnet-Labs__cac14 sshd[12608]: Failed password for invalid user r.r from 42.51.40.73 port 34918 ssh2 Aug 9 06:03:29 UTC__SANYALnet-Labs__cac14 sshd[12608]: Received disconnect from 42.51.40.73: 11: Bye Bye [preauth] Aug 9 06:06:16 UTC__SANYALnet-Labs__cac14 sshd[12670]: Connection from 42.51.40.73 port 56588 on 64.137.176.112 port 22 Aug 9 06:06:18 UTC__SANYALnet-Labs__cac1........ ------------------------------- |
2020-08-10 07:22:53 |
| 167.99.183.237 | attackbots | "Unauthorized connection attempt on SSHD detected" |
2020-08-10 07:32:13 |
| 89.221.212.63 | attack | Automatic report - Banned IP Access |
2020-08-10 08:00:58 |
| 194.87.138.124 | attackbotsspam |
|
2020-08-10 08:04:09 |
| 218.92.0.246 | attackbotsspam | Aug 10 01:32:03 vps639187 sshd\[7906\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.246 user=root Aug 10 01:32:06 vps639187 sshd\[7906\]: Failed password for root from 218.92.0.246 port 37995 ssh2 Aug 10 01:32:09 vps639187 sshd\[7906\]: Failed password for root from 218.92.0.246 port 37995 ssh2 ... |
2020-08-10 07:44:51 |
| 176.109.234.70 | attackspam | " " |
2020-08-10 07:34:20 |
| 194.87.138.3 | attackbots | 2020-08-09T22:39:29.932268correo.[domain] sshd[38292]: Invalid user ubnt from 194.87.138.3 port 59952 2020-08-09T22:39:32.042262correo.[domain] sshd[38292]: Failed password for invalid user ubnt from 194.87.138.3 port 59952 ssh2 2020-08-09T22:39:32.686120correo.[domain] sshd[38294]: Invalid user admin from 194.87.138.3 port 36282 ... |
2020-08-10 07:37:44 |
| 193.27.229.219 | attackbotsspam | firewall-block, port(s): 34097/tcp |
2020-08-10 07:40:04 |
| 51.68.195.146 | attack | Port scan on 2 port(s): 139 445 |
2020-08-10 07:24:13 |
| 87.251.74.24 | attackspam | [H1.VM8] Blocked by UFW |
2020-08-10 07:59:52 |
| 222.186.15.115 | attackspam | Aug 10 01:25:02 vmanager6029 sshd\[29275\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.15.115 user=root Aug 10 01:25:04 vmanager6029 sshd\[29267\]: error: PAM: Authentication failure for root from 222.186.15.115 Aug 10 01:25:05 vmanager6029 sshd\[29280\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.15.115 user=root |
2020-08-10 07:25:49 |
| 49.88.112.70 | attackspambots | SSH auth scanning - multiple failed logins |
2020-08-10 07:55:36 |