City: unknown
Region: unknown
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 134.207.102.137
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 6466
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;134.207.102.137. IN A
;; AUTHORITY SECTION:
. 600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022021702 1800 900 604800 86400
;; Query time: 77 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 07:02:56 CST 2022
;; MSG SIZE rcvd: 108b'Host 137.102.207.134.in-addr.arpa. not found: 3(NXDOMAIN)
'server can't find 134.207.102.137.in-addr.arpa: SERVFAIL| IP | Type | Details | Datetime |
|---|---|---|---|
| 46.217.1.29 | attackspam | 1581256961 - 02/09/2020 15:02:41 Host: 46.217.1.29/46.217.1.29 Port: 445 TCP Blocked |
2020-02-10 03:13:30 |
| 220.129.186.125 | attackspam | Telnet/23 MH Probe, BF, Hack - |
2020-02-10 02:47:18 |
| 109.108.86.63 | attack | Automatic report - Port Scan Attack |
2020-02-10 03:02:28 |
| 172.105.3.22 | attack | 172.105.3.22 was recorded 9 times by 9 hosts attempting to connect to the following ports: 123. Incident counter (4h, 24h, all-time): 9, 9, 9 |
2020-02-10 03:04:35 |
| 198.12.116.238 | attackbots | SSH-bruteforce attempts |
2020-02-10 03:21:39 |
| 185.104.187.116 | attack | 0,48-02/05 [bc01/m09] PostRequest-Spammer scoring: Durban01 |
2020-02-10 02:59:33 |
| 116.73.24.9 | attack | Fail2Ban Ban Triggered |
2020-02-10 03:29:22 |
| 27.74.244.56 | attackspam | Unauthorized connection attempt from IP address 27.74.244.56 on Port 445(SMB) |
2020-02-10 03:06:20 |
| 137.74.166.77 | attackspam | Feb 9 14:53:57 dedicated sshd[26155]: Invalid user nfj from 137.74.166.77 port 57290 |
2020-02-10 02:54:10 |
| 120.29.158.173 | attackspam | Feb 9 17:20:34 l02a sshd[17882]: Invalid user yko from 120.29.158.173 Feb 9 17:20:34 l02a sshd[17882]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.29.158.173 Feb 9 17:20:34 l02a sshd[17882]: Invalid user yko from 120.29.158.173 Feb 9 17:20:36 l02a sshd[17882]: Failed password for invalid user yko from 120.29.158.173 port 37484 ssh2 |
2020-02-10 03:05:35 |
| 114.69.249.194 | attack | Feb 9 14:25:56 ovpn sshd\[10483\]: Invalid user jza from 114.69.249.194 Feb 9 14:25:56 ovpn sshd\[10483\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.69.249.194 Feb 9 14:25:58 ovpn sshd\[10483\]: Failed password for invalid user jza from 114.69.249.194 port 42811 ssh2 Feb 9 14:32:03 ovpn sshd\[11935\]: Invalid user dzk from 114.69.249.194 Feb 9 14:32:03 ovpn sshd\[11935\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.69.249.194 |
2020-02-10 03:02:00 |
| 203.156.132.3 | attack | 20/2/9@09:22:14: FAIL: Alarm-Intrusion address from=203.156.132.3 ... |
2020-02-10 03:13:58 |
| 27.106.18.218 | attack | Feb 9 19:20:59 gw1 sshd[1606]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=27.106.18.218 Feb 9 19:21:01 gw1 sshd[1606]: Failed password for invalid user qnf from 27.106.18.218 port 36598 ssh2 ... |
2020-02-10 03:10:24 |
| 42.113.131.150 | attackbotsspam | 20/2/9@11:41:42: FAIL: Alarm-Network address from=42.113.131.150 ... |
2020-02-10 02:51:48 |
| 222.186.31.166 | attack | pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.166 user=root Failed password for root from 222.186.31.166 port 55547 ssh2 Failed password for root from 222.186.31.166 port 55547 ssh2 Failed password for root from 222.186.31.166 port 55547 ssh2 pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.166 user=root |
2020-02-10 03:04:05 |