城市(city): unknown
省份(region): unknown
国家(country): Hong Kong
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 118.193.38.145
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13424
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;118.193.38.145. IN A
;; AUTHORITY SECTION:
. 474 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022030800 1800 900 604800 86400
;; Query time: 65 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 08 17:14:58 CST 2022
;; MSG SIZE rcvd: 107
Host 145.38.193.118.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 145.38.193.118.in-addr.arpa: NXDOMAIN
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 61.133.122.19 | attackspam | (sshd) Failed SSH login from 61.133.122.19 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep 4 15:13:20 server sshd[23675]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.133.122.19 user=root Sep 4 15:13:22 server sshd[23675]: Failed password for root from 61.133.122.19 port 57374 ssh2 Sep 4 15:33:36 server sshd[30000]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.133.122.19 user=root Sep 4 15:33:38 server sshd[30000]: Failed password for root from 61.133.122.19 port 39716 ssh2 Sep 4 15:37:30 server sshd[31339]: Invalid user tang from 61.133.122.19 port 62438 |
2020-09-05 07:46:54 |
| 91.229.112.12 | attackbots | Auto Detect Rule! proto TCP (SYN), 91.229.112.12:52222->gjan.info:21, len 40 |
2020-09-05 07:46:15 |
| 141.98.10.214 | attackspambots | 2020-09-04T23:19:52.093584shield sshd\[22082\]: Invalid user admin from 141.98.10.214 port 43725 2020-09-04T23:19:52.102364shield sshd\[22082\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=141.98.10.214 2020-09-04T23:19:53.537466shield sshd\[22082\]: Failed password for invalid user admin from 141.98.10.214 port 43725 ssh2 2020-09-04T23:20:33.319213shield sshd\[22224\]: Invalid user admin from 141.98.10.214 port 41057 2020-09-04T23:20:33.328245shield sshd\[22224\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=141.98.10.214 |
2020-09-05 07:31:47 |
| 112.85.42.173 | attackbots | Sep 5 00:40:07 sd-69548 sshd[755217]: Unable to negotiate with 112.85.42.173 port 23352: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1 [preauth] Sep 5 01:17:12 sd-69548 sshd[757731]: Unable to negotiate with 112.85.42.173 port 11297: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1 [preauth] ... |
2020-09-05 07:20:41 |
| 143.202.209.47 | attackbots | fail2ban -- 143.202.209.47 ... |
2020-09-05 07:11:43 |
| 194.26.25.97 | attack | Multiport scan : 43 ports scanned 58 221 292 322 442 565 710 939 1876 1891 1901 2025 2552 2795 4894 5435 5671 6336 8990 9222 9351 9456 9585 9769 12124 13022 13135 13226 14145 14444 14725 18586 19495 19756 20726 21216 21439 22021 22227 24445 26914 31112 32122 |
2020-09-05 07:12:45 |
| 191.233.199.68 | attackbots | " " |
2020-09-05 07:28:23 |
| 54.39.133.91 | attack | 2020-09-05T02:59:58.124541paragon sshd[134037]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.39.133.91 2020-09-05T02:59:58.120819paragon sshd[134037]: Invalid user vitor from 54.39.133.91 port 54350 2020-09-05T02:59:59.977600paragon sshd[134037]: Failed password for invalid user vitor from 54.39.133.91 port 54350 ssh2 2020-09-05T03:02:14.344829paragon sshd[134076]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.39.133.91 user=root 2020-09-05T03:02:16.537739paragon sshd[134076]: Failed password for root from 54.39.133.91 port 39312 ssh2 ... |
2020-09-05 07:13:33 |
| 207.46.13.42 | attackspam | Automatic report - Banned IP Access |
2020-09-05 07:40:59 |
| 192.241.200.105 | attack | firewall-block, port(s): 2323/tcp |
2020-09-05 07:23:05 |
| 139.99.203.12 | attackspambots | (sshd) Failed SSH login from 139.99.203.12 (AU/Australia/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep 4 15:51:41 server4 sshd[23678]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.99.203.12 user=root Sep 4 15:51:43 server4 sshd[23678]: Failed password for root from 139.99.203.12 port 51122 ssh2 Sep 4 15:58:58 server4 sshd[28369]: Invalid user bitnami from 139.99.203.12 Sep 4 15:58:58 server4 sshd[28369]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.99.203.12 Sep 4 15:59:00 server4 sshd[28369]: Failed password for invalid user bitnami from 139.99.203.12 port 47564 ssh2 |
2020-09-05 07:23:26 |
| 205.185.127.217 | attack | 2020-09-05T01:22:22+0200 Failed SSH Authentication/Brute Force Attack. (Server 5) |
2020-09-05 07:30:12 |
| 66.249.64.135 | attack | The IP has triggered Cloudflare WAF. CF-Ray: 5cd1f90fd8a409b0 | WAF_Rule_ID: 1bd9f7863d3d4d8faf68c16295216fb5 | WAF_Kind: firewall | CF_Action: allow | Country: US | CF_IPClass: searchEngine | Protocol: HTTP/1.1 | Method: GET | Host: www.wevg.org | User-Agent: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html) | CF_DC: IAD. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB). |
2020-09-05 07:27:06 |
| 178.128.243.225 | attackspam | Sep 4 19:11:18 vps46666688 sshd[7180]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.243.225 Sep 4 19:11:21 vps46666688 sshd[7180]: Failed password for invalid user hduser from 178.128.243.225 port 36052 ssh2 ... |
2020-09-05 07:11:20 |
| 172.245.58.78 | attack | (From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across drdoor.com 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://www.talkwithwe |
2020-09-05 07:20:02 |