City: unknown
Region: unknown
Country: United States of America (the)
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 11.139.28.134
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9938
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;11.139.28.134. IN A
;; AUTHORITY SECTION:
. 226 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2024010601 1800 900 604800 86400
;; Query time: 23 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 07 04:26:49 CST 2024
;; MSG SIZE rcvd: 106Host 134.28.139.11.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 134.28.139.11.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 111.75.149.221 | attackbotsspam | 2019-12-12 00:25:45 dovecot_login authenticator failed for (sienawx.net) [111.75.149.221]:51300 I=[192.147.25.65]:25: 535 Incorrect authentication data (set_id=nologin@lerctr.org) 2019-12-12 00:26:15 dovecot_login authenticator failed for (sienawx.net) [111.75.149.221]:52686 I=[192.147.25.65]:25: 535 Incorrect authentication data (set_id=alex@lerctr.org) 2019-12-12 00:26:40 dovecot_login authenticator failed for (sienawx.net) [111.75.149.221]:54536 I=[192.147.25.65]:25: 535 Incorrect authentication data (set_id=alex@lerctr.org) ... |
2019-12-12 18:15:55 |
| 185.176.27.254 | attackbots | 12/12/2019-04:36:51.156413 185.176.27.254 Protocol: 6 ET DROP Dshield Block Listed Source group 1 |
2019-12-12 17:39:02 |
| 139.162.123.103 | attackbotsspam | IP was detected trying to Brute-Force SSH, FTP, Web Apps, Port-Scan or Hacking. |
2019-12-12 17:59:20 |
| 177.106.151.64 | attack | Port Scan |
2019-12-12 17:49:44 |
| 172.110.30.125 | attackbots | <6 unauthorized SSH connections |
2019-12-12 18:08:42 |
| 89.133.103.216 | attack | Dec 12 04:43:54 ny01 sshd[26191]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.133.103.216 Dec 12 04:43:55 ny01 sshd[26191]: Failed password for invalid user danzig from 89.133.103.216 port 39298 ssh2 Dec 12 04:49:11 ny01 sshd[26867]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.133.103.216 |
2019-12-12 17:54:44 |
| 178.128.221.162 | attack | SSH authentication failure x 6 reported by Fail2Ban ... |
2019-12-12 17:47:29 |
| 106.12.102.143 | attackbotsspam | Dec 12 10:43:17 OPSO sshd\[30060\]: Invalid user courtadm from 106.12.102.143 port 58020 Dec 12 10:43:17 OPSO sshd\[30060\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.102.143 Dec 12 10:43:19 OPSO sshd\[30060\]: Failed password for invalid user courtadm from 106.12.102.143 port 58020 ssh2 Dec 12 10:50:21 OPSO sshd\[31633\]: Invalid user cheng from 106.12.102.143 port 39772 Dec 12 10:50:21 OPSO sshd\[31633\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.102.143 |
2019-12-12 17:56:09 |
| 51.38.125.51 | attackbotsspam | Automatic report: SSH brute force attempt |
2019-12-12 18:04:07 |
| 104.129.4.229 | attackspam | (From eric@talkwithcustomer.com) Hello knutsonchiropractic.com, 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 knutsonchiropractic.com. - 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 knutsonchiropractic.com, 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 – |
2019-12-12 18:03:23 |
| 92.118.37.70 | attack | [portscan] tcp/3389 [MS RDP] [scan/connect: 2 time(s)] *(RWIN=1024)(12121149) |
2019-12-12 18:09:16 |
| 51.68.97.191 | attack | 2019-12-12T07:51:59.335888shield sshd\[12442\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip191.ip-51-68-97.eu user=root 2019-12-12T07:52:01.388646shield sshd\[12442\]: Failed password for root from 51.68.97.191 port 46824 ssh2 2019-12-12T07:59:40.926479shield sshd\[14992\]: Invalid user nasruddin from 51.68.97.191 port 55552 2019-12-12T07:59:40.930951shield sshd\[14992\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip191.ip-51-68-97.eu 2019-12-12T07:59:42.938179shield sshd\[14992\]: Failed password for invalid user nasruddin from 51.68.97.191 port 55552 ssh2 |
2019-12-12 17:50:38 |
| 170.254.229.178 | attackspam | sshd jail - ssh hack attempt |
2019-12-12 18:01:03 |
| 206.189.138.22 | attackbotsspam | 2019-12-12T08:01:25.931135shield sshd\[15753\]: Invalid user ubuntu from 206.189.138.22 port 52914 2019-12-12T08:01:25.935474shield sshd\[15753\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.138.22 2019-12-12T08:01:28.015857shield sshd\[15753\]: Failed password for invalid user ubuntu from 206.189.138.22 port 52914 ssh2 2019-12-12T08:02:39.372110shield sshd\[16273\]: Invalid user ubuntu from 206.189.138.22 port 23775 2019-12-12T08:02:39.376457shield sshd\[16273\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.138.22 |
2019-12-12 17:41:29 |
| 187.188.183.27 | attack | ../../mnt/custom/ProductDefinition |
2019-12-12 18:06:46 |