City: unknown
Region: unknown
Country: None
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 172.70.130.216
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54122
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;172.70.130.216. IN A
;; AUTHORITY SECTION:
. 600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022021300 1800 900 604800 86400
;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 15:09:05 CST 2022
;; MSG SIZE rcvd: 107Host 216.130.70.172.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 216.130.70.172.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 60.209.112.216 | attackspam | port scan and connect, tcp 23 (telnet) |
2019-11-02 12:55:59 |
| 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 |
| 45.136.109.95 | attackspambots | 11/02/2019-05:37:49.821646 45.136.109.95 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 42 |
2019-11-02 13:26:41 |
| 123.206.90.149 | attack | Nov 2 05:55:33 localhost sshd\[29208\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.206.90.149 user=root Nov 2 05:55:35 localhost sshd\[29208\]: Failed password for root from 123.206.90.149 port 35344 ssh2 Nov 2 06:01:04 localhost sshd\[29877\]: Invalid user masran from 123.206.90.149 port 42932 Nov 2 06:01:04 localhost sshd\[29877\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.206.90.149 |
2019-11-02 13:22:40 |
| 220.130.222.156 | attackbots | Nov 2 00:53:42 firewall sshd[16195]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.130.222.156 Nov 2 00:53:42 firewall sshd[16195]: Invalid user digi-user from 220.130.222.156 Nov 2 00:53:44 firewall sshd[16195]: Failed password for invalid user digi-user from 220.130.222.156 port 52652 ssh2 ... |
2019-11-02 13:23:57 |
| 201.68.178.217 | attack | Automatic report - Port Scan Attack |
2019-11-02 12:58:46 |
| 106.13.150.163 | attackspambots | Nov 1 18:32:03 web1 sshd\[21399\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.150.163 user=root Nov 1 18:32:05 web1 sshd\[21399\]: Failed password for root from 106.13.150.163 port 47364 ssh2 Nov 1 18:36:50 web1 sshd\[21849\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.150.163 user=root Nov 1 18:36:53 web1 sshd\[21849\]: Failed password for root from 106.13.150.163 port 54828 ssh2 Nov 1 18:41:54 web1 sshd\[22365\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.150.163 user=root |
2019-11-02 13:03:16 |
| 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 |
| 191.252.195.225 | attackspambots | Nov 1 18:45:32 sachi sshd\[32675\]: Invalid user a from 191.252.195.225 Nov 1 18:45:32 sachi sshd\[32675\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=vps8811.publiccloud.com.br Nov 1 18:45:34 sachi sshd\[32675\]: Failed password for invalid user a from 191.252.195.225 port 37970 ssh2 Nov 1 18:50:20 sachi sshd\[617\]: Invalid user 123456 from 191.252.195.225 Nov 1 18:50:20 sachi sshd\[617\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=vps8811.publiccloud.com.br |
2019-11-02 13:06:02 |
| 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 |
| 92.53.90.179 | attackspam | Port scan on 6 port(s): 5607 5769 5916 5950 6270 6371 |
2019-11-02 13:17:56 |
| 187.162.51.63 | attack | Nov 1 19:14:14 auw2 sshd\[29947\]: Invalid user bamboo from 187.162.51.63 Nov 1 19:14:14 auw2 sshd\[29947\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187-162-51-63.static.axtel.net Nov 1 19:14:16 auw2 sshd\[29947\]: Failed password for invalid user bamboo from 187.162.51.63 port 55408 ssh2 Nov 1 19:18:26 auw2 sshd\[30305\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187-162-51-63.static.axtel.net user=root Nov 1 19:18:29 auw2 sshd\[30305\]: Failed password for root from 187.162.51.63 port 46409 ssh2 |
2019-11-02 13:26:11 |
| 77.45.213.127 | attack | [Sat Nov 02 01:41:39.302455 2019] [:error] [pid 48247] [client 77.45.213.127:58491] script '/var/www/www.periodicos.unifra.br/wp-login.php' not found or unable to stat, referer: https://www.google.com/ [Sat Nov 02 01:42:33.049600 2019] [:error] [pid 48247] [client 77.45.213.127:60183] script '/var/www/www.periodicos.unifra.br/wp-login.php' not found or unable to stat, referer: https://www.google.com/ [Sat Nov 02 01:46:58.093101 2019] [:error] [pid 45481] [client 77.45.213.127:52461] script '/var/www/www.periodicos.unifra.br/wp-login.php' not found or unable to stat, referer: https://www.google.com/ ... |
2019-11-02 13:11:28 |
| 206.189.30.229 | attack | Nov 2 06:07:31 sd-53420 sshd\[23085\]: User root from 206.189.30.229 not allowed because none of user's groups are listed in AllowGroups Nov 2 06:07:31 sd-53420 sshd\[23085\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.30.229 user=root Nov 2 06:07:33 sd-53420 sshd\[23085\]: Failed password for invalid user root from 206.189.30.229 port 51504 ssh2 Nov 2 06:10:56 sd-53420 sshd\[23384\]: User root from 206.189.30.229 not allowed because none of user's groups are listed in AllowGroups Nov 2 06:10:56 sd-53420 sshd\[23384\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.30.229 user=root ... |
2019-11-02 13:12:21 |
| 142.44.251.207 | attackspambots | Lines containing failures of 142.44.251.207 Nov 1 21:08:54 nextcloud sshd[626]: Invalid user indiana from 142.44.251.207 port 48331 Nov 1 21:08:54 nextcloud sshd[626]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.44.251.207 Nov 1 21:08:56 nextcloud sshd[626]: Failed password for invalid user indiana from 142.44.251.207 port 48331 ssh2 Nov 1 21:08:56 nextcloud sshd[626]: Received disconnect from 142.44.251.207 port 48331:11: Bye Bye [preauth] Nov 1 21:08:56 nextcloud sshd[626]: Disconnected from invalid user indiana 142.44.251.207 port 48331 [preauth] Nov 1 21:21:06 nextcloud sshd[5120]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.44.251.207 user=r.r Nov 1 21:21:08 nextcloud sshd[5120]: Failed password for r.r from 142.44.251.207 port 35391 ssh2 Nov 1 21:21:08 nextcloud sshd[5120]: Received disconnect from 142.44.251.207 port 35391:11: Bye Bye [preauth] Nov 1 21:21:08 ........ ------------------------------ |
2019-11-02 13:49:18 |