City: unknown
Region: unknown
Country: None
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 239.7.40.36
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 25137
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;239.7.40.36. IN A
;; AUTHORITY SECTION:
. 428 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022011101 1800 900 604800 86400
;; Query time: 56 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 12 04:41:18 CST 2022
;; MSG SIZE rcvd: 104
Host 36.40.7.239.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 36.40.7.239.in-addr.arpa: NXDOMAIN
| IP | Type | Details | Datetime |
|---|---|---|---|
| 139.9.235.252 | attack | Unauthorized connection attempt detected from IP address 139.9.235.252 to port 348 |
2019-12-31 22:43:31 |
| 218.92.0.164 | attackspambots | Dec 30 21:07:28 debian sshd[467]: Unable to negotiate with 218.92.0.164 port 23682: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1 [preauth] Dec 31 10:01:27 debian sshd[6525]: Unable to negotiate with 218.92.0.164 port 60587: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1 [preauth] ... |
2019-12-31 23:05:15 |
| 124.88.188.3 | attack | Unauthorized connection attempt detected from IP address 124.88.188.3 to port 1433 |
2019-12-31 22:44:56 |
| 122.224.175.218 | attack | Dec 31 15:51:22 vps691689 sshd[19907]: Failed password for root from 122.224.175.218 port 28843 ssh2 Dec 31 15:54:23 vps691689 sshd[19974]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.224.175.218 ... |
2019-12-31 23:04:18 |
| 192.3.4.106 | attackbotsspam | (From eric@talkwithcustomer.com) Hello naturalhealthdcs.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 naturalhealthdcs.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 naturalhealthdcs.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 – as one f |
2019-12-31 22:58:20 |
| 223.72.94.140 | attack | Unauthorized connection attempt detected from IP address 223.72.94.140 to port 3389 |
2019-12-31 22:37:13 |
| 117.107.174.98 | attackspam | Unauthorized connection attempt detected from IP address 117.107.174.98 to port 445 |
2019-12-31 22:23:58 |
| 120.244.115.167 | attackbots | Unauthorized connection attempt detected from IP address 120.244.115.167 to port 3389 |
2019-12-31 22:47:06 |
| 107.175.92.123 | attackspam | (From eric@talkwithcustomer.com) Hello naturalhealthdcs.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 naturalhealthdcs.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 naturalhealthdcs.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 – as one f |
2019-12-31 23:01:42 |
| 111.122.175.73 | attack | Unauthorized connection attempt detected from IP address 111.122.175.73 to port 1433 |
2019-12-31 22:53:50 |
| 222.186.190.2 | attack | Dec 31 15:54:11 sd-53420 sshd\[13450\]: User root from 222.186.190.2 not allowed because none of user's groups are listed in AllowGroups Dec 31 15:54:12 sd-53420 sshd\[13450\]: Failed none for invalid user root from 222.186.190.2 port 15266 ssh2 Dec 31 15:54:12 sd-53420 sshd\[13450\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.190.2 user=root Dec 31 15:54:14 sd-53420 sshd\[13450\]: Failed password for invalid user root from 222.186.190.2 port 15266 ssh2 Dec 31 15:54:25 sd-53420 sshd\[13450\]: Failed password for invalid user root from 222.186.190.2 port 15266 ssh2 ... |
2019-12-31 22:59:59 |
| 110.137.101.3 | attack | Unauthorized connection attempt detected from IP address 110.137.101.3 to port 445 |
2019-12-31 22:55:10 |
| 58.245.139.178 | attackspambots | Unauthorized connection attempt detected from IP address 58.245.139.178 to port 5555 |
2019-12-31 22:31:25 |
| 106.75.79.172 | attack | Unauthorized connection attempt detected from IP address 106.75.79.172 to port 548 |
2019-12-31 22:27:48 |
| 118.71.1.72 | attack | Unauthorized connection attempt detected from IP address 118.71.1.72 to port 445 |
2019-12-31 22:51:04 |