City: unknown
Region: unknown
Country: China
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 113.6.168.48
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 48328
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;113.6.168.48. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025031201 1800 900 604800 86400
;; Query time: 38 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Mar 13 07:20:46 CST 2025
;; MSG SIZE rcvd: 105b'Host 48.168.6.113.in-addr.arpa not found: 2(SERVFAIL)
'server can't find 113.6.168.48.in-addr.arpa: SERVFAIL| IP | Type | Details | Datetime |
|---|---|---|---|
| 45.82.35.37 | attackspambots | Postfix RBL failed |
2020-01-03 04:13:32 |
| 35.247.138.99 | attackspam | xmlrpc attack |
2020-01-03 04:06:38 |
| 142.44.251.207 | attackspam | $f2bV_matches |
2020-01-03 04:00:23 |
| 134.209.115.206 | attackbots | Jan 2 16:27:58 ns382633 sshd\[26776\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.115.206 user=root Jan 2 16:28:00 ns382633 sshd\[26776\]: Failed password for root from 134.209.115.206 port 47026 ssh2 Jan 2 16:46:19 ns382633 sshd\[30039\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.115.206 user=root Jan 2 16:46:22 ns382633 sshd\[30039\]: Failed password for root from 134.209.115.206 port 38712 ssh2 Jan 2 16:48:35 ns382633 sshd\[30216\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.115.206 user=root |
2020-01-03 04:03:17 |
| 183.6.107.248 | attackspam | Jan 2 16:16:33 dedicated sshd[7751]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.6.107.248 user=root Jan 2 16:16:35 dedicated sshd[7751]: Failed password for root from 183.6.107.248 port 39028 ssh2 |
2020-01-03 03:56:41 |
| 103.81.85.21 | attackspam | xmlrpc attack |
2020-01-03 04:24:23 |
| 185.65.134.181 | attackbots | /cgi-bin/hi3510/getidentify.cgi |
2020-01-03 04:09:51 |
| 51.91.136.174 | attack | Jan 2 14:19:18 plusreed sshd[21473]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.91.136.174 user=root Jan 2 14:19:20 plusreed sshd[21473]: Failed password for root from 51.91.136.174 port 57512 ssh2 ... |
2020-01-03 04:12:59 |
| 185.142.236.35 | attack | Unauthorized connection attempt detected from IP address 185.142.236.35 to port 1604 |
2020-01-03 04:01:15 |
| 210.212.237.67 | attackspambots | SSH bruteforce (Triggered fail2ban) |
2020-01-03 03:49:57 |
| 45.182.137.191 | attackspambots | port scan and connect, tcp 23 (telnet) |
2020-01-03 04:12:01 |
| 104.244.75.12 | attack | Jan 2 16:53:53 server2 sshd\[15823\]: Invalid user ubnt from 104.244.75.12 Jan 2 16:53:53 server2 sshd\[15825\]: Invalid user admin from 104.244.75.12 Jan 2 16:53:54 server2 sshd\[15827\]: User root from 104.244.75.12 not allowed because not listed in AllowUsers Jan 2 16:53:54 server2 sshd\[15829\]: Invalid user 1234 from 104.244.75.12 Jan 2 16:53:54 server2 sshd\[15831\]: Invalid user usuario from 104.244.75.12 Jan 2 16:53:54 server2 sshd\[15833\]: Invalid user support from 104.244.75.12 |
2020-01-03 04:15:13 |
| 222.186.190.92 | attackbotsspam | Jan 2 21:12:24 nextcloud sshd\[19853\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.190.92 user=root Jan 2 21:12:26 nextcloud sshd\[19853\]: Failed password for root from 222.186.190.92 port 41394 ssh2 Jan 2 21:12:44 nextcloud sshd\[20270\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.190.92 user=root ... |
2020-01-03 04:14:02 |
| 217.182.95.250 | attackbots | tries to exploit known vulnerabilities in WordPress waists system resources blocked |
2020-01-03 04:21:45 |
| 183.83.163.243 | attackbotsspam | 1577976826 - 01/02/2020 15:53:46 Host: 183.83.163.243/183.83.163.243 Port: 445 TCP Blocked |
2020-01-03 04:19:32 |