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 <<>> 140.4.149.102
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 26496
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;140.4.149.102. IN A
;; AUTHORITY SECTION:
. 600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2024052401 1800 900 604800 86400
;; Query time: 23 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat May 25 04:11:04 CST 2024
;; MSG SIZE rcvd: 106
b'Host 102.149.4.140.in-addr.arpa. not found: 3(NXDOMAIN)
'
server can't find 140.4.149.102.in-addr.arpa: SERVFAIL
| IP | Type | Details | Datetime |
|---|---|---|---|
| 114.31.5.154 | attackbots | spam, scanner BC |
2019-11-16 14:18:57 |
| 144.217.214.13 | attack | SSH bruteforce |
2019-11-16 14:52:31 |
| 31.52.157.179 | attack | Automatic report - Port Scan Attack |
2019-11-16 14:58:02 |
| 203.191.150.157 | attack | 1433/tcp 1433/tcp 1433/tcp [2019-10-18/11-16]3pkt |
2019-11-16 14:16:10 |
| 84.255.152.10 | attackspam | 2019-11-16T06:05:24.824921abusebot-5.cloudsearch.cf sshd\[25703\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.255.152.10 user=root |
2019-11-16 14:16:26 |
| 200.169.1.232 | attack | port scan and connect, tcp 8080 (http-proxy) |
2019-11-16 14:16:47 |
| 222.186.175.215 | attack | Nov 16 08:49:23 sauna sshd[29316]: Failed password for root from 222.186.175.215 port 60816 ssh2 Nov 16 08:49:35 sauna sshd[29316]: error: maximum authentication attempts exceeded for root from 222.186.175.215 port 60816 ssh2 [preauth] ... |
2019-11-16 14:52:05 |
| 36.239.147.45 | attackspam | Fail2Ban Ban Triggered |
2019-11-16 14:54:33 |
| 80.82.77.139 | attack | 80.82.77.139 was recorded 10 times by 8 hosts attempting to connect to the following ports: 179,1010,3000,3689,3001,47808,666,5900,1911,9443. Incident counter (4h, 24h, all-time): 10, 90, 1256 |
2019-11-16 14:52:52 |
| 183.237.218.221 | attackspambots | Nov 16 07:28:49 srv01 postfix/smtpd\[2134\]: warning: unknown\[183.237.218.221\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Nov 16 07:28:59 srv01 postfix/smtpd\[1917\]: warning: unknown\[183.237.218.221\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Nov 16 07:29:14 srv01 postfix/smtpd\[1917\]: warning: unknown\[183.237.218.221\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Nov 16 07:29:26 srv01 postfix/smtpd\[2134\]: warning: unknown\[183.237.218.221\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Nov 16 07:29:41 srv01 postfix/smtpd\[1917\]: warning: unknown\[183.237.218.221\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2019-11-16 14:58:51 |
| 51.255.234.209 | attack | Nov 16 07:03:16 dedicated sshd[30515]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.255.234.209 user=root Nov 16 07:03:18 dedicated sshd[30515]: Failed password for root from 51.255.234.209 port 52360 ssh2 |
2019-11-16 14:18:02 |
| 123.195.76.116 | attackbots | 23/tcp 9001/tcp... [2019-10-22/11-16]4pkt,2pt.(tcp) |
2019-11-16 14:28:51 |
| 107.170.190.16 | attackspam | *Port Scan* detected from 107.170.190.16 (US/United States/-). 4 hits in the last 205 seconds |
2019-11-16 14:08:13 |
| 46.38.144.17 | attack | Nov 16 07:20:21 relay postfix/smtpd\[26001\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Nov 16 07:20:41 relay postfix/smtpd\[31201\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Nov 16 07:20:58 relay postfix/smtpd\[32243\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Nov 16 07:21:18 relay postfix/smtpd\[333\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Nov 16 07:21:36 relay postfix/smtpd\[27065\]: warning: unknown\[46.38.144.17\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2019-11-16 14:22:53 |
| 122.235.250.120 | attackspambots | Triggered by Fail2Ban at Vostok web server |
2019-11-16 14:24:26 |