城市(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.14.53
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 14627
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.21.14.53. IN A
;; AUTHORITY SECTION:
. 470 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022021700 1800 900 604800 86400
;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 17 18:02:40 CST 2022
;; MSG SIZE rcvd: 105Host 53.14.21.104.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 53.14.21.104.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 176.113.70.60 | attack | 176.113.70.60 was recorded 7 times by 3 hosts attempting to connect to the following ports: 1900. Incident counter (4h, 24h, all-time): 7, 47, 6116 |
2020-04-22 20:17:19 |
| 36.89.67.186 | attackspambots | 2020-04-22T14:01:31.826383mail.broermann.family sshd[12401]: Invalid user cr from 36.89.67.186 port 35050 2020-04-22T14:01:31.836377mail.broermann.family sshd[12401]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.89.67.186 2020-04-22T14:01:31.826383mail.broermann.family sshd[12401]: Invalid user cr from 36.89.67.186 port 35050 2020-04-22T14:01:34.013485mail.broermann.family sshd[12401]: Failed password for invalid user cr from 36.89.67.186 port 35050 ssh2 2020-04-22T14:05:15.795732mail.broermann.family sshd[12621]: Invalid user mq from 36.89.67.186 port 34200 ... |
2020-04-22 20:13:13 |
| 191.102.156.130 | attackbots | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found millenniumchiro.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well. So here’s my question – what happens AFTER someone lands on your site? Anything? Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever. That means that all the work and effort you put into getting them to show up, goes down the tubes. Why would you want all that good work – and the great site you’ve built – go to waste? Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry. But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket? You can – thanks to revolutionary new software tha |
2020-04-22 20:42:48 |
| 111.206.198.70 | attackbotsspam | Bad bot/spoofed identity |
2020-04-22 20:21:03 |
| 114.67.91.168 | attackspam | Invalid user eb from 114.67.91.168 port 40854 |
2020-04-22 20:07:25 |
| 176.114.199.56 | attackspam | 2020-04-22T08:01:00.8598111495-001 sshd[31606]: Invalid user qd from 176.114.199.56 port 41434 2020-04-22T08:01:00.8631781495-001 sshd[31606]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.114.199.56 2020-04-22T08:01:00.8598111495-001 sshd[31606]: Invalid user qd from 176.114.199.56 port 41434 2020-04-22T08:01:02.7832631495-001 sshd[31606]: Failed password for invalid user qd from 176.114.199.56 port 41434 ssh2 2020-04-22T08:05:12.3687021495-001 sshd[31838]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.114.199.56 user=root 2020-04-22T08:05:14.2199191495-001 sshd[31838]: Failed password for root from 176.114.199.56 port 55034 ssh2 ... |
2020-04-22 20:28:28 |
| 174.138.64.163 | attackbots | Apr 22 06:13:46 server1 sshd\[19316\]: Failed password for invalid user test from 174.138.64.163 port 58164 ssh2 Apr 22 06:18:14 server1 sshd\[20597\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.64.163 user=root Apr 22 06:18:17 server1 sshd\[20597\]: Failed password for root from 174.138.64.163 port 43704 ssh2 Apr 22 06:22:47 server1 sshd\[21790\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=174.138.64.163 user=root Apr 22 06:22:49 server1 sshd\[21790\]: Failed password for root from 174.138.64.163 port 57476 ssh2 ... |
2020-04-22 20:34:24 |
| 41.207.184.182 | attackbotsspam | Apr 22 13:58:08 legacy sshd[14564]: Failed password for root from 41.207.184.182 port 35686 ssh2 Apr 22 14:05:16 legacy sshd[14661]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.207.184.182 Apr 22 14:05:19 legacy sshd[14661]: Failed password for invalid user ftpuser from 41.207.184.182 port 42746 ssh2 ... |
2020-04-22 20:09:17 |
| 68.116.41.6 | attack | no |
2020-04-22 20:36:00 |
| 42.159.228.125 | attackbots | Apr 22 14:00:17 DAAP sshd[32106]: Invalid user mz from 42.159.228.125 port 48830 Apr 22 14:00:18 DAAP sshd[32106]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.159.228.125 Apr 22 14:00:17 DAAP sshd[32106]: Invalid user mz from 42.159.228.125 port 48830 Apr 22 14:00:19 DAAP sshd[32106]: Failed password for invalid user mz from 42.159.228.125 port 48830 ssh2 Apr 22 14:05:07 DAAP sshd[32174]: Invalid user admin from 42.159.228.125 port 45247 ... |
2020-04-22 20:23:26 |
| 222.186.42.137 | attack | Apr 22 14:36:18 vmanager6029 sshd\[6885\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.137 user=root Apr 22 14:36:20 vmanager6029 sshd\[6864\]: error: PAM: Authentication failure for root from 222.186.42.137 Apr 22 14:36:21 vmanager6029 sshd\[6886\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.137 user=root |
2020-04-22 20:37:58 |
| 103.241.5.174 | attackspambots | Sending SPAM email |
2020-04-22 20:24:32 |
| 49.88.112.113 | attackbots | Apr 22 08:05:14 plusreed sshd[8364]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.113 user=root Apr 22 08:05:16 plusreed sshd[8364]: Failed password for root from 49.88.112.113 port 58210 ssh2 ... |
2020-04-22 20:12:45 |
| 59.41.119.65 | attackbots | Lines containing failures of 59.41.119.65 Apr 22 09:12:26 nextcloud sshd[10898]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.41.119.65 user=r.r Apr 22 09:12:28 nextcloud sshd[10898]: Failed password for r.r from 59.41.119.65 port 61012 ssh2 Apr 22 09:12:29 nextcloud sshd[10898]: Received disconnect from 59.41.119.65 port 61012:11: Bye Bye [preauth] Apr 22 09:12:29 nextcloud sshd[10898]: Disconnected from authenticating user r.r 59.41.119.65 port 61012 [preauth] Apr 22 09:24:13 nextcloud sshd[12627]: Invalid user test from 59.41.119.65 port 60166 Apr 22 09:24:13 nextcloud sshd[12627]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.41.119.65 Apr 22 09:24:16 nextcloud sshd[12627]: Failed password for invalid user test from 59.41.119.65 port 60166 ssh2 Apr 22 09:24:16 nextcloud sshd[12627]: Received disconnect from 59.41.119.65 port 60166:11: Bye Bye [preauth] Apr 22 09:24:16 nextclou........ ------------------------------ |
2020-04-22 20:35:38 |
| 84.247.48.25 | attack | 84.247.48.25 - - [22/Apr/2020:13:58:30 +0200] "POST /wp-login.php HTTP/1.0" 200 3132 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 84.247.48.25 - - [22/Apr/2020:14:05:05 +0200] "POST /wp-login.php HTTP/1.0" 200 2504 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" ... |
2020-04-22 20:26:52 |