城市(city): unknown
省份(region): unknown
国家(country): Multicast Address
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 227.66.12.118
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 63573
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;227.66.12.118. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020601 1800 900 604800 86400
;; Query time: 150 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 07 05:02:06 CST 2025
;; MSG SIZE rcvd: 106Host 118.12.66.227.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 118.12.66.227.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 89.33.192.51 | attackspambots | [N3.H3.VM3] Port Scanner Detected Blocked by UFW |
2020-10-10 22:34:00 |
| 201.193.198.70 | attack | 445/tcp 445/tcp [2020-08-30/10-10]2pkt |
2020-10-10 22:14:16 |
| 81.70.20.28 | attackspam | $f2bV_matches |
2020-10-10 22:24:57 |
| 23.108.4.77 | attack | (From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across lifeforcedoc.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.talk |
2020-10-10 22:50:07 |
| 192.35.168.230 | attackspam | port |
2020-10-10 22:28:43 |
| 46.36.27.120 | attack | $f2bV_matches |
2020-10-10 22:26:36 |
| 51.79.55.141 | attack | Automatic report - Banned IP Access |
2020-10-10 22:42:39 |
| 94.102.54.221 | attack | Sep 11 22:18:34 *hidden* postfix/postscreen[38933]: DNSBL rank 4 for [94.102.54.221]:49264 |
2020-10-10 22:22:21 |
| 46.245.222.203 | attackspambots | Oct 10 10:19:39 ws22vmsma01 sshd[35052]: Failed password for root from 46.245.222.203 port 38911 ssh2 ... |
2020-10-10 22:45:00 |
| 114.242.25.132 | attackspambots | Oct 10 12:14:54 root sshd[13427]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.242.25.132 user=root Oct 10 12:14:57 root sshd[13427]: Failed password for root from 114.242.25.132 port 54312 ssh2 ... |
2020-10-10 22:51:42 |
| 221.202.197.114 | attackbotsspam | Port probing on unauthorized port 23 |
2020-10-10 22:16:29 |
| 106.55.242.70 | attackbotsspam | Oct 10 14:23:22 con01 sshd[2933001]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.55.242.70 user=root Oct 10 14:23:23 con01 sshd[2933001]: Failed password for root from 106.55.242.70 port 33324 ssh2 Oct 10 14:25:33 con01 sshd[2936886]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.55.242.70 user=irc Oct 10 14:25:35 con01 sshd[2936886]: Failed password for irc from 106.55.242.70 port 60146 ssh2 Oct 10 14:27:43 con01 sshd[2940165]: Invalid user arun from 106.55.242.70 port 58740 ... |
2020-10-10 22:19:19 |
| 61.177.172.61 | attack | 2020-10-10T14:32:45.557979shield sshd\[5967\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.177.172.61 user=root 2020-10-10T14:32:47.237973shield sshd\[5967\]: Failed password for root from 61.177.172.61 port 37831 ssh2 2020-10-10T14:32:50.592985shield sshd\[5967\]: Failed password for root from 61.177.172.61 port 37831 ssh2 2020-10-10T14:32:54.028903shield sshd\[5967\]: Failed password for root from 61.177.172.61 port 37831 ssh2 2020-10-10T14:32:57.014500shield sshd\[5967\]: Failed password for root from 61.177.172.61 port 37831 ssh2 |
2020-10-10 22:40:43 |
| 42.194.198.187 | attackbotsspam | Oct 10 15:16:47 master sshd[20644]: Failed password for root from 42.194.198.187 port 35186 ssh2 Oct 10 15:24:10 master sshd[20658]: Failed password for root from 42.194.198.187 port 49210 ssh2 Oct 10 15:29:36 master sshd[20667]: Failed password for root from 42.194.198.187 port 48024 ssh2 Oct 10 15:34:50 master sshd[20690]: Failed password for root from 42.194.198.187 port 46806 ssh2 Oct 10 15:40:17 master sshd[20698]: Failed password for root from 42.194.198.187 port 45592 ssh2 Oct 10 15:45:29 master sshd[20720]: Failed password for root from 42.194.198.187 port 44368 ssh2 Oct 10 15:50:39 master sshd[20732]: Failed password for invalid user serverpilot from 42.194.198.187 port 43190 ssh2 Oct 10 15:55:46 master sshd[20741]: Failed password for root from 42.194.198.187 port 41964 ssh2 Oct 10 16:00:57 master sshd[20774]: Failed password for invalid user issue from 42.194.198.187 port 40770 ssh2 Oct 10 16:06:13 master sshd[20792]: Failed password for invalid user testftp1 from 42.194.198.187 port 39590 ssh2 |
2020-10-10 22:42:58 |
| 141.98.9.162 | attackbots | SSH Remote Login Attempt Banned |
2020-10-10 22:43:59 |