City: unknown
Region: unknown
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.21.66.45
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 5551
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.21.66.45. IN A
;; AUTHORITY SECTION:
. 197 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022021701 1800 900 604800 86400
;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 02:45:09 CST 2022
;; MSG SIZE rcvd: 105Host 45.66.21.104.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 45.66.21.104.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 94.179.129.53 | attackbots | Jan 14 22:13:02 jane sshd[2892]: Failed password for root from 94.179.129.53 port 38194 ssh2 ... |
2020-01-15 05:36:47 |
| 106.12.26.160 | attack | Unauthorized connection attempt detected from IP address 106.12.26.160 to port 2220 [J] |
2020-01-15 05:41:25 |
| 107.174.151.78 | attackbots | (From eric@talkwithcustomer.com) Hello romechiropractic.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 romechiropractic.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 romechiropractic.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 |
2020-01-15 06:02:49 |
| 46.38.144.17 | attackspambots | Jan 14 22:37:42 relay postfix/smtpd\[24087\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jan 14 22:38:06 relay postfix/smtpd\[30806\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jan 14 22:38:30 relay postfix/smtpd\[24087\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jan 14 22:38:55 relay postfix/smtpd\[31838\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jan 14 22:39:19 relay postfix/smtpd\[24091\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-01-15 05:47:06 |
| 67.207.106.230 | attack | Unauthorized connection attempt from IP address 67.207.106.230 on Port 445(SMB) |
2020-01-15 05:59:14 |
| 107.175.13.74 | attack | (From eric@talkwithcustomer.com) Hello romechiropractic.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 romechiropractic.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 romechiropractic.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 |
2020-01-15 06:01:25 |
| 185.176.27.122 | attack | 01/14/2020-16:32:47.608322 185.176.27.122 Protocol: 6 ET SCAN NMAP -sS window 1024 |
2020-01-15 05:39:09 |
| 95.183.50.93 | attackbotsspam | Unauthorized connection attempt detected from IP address 95.183.50.93 to port 2220 [J] |
2020-01-15 05:57:20 |
| 39.37.143.179 | attack | Unauthorized connection attempt from IP address 39.37.143.179 on Port 445(SMB) |
2020-01-15 06:04:01 |
| 36.110.78.62 | attack | Jan 14 11:30:05 hanapaa sshd\[5133\]: Invalid user webuser from 36.110.78.62 Jan 14 11:30:05 hanapaa sshd\[5133\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.110.78.62 Jan 14 11:30:07 hanapaa sshd\[5133\]: Failed password for invalid user webuser from 36.110.78.62 port 49236 ssh2 Jan 14 11:34:24 hanapaa sshd\[5456\]: Invalid user test123 from 36.110.78.62 Jan 14 11:34:24 hanapaa sshd\[5456\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.110.78.62 |
2020-01-15 05:50:25 |
| 218.92.0.205 | attackspam | Jan 14 21:10:45 zeus sshd[1709]: Failed password for root from 218.92.0.205 port 20166 ssh2 Jan 14 21:10:49 zeus sshd[1709]: Failed password for root from 218.92.0.205 port 20166 ssh2 Jan 14 21:10:53 zeus sshd[1709]: Failed password for root from 218.92.0.205 port 20166 ssh2 Jan 14 21:17:30 zeus sshd[1781]: Failed password for root from 218.92.0.205 port 46623 ssh2 |
2020-01-15 05:33:44 |
| 2.185.18.234 | attackbotsspam | 1579036609 - 01/14/2020 22:16:49 Host: 2.185.18.234/2.185.18.234 Port: 445 TCP Blocked |
2020-01-15 06:04:28 |
| 112.85.42.188 | attackspambots | 01/14/2020-16:46:09.168622 112.85.42.188 Protocol: 6 ET SCAN Potential SSH Scan |
2020-01-15 05:48:28 |
| 155.4.35.142 | attackspambots | Jan 14 16:16:58 Tower sshd[15121]: Connection from 155.4.35.142 port 36636 on 192.168.10.220 port 22 rdomain "" Jan 14 16:17:14 Tower sshd[15121]: Invalid user developer from 155.4.35.142 port 36636 Jan 14 16:17:14 Tower sshd[15121]: error: Could not get shadow information for NOUSER Jan 14 16:17:14 Tower sshd[15121]: Failed password for invalid user developer from 155.4.35.142 port 36636 ssh2 Jan 14 16:17:14 Tower sshd[15121]: Received disconnect from 155.4.35.142 port 36636:11: Bye Bye [preauth] Jan 14 16:17:14 Tower sshd[15121]: Disconnected from invalid user developer 155.4.35.142 port 36636 [preauth] |
2020-01-15 05:32:50 |
| 27.128.230.190 | attackspambots | Jan 14 18:16:53 firewall sshd[16369]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.128.230.190 Jan 14 18:16:53 firewall sshd[16369]: Invalid user support from 27.128.230.190 Jan 14 18:16:54 firewall sshd[16369]: Failed password for invalid user support from 27.128.230.190 port 59984 ssh2 ... |
2020-01-15 05:57:48 |