City: unknown
Region: unknown
Country: Brazil
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 54.94.193.14
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24273
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;54.94.193.14. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020401 1800 900 604800 86400
;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 05 06:17:21 CST 2025
;; MSG SIZE rcvd: 10514.193.94.54.in-addr.arpa domain name pointer ec2-54-94-193-14.sa-east-1.compute.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
14.193.94.54.in-addr.arpa name = ec2-54-94-193-14.sa-east-1.compute.amazonaws.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 154.223.136.86 | attack | [portscan] tcp/22 [SSH] in blocklist.de:'listed [ssh]' *(RWIN=65535)(02221027) |
2020-02-22 20:39:31 |
| 23.94.153.187 | attackbotsspam | ET CINS Active Threat Intelligence Poor Reputation IP group 9 - port: 10701 proto: TCP cat: Misc Attack |
2020-02-22 20:44:21 |
| 184.167.32.172 | attack | Feb 22 10:31:21 ns382633 sshd\[21123\]: Invalid user mumble from 184.167.32.172 port 42632 Feb 22 10:31:21 ns382633 sshd\[21123\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=184.167.32.172 Feb 22 10:31:22 ns382633 sshd\[21123\]: Failed password for invalid user mumble from 184.167.32.172 port 42632 ssh2 Feb 22 11:18:21 ns382633 sshd\[28630\]: Invalid user hduser from 184.167.32.172 port 34518 Feb 22 11:18:21 ns382633 sshd\[28630\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=184.167.32.172 |
2020-02-22 20:23:03 |
| 103.212.223.67 | attack | Feb 22 12:19:21 lnxmail61 postfix/submission/smtpd[8382]: lost connection after CONNECT from unknown[103.212.223.67] Feb 22 12:19:55 lnxmail61 postfix/submission/smtpd[8382]: warning: unknown[103.212.223.67]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Feb 22 12:19:55 lnxmail61 postfix/submission/smtpd[8382]: warning: unknown[103.212.223.67]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Feb 22 12:20:03 lnxmail61 postfix/submission/smtpd[8382]: lost connection after AUTH from unknown[103.212.223.67] |
2020-02-22 20:41:04 |
| 177.1.213.19 | attackbots | Feb 22 06:31:41 ns382633 sshd\[14997\]: Invalid user usuario from 177.1.213.19 port 6565 Feb 22 06:31:41 ns382633 sshd\[14997\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.1.213.19 Feb 22 06:31:44 ns382633 sshd\[14997\]: Failed password for invalid user usuario from 177.1.213.19 port 6565 ssh2 Feb 22 06:45:50 ns382633 sshd\[17359\]: Invalid user bb2 from 177.1.213.19 port 52008 Feb 22 06:45:50 ns382633 sshd\[17359\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.1.213.19 |
2020-02-22 20:57:36 |
| 187.207.150.68 | attackbots | Lines containing failures of 187.207.150.68 Feb 22 07:05:11 newdogma sshd[689]: Invalid user user from 187.207.150.68 port 36698 Feb 22 07:05:11 newdogma sshd[689]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.207.150.68 Feb 22 07:05:13 newdogma sshd[689]: Failed password for invalid user user from 187.207.150.68 port 36698 ssh2 Feb 22 07:05:15 newdogma sshd[689]: Received disconnect from 187.207.150.68 port 36698:11: Bye Bye [preauth] Feb 22 07:05:15 newdogma sshd[689]: Disconnected from invalid user user 187.207.150.68 port 36698 [preauth] Feb 22 07:14:44 newdogma sshd[772]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.207.150.68 user=r.r Feb 22 07:14:46 newdogma sshd[772]: Failed password for r.r from 187.207.150.68 port 44420 ssh2 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=187.207.150.68 |
2020-02-22 20:26:11 |
| 185.173.35.45 | attack | 02/22/2020-07:24:39.614808 185.173.35.45 Protocol: 6 ET SCAN NMAP -sS window 1024 |
2020-02-22 20:29:37 |
| 181.197.93.224 | attackbotsspam | Fail2Ban Ban Triggered |
2020-02-22 20:25:34 |
| 106.13.47.10 | attackspambots | Feb 22 09:41:45 firewall sshd[22177]: Invalid user share from 106.13.47.10 Feb 22 09:41:47 firewall sshd[22177]: Failed password for invalid user share from 106.13.47.10 port 34832 ssh2 Feb 22 09:45:49 firewall sshd[22318]: Invalid user robert from 106.13.47.10 ... |
2020-02-22 20:53:39 |
| 103.73.76.74 | attackbots | 20/2/21@23:43:10: FAIL: Alarm-Network address from=103.73.76.74 20/2/21@23:43:10: FAIL: Alarm-Network address from=103.73.76.74 ... |
2020-02-22 20:25:53 |
| 109.167.200.10 | attack | Automatic report BANNED IP |
2020-02-22 20:54:56 |
| 129.211.24.104 | attack | Feb 22 01:27:03 dallas01 sshd[5509]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.24.104 Feb 22 01:27:05 dallas01 sshd[5509]: Failed password for invalid user sysbackup from 129.211.24.104 port 42860 ssh2 Feb 22 01:30:17 dallas01 sshd[7514]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.24.104 |
2020-02-22 20:54:38 |
| 190.217.68.204 | attackspambots | Unauthorized connection attempt detected from IP address 190.217.68.204 to port 445 |
2020-02-22 20:24:56 |
| 217.5.227.203 | attackspam | 20 attempts against mh-ssh on cloud |
2020-02-22 20:52:32 |
| 1.55.140.83 | attackbotsspam | Fail2Ban Ban Triggered |
2020-02-22 20:24:21 |