City: unknown
Region: unknown
Country: South Korea
Internet Service Provider: unknown
Hostname: unknown
Organization: Korea Telecom
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 211.42.154.164
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 36529
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;211.42.154.164. IN A
;; AUTHORITY SECTION:
. 3600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019080801 1800 900 604800 86400
;; Query time: 2 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Fri Aug 09 03:53:10 CST 2019
;; MSG SIZE rcvd: 118
Host 164.154.42.211.in-addr.arpa not found: 2(SERVFAIL)
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
*** Can't find 164.154.42.211.in-addr.arpa.: No answer
Authoritative answers can be found from:
IP | Type | Details | Datetime |
---|---|---|---|
167.99.146.21 | attack | Apr 17 12:57:10 debian-2gb-nbg1-2 kernel: \[9380006.670067\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=167.99.146.21 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=242 ID=1208 PROTO=TCP SPT=57386 DPT=18400 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-04-17 20:04:35 |
192.144.136.109 | attackspambots | SSH Brute-Force reported by Fail2Ban |
2020-04-17 20:01:34 |
114.67.79.46 | attackbots | 2020-04-17T10:54:56.619745upcloud.m0sh1x2.com sshd[7645]: Invalid user v from 114.67.79.46 port 46308 |
2020-04-17 20:21:41 |
66.187.161.112 | attack | Apr 17 01:48:46 web1 sshd\[15494\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.187.161.112 user=root Apr 17 01:48:48 web1 sshd\[15494\]: Failed password for root from 66.187.161.112 port 42070 ssh2 Apr 17 01:52:40 web1 sshd\[15894\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.187.161.112 user=root Apr 17 01:52:41 web1 sshd\[15894\]: Failed password for root from 66.187.161.112 port 50400 ssh2 Apr 17 01:56:29 web1 sshd\[16275\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=66.187.161.112 user=root |
2020-04-17 20:10:30 |
188.254.0.160 | attackbotsspam | Invalid user zc from 188.254.0.160 port 42934 |
2020-04-17 20:16:26 |
79.124.62.82 | attackspam | 3305/tcp 3401/tcp 8250/tcp... [2020-03-17/04-17]1231pkt,474pt.(tcp) |
2020-04-17 19:56:22 |
189.41.94.196 | attack | Honeypot attack, port: 81, PTR: 189-041-094-196.xd-dynamic.algarnetsuper.com.br. |
2020-04-17 20:01:52 |
101.231.154.154 | attack | SSH bruteforce |
2020-04-17 19:57:57 |
94.200.211.242 | attack | Telnet/23 MH Probe, Scan, BF, Hack - |
2020-04-17 20:20:45 |
49.234.212.177 | attackbots | Bruteforce detected by fail2ban |
2020-04-17 20:24:09 |
122.114.131.13 | attack | 2020-04-17T07:28:11.6419851495-001 sshd[35885]: Invalid user ftpadmin from 122.114.131.13 port 49417 2020-04-17T07:28:13.8507891495-001 sshd[35885]: Failed password for invalid user ftpadmin from 122.114.131.13 port 49417 ssh2 2020-04-17T07:38:04.4195811495-001 sshd[36151]: Invalid user admin from 122.114.131.13 port 49417 2020-04-17T07:38:04.4225801495-001 sshd[36151]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.114.131.13 2020-04-17T07:38:04.4195811495-001 sshd[36151]: Invalid user admin from 122.114.131.13 port 49417 2020-04-17T07:38:06.0352591495-001 sshd[36151]: Failed password for invalid user admin from 122.114.131.13 port 49417 ssh2 ... |
2020-04-17 20:03:11 |
79.124.62.66 | attack | Fail2Ban Ban Triggered |
2020-04-17 20:00:35 |
150.109.63.204 | attackbots | SSH brute-force: detected 6 distinct usernames within a 24-hour window. |
2020-04-17 20:14:34 |
91.218.88.128 | attackspam | Telnet/23 MH Probe, Scan, BF, Hack - |
2020-04-17 20:15:49 |
45.40.201.5 | attack | Apr 17 14:13:16 eventyay sshd[14234]: Failed password for root from 45.40.201.5 port 49020 ssh2 Apr 17 14:16:23 eventyay sshd[14328]: Failed password for root from 45.40.201.5 port 49960 ssh2 ... |
2020-04-17 20:24:26 |