City: unknown
Region: unknown
Country: IANA Special-Purpose Address
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 10.19.38.109
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 39821
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;10.19.38.109. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021800 1800 900 604800 86400
;; Query time: 41 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 17:02:15 CST 2025
;; MSG SIZE rcvd: 105Host 109.38.19.10.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 109.38.19.10.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 1.10.188.42 | attackspam | Automatic report - XMLRPC Attack |
2019-11-01 03:23:04 |
| 106.13.119.163 | attackspam | Oct 31 17:35:16 cavern sshd[10011]: Failed password for root from 106.13.119.163 port 54606 ssh2 |
2019-11-01 03:37:23 |
| 148.70.136.94 | attack | 2019-10-30 21:37:24,934 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 148.70.136.94 2019-10-30 22:00:10,827 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 148.70.136.94 2019-10-30 22:18:17,490 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 148.70.136.94 2019-10-30 22:36:28,643 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 148.70.136.94 2019-10-30 22:55:03,080 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 148.70.136.94 2019-10-30 21:37:24,934 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 148.70.136.94 2019-10-30 22:00:10,827 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 148.70.136.94 2019-10-30 22:18:17,490 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 148.70.136.94 2019-10-30 22:36:28,643 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 148.70.136.94 2019-10-30 22:55:03,080 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 148.70.136.94 2019-10-30 21:37:24,934 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 148.70.136.94 2019-10-30 2 |
2019-11-01 03:51:05 |
| 83.110.73.177 | attackspambots | scan r |
2019-11-01 03:42:05 |
| 188.162.199.42 | attackspam | failed_logins |
2019-11-01 03:35:55 |
| 52.164.211.22 | attackspambots | SSH Brute Force, server-1 sshd[24127]: Failed password for root from 52.164.211.22 port 40352 ssh2 |
2019-11-01 03:50:31 |
| 114.7.15.169 | attackbots | PostgreSQL port 5432 |
2019-11-01 03:51:37 |
| 31.3.152.200 | attack | Trying ports that it shouldn't be. |
2019-11-01 03:30:17 |
| 209.208.111.71 | attack | IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/209.208.111.71/ US - 1H : (246) Protection Against DDoS WordPress plugin : "odzyskiwanie danych help-dysk" IP Address Ranges by Country : US NAME ASN : ASN6364 IP : 209.208.111.71 CIDR : 209.208.64.0/18 PREFIX COUNT : 55 UNIQUE IP COUNT : 60928 ATTACKS DETECTED ASN6364 : 1H - 1 3H - 1 6H - 1 12H - 1 24H - 1 DateTime : 2019-10-31 12:57:53 INFO : Server 301 - Looking for resource vulnerabilities Detected and Blocked by ADMIN - data recovery |
2019-11-01 03:51:55 |
| 190.104.233.28 | attack | Oct 31 19:15:41 hosting sshd[8606]: Invalid user brian from 190.104.233.28 port 57734 ... |
2019-11-01 03:41:47 |
| 192.99.57.32 | attackbots | 2019-10-30 20:09:12,460 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 192.99.57.32 2019-10-30 20:27:28,850 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 192.99.57.32 2019-10-30 20:45:49,311 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 192.99.57.32 2019-10-30 21:04:25,251 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 192.99.57.32 2019-10-30 21:34:15,337 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 192.99.57.32 2019-10-30 20:09:12,460 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 192.99.57.32 2019-10-30 20:27:28,850 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 192.99.57.32 2019-10-30 20:45:49,311 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 192.99.57.32 2019-10-30 21:04:25,251 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 192.99.57.32 2019-10-30 21:34:15,337 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 192.99.57.32 2019-10-30 20:09:12,460 fail2ban.actions \[1865\]: NOTICE \[ssh\] Ban 192.99.57.32 2019-10-30 20:27:28,850 |
2019-11-01 03:30:34 |
| 119.48.16.182 | attack | invalid login attempt |
2019-11-01 03:40:35 |
| 185.216.27.64 | attack | Oct 31 03:08:04 *** sshd[24409]: Address 185.216.27.64 maps to 64.27.216.185.static.reveeclipse.proxgroup.fr, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! Oct 31 03:08:04 *** sshd[24409]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.216.27.64 user=r.r Oct 31 03:08:05 *** sshd[24409]: Failed password for r.r from 185.216.27.64 port 42304 ssh2 Oct 31 03:08:05 *** sshd[24409]: Received disconnect from 185.216.27.64: 11: Bye Bye [preauth] Oct 31 04:10:45 *** sshd[1360]: Address 185.216.27.64 maps to 64.27.216.185.static.reveeclipse.proxgroup.fr, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! Oct 31 04:10:45 *** sshd[1360]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.216.27.64 user=r.r Oct 31 04:10:47 *** sshd[1360]: Failed password for r.r from 185.216.27.64 port 42764 ssh2 Oct 31 04:10:47 *** sshd[1360]: Received disconnect from........ ------------------------------- |
2019-11-01 03:47:11 |
| 149.202.115.157 | attackspambots | k+ssh-bruteforce |
2019-11-01 03:50:05 |
| 45.124.86.65 | attackbotsspam | Oct 31 14:01:50 vpn01 sshd[2728]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.124.86.65 Oct 31 14:01:51 vpn01 sshd[2728]: Failed password for invalid user aaaaaa123 from 45.124.86.65 port 33334 ssh2 ... |
2019-11-01 03:46:58 |