城市(city): unknown
省份(region): unknown
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.21.8.241
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12619
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.21.8.241. IN A
;; AUTHORITY SECTION:
. 598 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022021701 1800 900 604800 86400
;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 03:00:06 CST 2022
;; MSG SIZE rcvd: 105
Host 241.8.21.104.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 241.8.21.104.in-addr.arpa: NXDOMAIN
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 185.216.140.43 | attack | firewall-block, port(s): 50026/tcp, 50039/tcp, 50044/tcp, 50069/tcp, 50092/tcp |
2020-10-03 07:13:05 |
| 122.51.248.76 | attackspambots | Oct 3 00:46:04 DAAP sshd[4579]: Invalid user yhlee from 122.51.248.76 port 58192 Oct 3 00:46:04 DAAP sshd[4579]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.248.76 Oct 3 00:46:04 DAAP sshd[4579]: Invalid user yhlee from 122.51.248.76 port 58192 Oct 3 00:46:06 DAAP sshd[4579]: Failed password for invalid user yhlee from 122.51.248.76 port 58192 ssh2 Oct 3 00:49:28 DAAP sshd[4592]: Invalid user cs from 122.51.248.76 port 53470 ... |
2020-10-03 06:55:10 |
| 41.207.7.240 | attackbotsspam | Lines containing failures of 41.207.7.240 Oct 2 22:24:45 new sshd[31337]: Did not receive identification string from 41.207.7.240 port 57604 Oct 2 22:24:45 new sshd[31338]: Did not receive identification string from 41.207.7.240 port 57607 Oct 2 22:24:48 new sshd[31341]: Did not receive identification string from 41.207.7.240 port 57651 Oct 2 22:24:48 new sshd[31339]: Invalid user dircreate from 41.207.7.240 port 57884 Oct 2 22:24:48 new sshd[31339]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.207.7.240 Oct 2 22:24:50 new sshd[31339]: Failed password for invalid user dircreate from 41.207.7.240 port 57884 ssh2 Oct 2 22:24:50 new sshd[31343]: Invalid user dircreate from 41.207.7.240 port 57893 Oct 2 22:24:50 new sshd[31343]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.207.7.240 Oct 2 22:24:50 new sshd[31339]: Connection closed by invalid user dircreate 41.207.7.240 port ........ ------------------------------ |
2020-10-03 06:49:34 |
| 52.191.166.171 | attackbotsspam | Oct 2 21:41:35 Ubuntu-1404-trusty-64-minimal sshd\[15513\]: Invalid user ftpuser1 from 52.191.166.171 Oct 2 21:41:35 Ubuntu-1404-trusty-64-minimal sshd\[15513\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.191.166.171 Oct 2 21:41:38 Ubuntu-1404-trusty-64-minimal sshd\[15513\]: Failed password for invalid user ftpuser1 from 52.191.166.171 port 36892 ssh2 Oct 2 22:41:04 Ubuntu-1404-trusty-64-minimal sshd\[619\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.191.166.171 user=git Oct 2 22:41:06 Ubuntu-1404-trusty-64-minimal sshd\[619\]: Failed password for git from 52.191.166.171 port 60674 ssh2 |
2020-10-03 07:20:35 |
| 191.23.113.164 | attackbotsspam | Oct 2 22:34:06 mx01 sshd[15750]: reveeclipse mapping checking getaddrinfo for 191-23-113-164.user.vivozap.com.br [191.23.113.164] failed - POSSIBLE BREAK-IN ATTEMPT! Oct 2 22:34:06 mx01 sshd[15750]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=191.23.113.164 user=r.r Oct 2 22:34:08 mx01 sshd[15750]: Failed password for r.r from 191.23.113.164 port 53720 ssh2 Oct 2 22:34:08 mx01 sshd[15750]: Received disconnect from 191.23.113.164: 11: Bye Bye [preauth] Oct 2 22:34:10 mx01 sshd[15754]: reveeclipse mapping checking getaddrinfo for 191-23-113-164.user.vivozap.com.br [191.23.113.164] failed - POSSIBLE BREAK-IN ATTEMPT! Oct 2 22:34:11 mx01 sshd[15754]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=191.23.113.164 user=r.r Oct 2 22:34:12 mx01 sshd[15754]: Failed password for r.r from 191.23.113.164 port 53804 ssh2 Oct 2 22:34:12 mx01 sshd[15754]: Received disconnect from 191.23.113.1........ ------------------------------- |
2020-10-03 07:17:37 |
| 89.233.112.6 | attackspambots | port scan and connect, tcp 23 (telnet) |
2020-10-03 06:55:38 |
| 129.28.187.169 | attackbots | Time: Fri Oct 2 22:48:02 2020 +0200 IP: 129.28.187.169 (CN/China/-) Failures: 5 (sshd) Interval: 3600 seconds Blocked: Permanent Block [LF_SSHD] Log entries: Oct 2 22:39:37 3-1 sshd[17808]: Invalid user testbed from 129.28.187.169 port 56400 Oct 2 22:39:39 3-1 sshd[17808]: Failed password for invalid user testbed from 129.28.187.169 port 56400 ssh2 Oct 2 22:46:55 3-1 sshd[18148]: Invalid user test from 129.28.187.169 port 35896 Oct 2 22:46:56 3-1 sshd[18148]: Failed password for invalid user test from 129.28.187.169 port 35896 ssh2 Oct 2 22:48:00 3-1 sshd[18183]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.28.187.169 user=root |
2020-10-03 07:13:36 |
| 170.0.160.165 | attackbots | Oct 2 16:27:05 cumulus sshd[22622]: Did not receive identification string from 170.0.160.165 port 56894 Oct 2 16:27:05 cumulus sshd[22624]: Did not receive identification string from 170.0.160.165 port 56901 Oct 2 16:27:05 cumulus sshd[22623]: Did not receive identification string from 170.0.160.165 port 56900 Oct 2 16:27:06 cumulus sshd[22625]: Did not receive identification string from 170.0.160.165 port 57113 Oct 2 16:27:06 cumulus sshd[22626]: Did not receive identification string from 170.0.160.165 port 57110 Oct 2 16:27:06 cumulus sshd[22627]: Did not receive identification string from 170.0.160.165 port 57122 Oct 2 16:27:06 cumulus sshd[22628]: Did not receive identification string from 170.0.160.165 port 57151 Oct 2 16:27:08 cumulus sshd[22631]: Invalid user guest from 170.0.160.165 port 57170 Oct 2 16:27:08 cumulus sshd[22634]: Invalid user guest from 170.0.160.165 port 57173 Oct 2 16:27:08 cumulus sshd[22632]: Invalid user guest from 170.0.160.165 po........ ------------------------------- |
2020-10-03 06:57:56 |
| 14.200.208.244 | attackbots | SSH Invalid Login |
2020-10-03 07:10:31 |
| 222.186.42.57 | attackspam | Oct 2 19:47:07 shivevps sshd[10678]: Failed password for root from 222.186.42.57 port 34526 ssh2 Oct 2 19:47:13 shivevps sshd[10680]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.57 user=root Oct 2 19:47:15 shivevps sshd[10680]: Failed password for root from 222.186.42.57 port 64609 ssh2 ... |
2020-10-03 06:57:12 |
| 190.167.244.87 | attack | Lines containing failures of 190.167.244.87 Oct 2 22:27:15 shared04 sshd[2191]: Did not receive identification string from 190.167.244.87 port 3192 Oct 2 22:27:17 shared04 sshd[2195]: Invalid user user1 from 190.167.244.87 port 3994 Oct 2 22:27:17 shared04 sshd[2195]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.167.244.87 Oct 2 22:27:19 shared04 sshd[2195]: Failed password for invalid user user1 from 190.167.244.87 port 3994 ssh2 Oct 2 22:27:20 shared04 sshd[2195]: Connection closed by invalid user user1 190.167.244.87 port 3994 [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=190.167.244.87 |
2020-10-03 06:59:52 |
| 129.211.73.2 | attackbots | 3x Failed Password |
2020-10-03 07:09:32 |
| 1.255.48.197 | attack | (From annabelle@merchantpay.top) I have a quick question about working with your business. Like most business owners you just want to survive through to 2021. In order for that to happen you need to save every dollar possible right? This is an honest question, would you continue with the high credit card processing fees if there was another way? New laws are on your side. Test this newly released card processing model this October - just send a phone number and we'll call. $24.99/mo Flat Fee Credit Card Processing (Unlimited) 1) As a small business owner accepting credit/debit, recently passed State Laws are on your side. - Were you aware? New state regulations now in effect, the law was successfully passed in 46 states - effective since August 2019. Since that date you shouldn't be paying above 0.75% Credit Card Processing Fees. 2) You're legally able to demand this new option. Bottom Line: Your processor isn't telling you everything. Why are they hiding the lower fee options? We repre |
2020-10-03 06:58:51 |
| 35.204.93.160 | attack | RU spamvertising/fraud - From: Your Nail Fungus |
2020-10-03 07:08:17 |
| 122.51.252.45 | attack | SSH Invalid Login |
2020-10-03 07:21:41 |