City: unknown
Region: unknown
Country: United States of America (the)
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 21.172.196.39
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 43674
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;21.172.196.39. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012700 1800 900 604800 86400
;; Query time: 34 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 27 16:11:35 CST 2025
;; MSG SIZE rcvd: 106
Host 39.196.172.21.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 39.196.172.21.in-addr.arpa: NXDOMAIN
IP | Type | Details | Datetime |
---|---|---|---|
106.12.27.117 | attackspam | $f2bV_matches |
2019-11-17 03:48:06 |
202.138.248.62 | attack | A spam email was sent from this SMTP server. This kind of spam emails had the following features.: - They attempted to camouflage the SMTP server with a KDDI's legitimate server. - The domain of URLs in the messages was best-self.info (103.212.223.59). |
2019-11-17 03:56:47 |
222.186.180.17 | attack | Nov 16 21:20:38 tux-35-217 sshd\[9808\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.17 user=root Nov 16 21:20:40 tux-35-217 sshd\[9808\]: Failed password for root from 222.186.180.17 port 46406 ssh2 Nov 16 21:20:44 tux-35-217 sshd\[9808\]: Failed password for root from 222.186.180.17 port 46406 ssh2 Nov 16 21:20:48 tux-35-217 sshd\[9808\]: Failed password for root from 222.186.180.17 port 46406 ssh2 ... |
2019-11-17 04:22:06 |
106.12.178.127 | attackbots | Invalid user ssh from 106.12.178.127 port 40426 |
2019-11-17 04:13:33 |
200.126.81.128 | attackbotsspam | DATE:2019-11-16 15:47:27, IP:200.126.81.128, PORT:telnet Telnet brute force auth on honeypot server (honey-neo-dc) |
2019-11-17 04:11:09 |
103.48.193.7 | attackbotsspam | SSHScan |
2019-11-17 04:10:00 |
195.142.107.163 | attack | 11/16/2019-15:47:30.338733 195.142.107.163 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433 |
2019-11-17 04:04:41 |
116.196.80.104 | attackbotsspam | Nov 16 17:32:58 Invalid user nen from 116.196.80.104 port 51026 |
2019-11-17 04:16:32 |
59.3.71.222 | attackbotsspam | SSH Brute Force, server-1 sshd[9131]: Failed password for invalid user darcy from 59.3.71.222 port 44096 ssh2 |
2019-11-17 04:08:21 |
188.166.150.17 | attack | SSH Brute Force, server-1 sshd[9099]: Failed password for invalid user mostad from 188.166.150.17 port 45088 ssh2 |
2019-11-17 04:06:22 |
104.238.99.130 | attackbots | Automatic report - Banned IP Access |
2019-11-17 04:13:19 |
45.143.221.17 | attack | *Port Scan* detected from 45.143.221.17 (NL/Netherlands/-). 11 hits in the last 110 seconds |
2019-11-17 03:50:57 |
167.114.97.209 | attackspam | Nov 16 16:50:09 SilenceServices sshd[13870]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.114.97.209 Nov 16 16:50:11 SilenceServices sshd[13870]: Failed password for invalid user ident from 167.114.97.209 port 50338 ssh2 Nov 16 16:54:30 SilenceServices sshd[15147]: Failed password for root from 167.114.97.209 port 58898 ssh2 |
2019-11-17 04:11:40 |
106.12.93.25 | attackbots | 2019-11-16T19:35:45.429601shield sshd\[16743\]: Invalid user kafka from 106.12.93.25 port 35378 2019-11-16T19:35:45.434079shield sshd\[16743\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.93.25 2019-11-16T19:35:47.443917shield sshd\[16743\]: Failed password for invalid user kafka from 106.12.93.25 port 35378 ssh2 2019-11-16T19:39:51.406107shield sshd\[17777\]: Invalid user alyxzander from 106.12.93.25 port 49316 2019-11-16T19:39:51.410296shield sshd\[17777\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.93.25 |
2019-11-17 03:52:35 |
122.224.175.218 | attack | Nov 16 14:47:54 *** sshd[27800]: User backup from 122.224.175.218 not allowed because not listed in AllowUsers |
2019-11-17 03:49:42 |