City: Madrid
Region: Comunidad de Madrid
Country: Spain
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 192.145.38.49
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 55258
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;192.145.38.49. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2026010601 1800 900 604800 86400
;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 07 12:00:43 CST 2026
;; MSG SIZE rcvd: 106
Host 49.38.145.192.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 49.38.145.192.in-addr.arpa: NXDOMAIN
| IP | Type | Details | Datetime |
|---|---|---|---|
| 72.239.45.143 | attackspambots | Automatic report - Port Scan Attack |
2019-12-22 20:49:37 |
| 206.189.171.204 | attack | Dec 22 09:14:53 Ubuntu-1404-trusty-64-minimal sshd\[20122\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.171.204 user=root Dec 22 09:14:54 Ubuntu-1404-trusty-64-minimal sshd\[20122\]: Failed password for root from 206.189.171.204 port 51640 ssh2 Dec 22 09:23:45 Ubuntu-1404-trusty-64-minimal sshd\[24978\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.171.204 user=root Dec 22 09:23:47 Ubuntu-1404-trusty-64-minimal sshd\[24978\]: Failed password for root from 206.189.171.204 port 57046 ssh2 Dec 22 09:28:50 Ubuntu-1404-trusty-64-minimal sshd\[27084\]: Invalid user admin from 206.189.171.204 Dec 22 09:28:50 Ubuntu-1404-trusty-64-minimal sshd\[27084\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.171.204 |
2019-12-22 21:05:14 |
| 217.77.221.85 | attack | Dec 22 00:16:20 hanapaa sshd\[30339\]: Invalid user test from 217.77.221.85 Dec 22 00:16:20 hanapaa sshd\[30339\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=static-217-77-221-85.wildpark.net Dec 22 00:16:21 hanapaa sshd\[30339\]: Failed password for invalid user test from 217.77.221.85 port 51370 ssh2 Dec 22 00:21:33 hanapaa sshd\[30771\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=static-217-77-221-85.wildpark.net user=backup Dec 22 00:21:36 hanapaa sshd\[30771\]: Failed password for backup from 217.77.221.85 port 53775 ssh2 |
2019-12-22 21:25:25 |
| 115.231.156.236 | attackbotsspam | Lines containing failures of 115.231.156.236 Dec 19 19:56:03 icinga sshd[5302]: Invalid user ftpuser from 115.231.156.236 port 52560 Dec 19 19:56:03 icinga sshd[5302]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.231.156.236 Dec 19 19:56:05 icinga sshd[5302]: Failed password for invalid user ftpuser from 115.231.156.236 port 52560 ssh2 Dec 19 19:56:06 icinga sshd[5302]: Received disconnect from 115.231.156.236 port 52560:11: Bye Bye [preauth] Dec 19 19:56:06 icinga sshd[5302]: Disconnected from invalid user ftpuser 115.231.156.236 port 52560 [preauth] Dec 19 20:08:17 icinga sshd[8482]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.231.156.236 user=bin Dec 19 20:08:19 icinga sshd[8482]: Failed password for bin from 115.231.156.236 port 38074 ssh2 Dec 19 20:08:19 icinga sshd[8482]: Received disconnect from 115.231.156.236 port 38074:11: Bye Bye [preauth] Dec 19 20:08:19 icinga ssh........ ------------------------------ |
2019-12-22 20:52:23 |
| 118.107.243.29 | attack | Dec 22 13:31:51 meumeu sshd[25518]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.107.243.29 Dec 22 13:31:54 meumeu sshd[25518]: Failed password for invalid user steiner from 118.107.243.29 port 57806 ssh2 Dec 22 13:37:59 meumeu sshd[26309]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.107.243.29 ... |
2019-12-22 20:51:59 |
| 117.90.39.2 | attackbots | Dec 21 00:04:26 riskplan-s sshd[28699]: reveeclipse mapping checking getaddrinfo for 2.39.90.117.broad.zj.js.dynamic.163data.com.cn [117.90.39.2] failed - POSSIBLE BREAK-IN ATTEMPT! Dec 21 00:04:26 riskplan-s sshd[28699]: Invalid user admin from 117.90.39.2 Dec 21 00:04:26 riskplan-s sshd[28699]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.90.39.2 Dec 21 00:04:27 riskplan-s sshd[28699]: Failed password for invalid user admin from 117.90.39.2 port 32128 ssh2 Dec 21 00:04:27 riskplan-s sshd[28699]: Received disconnect from 117.90.39.2: 11: Bye Bye [preauth] Dec 21 00:19:39 riskplan-s sshd[28989]: reveeclipse mapping checking getaddrinfo for 2.39.90.117.broad.zj.js.dynamic.163data.com.cn [117.90.39.2] failed - POSSIBLE BREAK-IN ATTEMPT! Dec 21 00:19:39 riskplan-s sshd[28989]: Invalid user michhostnameake from 117.90.39.2 Dec 21 00:19:39 riskplan-s sshd[28989]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=........ ------------------------------- |
2019-12-22 20:46:30 |
| 73.229.232.218 | attackspam | Dec 22 02:14:09 sachi sshd\[14612\]: Invalid user bevens from 73.229.232.218 Dec 22 02:14:09 sachi sshd\[14612\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=c-73-229-232-218.hsd1.co.comcast.net Dec 22 02:14:11 sachi sshd\[14612\]: Failed password for invalid user bevens from 73.229.232.218 port 42256 ssh2 Dec 22 02:20:04 sachi sshd\[15154\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=c-73-229-232-218.hsd1.co.comcast.net user=root Dec 22 02:20:06 sachi sshd\[15154\]: Failed password for root from 73.229.232.218 port 48826 ssh2 |
2019-12-22 20:57:57 |
| 125.166.116.124 | attackbots | Unauthorized connection attempt detected from IP address 125.166.116.124 to port 445 |
2019-12-22 21:20:02 |
| 159.89.134.199 | attackspam | Dec 22 02:41:24 wbs sshd\[30655\]: Invalid user jmckervey from 159.89.134.199 Dec 22 02:41:24 wbs sshd\[30655\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.134.199 Dec 22 02:41:26 wbs sshd\[30655\]: Failed password for invalid user jmckervey from 159.89.134.199 port 51092 ssh2 Dec 22 02:46:39 wbs sshd\[31120\]: Invalid user guest from 159.89.134.199 Dec 22 02:46:39 wbs sshd\[31120\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.134.199 |
2019-12-22 21:00:36 |
| 109.194.54.126 | attackspambots | Dec 22 00:23:31 hpm sshd\[20686\]: Invalid user gimp from 109.194.54.126 Dec 22 00:23:31 hpm sshd\[20686\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.194.54.126 Dec 22 00:23:33 hpm sshd\[20686\]: Failed password for invalid user gimp from 109.194.54.126 port 54494 ssh2 Dec 22 00:29:12 hpm sshd\[21223\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.194.54.126 user=root Dec 22 00:29:14 hpm sshd\[21223\]: Failed password for root from 109.194.54.126 port 59360 ssh2 |
2019-12-22 21:17:15 |
| 1.1.219.197 | attackbotsspam | firewall-block, port(s): 8291/tcp |
2019-12-22 20:49:56 |
| 163.172.13.168 | attackbotsspam | Dec 22 17:38:59 gw1 sshd[23846]: Failed password for backup from 163.172.13.168 port 56920 ssh2 ... |
2019-12-22 20:47:56 |
| 106.13.216.239 | attack | Dec 22 13:27:59 server sshd\[28228\]: Invalid user duconge from 106.13.216.239 Dec 22 13:27:59 server sshd\[28228\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.216.239 Dec 22 13:28:02 server sshd\[28228\]: Failed password for invalid user duconge from 106.13.216.239 port 40234 ssh2 Dec 22 13:37:31 server sshd\[30702\]: Invalid user lr from 106.13.216.239 Dec 22 13:37:31 server sshd\[30702\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.216.239 ... |
2019-12-22 21:09:21 |
| 122.199.152.114 | attack | SSH Brute Force |
2019-12-22 21:08:31 |
| 206.189.233.154 | attackbots | Too many connections or unauthorized access detected from Arctic banned ip |
2019-12-22 21:15:57 |