City: unknown
Region: unknown
Country: Uruguay
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 167.56.34.160
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 15778
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;167.56.34.160. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025013101 1800 900 604800 86400
;; Query time: 39 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 01 03:33:23 CST 2025
;; MSG SIZE rcvd: 106
160.34.56.167.in-addr.arpa domain name pointer r167-56-34-160.dialup.adsl.anteldata.net.uy.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
160.34.56.167.in-addr.arpa name = r167-56-34-160.dialup.adsl.anteldata.net.uy.
Authoritative answers can be found from:
| IP | Type | Details | Datetime |
|---|---|---|---|
| 194.247.27.169 | attackbots | slow and persistent scanner |
2019-11-01 07:38:39 |
| 101.71.2.111 | attack | Oct 31 19:54:22 firewall sshd[3172]: Failed password for root from 101.71.2.111 port 56540 ssh2 Oct 31 19:59:11 firewall sshd[3234]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.71.2.111 user=root Oct 31 19:59:13 firewall sshd[3234]: Failed password for root from 101.71.2.111 port 47135 ssh2 ... |
2019-11-01 07:23:10 |
| 134.175.154.93 | attackspam | Invalid user ntop from 134.175.154.93 port 41704 |
2019-11-01 07:51:20 |
| 112.221.179.133 | attackbotsspam | Nov 1 00:15:13 server sshd\[15140\]: User root from 112.221.179.133 not allowed because listed in DenyUsers Nov 1 00:15:13 server sshd\[15140\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.221.179.133 user=root Nov 1 00:15:15 server sshd\[15140\]: Failed password for invalid user root from 112.221.179.133 port 59618 ssh2 Nov 1 00:19:42 server sshd\[17634\]: User root from 112.221.179.133 not allowed because listed in DenyUsers Nov 1 00:19:42 server sshd\[17634\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.221.179.133 user=root |
2019-11-01 07:27:26 |
| 194.247.27.36 | attackspam | slow and persistent scanner |
2019-11-01 07:19:10 |
| 103.58.92.5 | attackspambots | Nov 1 00:55:42 sauna sshd[143960]: Failed password for sync from 103.58.92.5 port 49464 ssh2 ... |
2019-11-01 07:16:02 |
| 31.46.16.95 | attackspam | Oct 31 17:04:09 TORMINT sshd\[14354\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.46.16.95 user=root Oct 31 17:04:12 TORMINT sshd\[14354\]: Failed password for root from 31.46.16.95 port 48652 ssh2 Oct 31 17:08:13 TORMINT sshd\[14550\]: Invalid user edition from 31.46.16.95 Oct 31 17:08:13 TORMINT sshd\[14550\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.46.16.95 ... |
2019-11-01 07:10:31 |
| 89.33.8.34 | attack | ET CINS Active Threat Intelligence Poor Reputation IP group 85 - port: 53 proto: UDP cat: Misc Attack |
2019-11-01 07:13:07 |
| 122.188.209.253 | attackspam | Oct 31 21:02:18 host sshd[19445]: User r.r from 122.188.209.253 not allowed because none of user's groups are listed in AllowGroups Oct 31 21:02:18 host sshd[19445]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.188.209.253 user=r.r Oct 31 21:02:19 host sshd[19445]: Failed password for invalid user r.r from 122.188.209.253 port 36059 ssh2 Oct 31 21:02:20 host sshd[19445]: Received disconnect from 122.188.209.253 port 36059:11: Bye Bye [preauth] Oct 31 21:02:20 host sshd[19445]: Disconnected from invalid user r.r 122.188.209.253 port 36059 [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=122.188.209.253 |
2019-11-01 07:44:11 |
| 119.57.117.222 | attack | 10/31/2019-21:11:27.485228 119.57.117.222 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433 |
2019-11-01 07:12:51 |
| 200.164.217.212 | attack | 2019-10-31T23:07:47.735706abusebot-5.cloudsearch.cf sshd\[5597\]: Invalid user test from 200.164.217.212 port 49749 |
2019-11-01 07:22:33 |
| 216.83.57.10 | attackspam | Oct 31 10:40:33 auw2 sshd\[21217\]: Invalid user jacob from 216.83.57.10 Oct 31 10:40:33 auw2 sshd\[21217\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=216.83.57.10 Oct 31 10:40:35 auw2 sshd\[21217\]: Failed password for invalid user jacob from 216.83.57.10 port 44921 ssh2 Oct 31 10:46:22 auw2 sshd\[21691\]: Invalid user beheerder from 216.83.57.10 Oct 31 10:46:22 auw2 sshd\[21691\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=216.83.57.10 |
2019-11-01 07:48:08 |
| 117.69.30.240 | attackspambots | Brute force SMTP login attempts. |
2019-11-01 07:36:52 |
| 49.88.112.76 | attack | 2019-10-31T23:18:40.642781abusebot-3.cloudsearch.cf sshd\[6935\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.76 user=root |
2019-11-01 07:18:47 |
| 94.23.39.179 | attack | FTPD brute force attack detected by fail2ban |
2019-11-01 07:14:18 |