城市(city): unknown
省份(region): unknown
国家(country): Canada
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 66.183.53.142
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 29922
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;66.183.53.142. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020901 1800 900 604800 86400
;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 09:18:40 CST 2025
;; MSG SIZE rcvd: 106142.53.183.66.in-addr.arpa domain name pointer d66-183-53-142.bchsia.telus.net.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
142.53.183.66.in-addr.arpa name = d66-183-53-142.bchsia.telus.net.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 129.158.73.144 | attackspam | Nov 2 05:56:14 fr01 sshd[2150]: Invalid user helena from 129.158.73.144 Nov 2 05:56:14 fr01 sshd[2150]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.158.73.144 Nov 2 05:56:14 fr01 sshd[2150]: Invalid user helena from 129.158.73.144 Nov 2 05:56:16 fr01 sshd[2150]: Failed password for invalid user helena from 129.158.73.144 port 56451 ssh2 ... |
2019-11-02 13:13:22 |
| 206.189.129.38 | attackspam | Nov 1 00:49:36 xm3 sshd[10442]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.129.38 user=r.r Nov 1 00:49:37 xm3 sshd[10442]: Failed password for r.r from 206.189.129.38 port 38548 ssh2 Nov 1 00:49:38 xm3 sshd[10442]: Received disconnect from 206.189.129.38: 11: Bye Bye [preauth] Nov 1 01:04:43 xm3 sshd[13655]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.129.38 user=r.r Nov 1 01:04:45 xm3 sshd[13655]: Failed password for r.r from 206.189.129.38 port 46286 ssh2 Nov 1 01:04:45 xm3 sshd[13655]: Received disconnect from 206.189.129.38: 11: Bye Bye [preauth] Nov 1 01:09:07 xm3 sshd[23124]: Failed password for invalid user user1 from 206.189.129.38 port 59326 ssh2 Nov 1 01:09:07 xm3 sshd[23124]: Received disconnect from 206.189.129.38: 11: Bye Bye [preauth] Nov 1 01:13:20 xm3 sshd[32741]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ru........ ------------------------------- |
2019-11-02 13:27:50 |
| 77.247.108.119 | attackspam | 11/02/2019-00:54:28.804421 77.247.108.119 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 74 |
2019-11-02 13:26:27 |
| 222.186.42.4 | attack | Nov 2 08:25:45 server sshd\[17229\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.4 user=root Nov 2 08:25:47 server sshd\[17229\]: Failed password for root from 222.186.42.4 port 13154 ssh2 Nov 2 08:25:47 server sshd\[17242\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.4 user=root Nov 2 08:25:48 server sshd\[17246\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.4 user=root Nov 2 08:25:49 server sshd\[17242\]: Failed password for root from 222.186.42.4 port 42758 ssh2 ... |
2019-11-02 13:30:03 |
| 45.61.172.60 | attackspambots | (From eric@talkwithcustomer.com) Hello abcchiropractic.net, People ask, “why does TalkWithCustomer work so well?” It’s simple. TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time. - NOT one week, two weeks, three weeks after they’ve checked out your website abcchiropractic.net. - NOT with a form letter style email that looks like it was written by a bot. - NOT with a robocall that could come at any time out of the blue. TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU. They kick off the conversation. They take that first step. They ask to hear from you regarding what you have to offer and how it can make their life better. And it happens almost immediately. In real time. While they’re still looking over your website abcchiropractic.net, trying to make up their mind whether you are right for them. When you connect with them at that very moment it’s the ultimate in Perfect Timing – as one famo |
2019-11-02 13:14:51 |
| 177.69.118.197 | attack | $f2bV_matches |
2019-11-02 13:05:32 |
| 122.141.177.112 | attackbotsspam | Tried sshing with brute force. |
2019-11-02 13:08:17 |
| 88.247.110.88 | attack | Nov 2 00:38:58 TORMINT sshd\[17632\]: Invalid user taras15 from 88.247.110.88 Nov 2 00:38:58 TORMINT sshd\[17632\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.247.110.88 Nov 2 00:39:00 TORMINT sshd\[17632\]: Failed password for invalid user taras15 from 88.247.110.88 port 37770 ssh2 ... |
2019-11-02 13:07:31 |
| 107.158.9.250 | attackbotsspam | (From eric@talkwithcustomer.com) Hello abcchiropractic.net, People ask, “why does TalkWithCustomer work so well?” It’s simple. TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time. - NOT one week, two weeks, three weeks after they’ve checked out your website abcchiropractic.net. - NOT with a form letter style email that looks like it was written by a bot. - NOT with a robocall that could come at any time out of the blue. TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU. They kick off the conversation. They take that first step. They ask to hear from you regarding what you have to offer and how it can make their life better. And it happens almost immediately. In real time. While they’re still looking over your website abcchiropractic.net, trying to make up their mind whether you are right for them. When you connect with them at that very moment it’s the ultimate in Perfect Timing – as one famo |
2019-11-02 13:13:42 |
| 201.68.178.217 | attack | Automatic report - Port Scan Attack |
2019-11-02 12:58:46 |
| 182.61.162.54 | attack | Nov 2 07:25:32 server sshd\[21248\]: User root from 182.61.162.54 not allowed because listed in DenyUsers Nov 2 07:25:32 server sshd\[21248\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.162.54 user=root Nov 2 07:25:34 server sshd\[21248\]: Failed password for invalid user root from 182.61.162.54 port 50272 ssh2 Nov 2 07:30:16 server sshd\[23828\]: User root from 182.61.162.54 not allowed because listed in DenyUsers Nov 2 07:30:16 server sshd\[23828\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.162.54 user=root |
2019-11-02 13:46:41 |
| 52.187.17.107 | attackspambots | Nov 1 17:49:06 auw2 sshd\[22432\]: Invalid user cqcq from 52.187.17.107 Nov 1 17:49:06 auw2 sshd\[22432\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.187.17.107 Nov 1 17:49:08 auw2 sshd\[22432\]: Failed password for invalid user cqcq from 52.187.17.107 port 11319 ssh2 Nov 1 17:53:56 auw2 sshd\[22848\]: Invalid user com from 52.187.17.107 Nov 1 17:53:56 auw2 sshd\[22848\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.187.17.107 |
2019-11-02 13:16:05 |
| 185.36.219.24 | attackspambots | slow and persistent scanner |
2019-11-02 13:09:59 |
| 177.66.208.235 | attackbotsspam | Automatic report - Port Scan Attack |
2019-11-02 13:02:57 |
| 37.187.46.74 | attack | $f2bV_matches |
2019-11-02 13:20:44 |