城市(city): unknown
省份(region): unknown
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 169.229.140.138
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 25076
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;169.229.140.138. IN A
;; AUTHORITY SECTION:
. 157 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022062202 1800 900 604800 86400
;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jun 23 06:13:23 CST 2022
;; MSG SIZE rcvd: 108138.140.229.169.in-addr.arpa domain name pointer ursp2013-sb.urel.berkeley.edu.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
138.140.229.169.in-addr.arpa name = ursp2013-sb.urel.berkeley.edu.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 168.235.103.66 | attackspambots | Nov 5 11:13:41 rama sshd[434526]: Address 168.235.103.66 maps to caradmirers.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! Nov 5 11:13:41 rama sshd[434526]: Invalid user pano from 168.235.103.66 Nov 5 11:13:41 rama sshd[434526]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.235.103.66 Nov 5 11:13:42 rama sshd[434526]: Failed password for invalid user pano from 168.235.103.66 port 57080 ssh2 Nov 5 11:13:43 rama sshd[434526]: Received disconnect from 168.235.103.66: 11: Bye Bye [preauth] Nov 5 11:25:10 rama sshd[441013]: Address 168.235.103.66 maps to caradmirers.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! Nov 5 11:25:10 rama sshd[441013]: Invalid user gamefiles from 168.235.103.66 Nov 5 11:25:10 rama sshd[441013]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.235.103.66 Nov 5 11:25:12 rama sshd[441013]: Faile........ ------------------------------- |
2019-11-09 20:17:32 |
| 139.59.23.68 | attack | Nov 9 02:49:16 tdfoods sshd\[14907\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.23.68 user=root Nov 9 02:49:18 tdfoods sshd\[14907\]: Failed password for root from 139.59.23.68 port 50686 ssh2 Nov 9 02:53:26 tdfoods sshd\[15272\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.23.68 user=root Nov 9 02:53:28 tdfoods sshd\[15272\]: Failed password for root from 139.59.23.68 port 60440 ssh2 Nov 9 02:57:45 tdfoods sshd\[15630\]: Invalid user fedora from 139.59.23.68 |
2019-11-09 21:01:34 |
| 222.186.190.2 | attack | pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.190.2 user=root Failed password for root from 222.186.190.2 port 51262 ssh2 Failed password for root from 222.186.190.2 port 51262 ssh2 Failed password for root from 222.186.190.2 port 51262 ssh2 Failed password for root from 222.186.190.2 port 51262 ssh2 |
2019-11-09 20:26:40 |
| 184.105.247.227 | attack | firewall-block, port(s): 5353/udp |
2019-11-09 20:34:30 |
| 172.58.38.155 | attackspambots | Chat Spam |
2019-11-09 20:38:15 |
| 121.227.43.114 | attack | SASL broute force |
2019-11-09 20:29:08 |
| 157.230.156.51 | attack | Nov 9 10:48:12 server sshd\[18704\]: Invalid user zte from 157.230.156.51 Nov 9 10:48:12 server sshd\[18704\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.156.51 Nov 9 10:48:14 server sshd\[18704\]: Failed password for invalid user zte from 157.230.156.51 port 40280 ssh2 Nov 9 11:09:06 server sshd\[23900\]: Invalid user max from 157.230.156.51 Nov 9 11:09:06 server sshd\[23900\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.156.51 ... |
2019-11-09 20:40:27 |
| 119.29.11.242 | attackbots | Nov 8 22:39:54 web1 sshd\[22987\]: Invalid user admin from 119.29.11.242 Nov 8 22:39:54 web1 sshd\[22987\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.11.242 Nov 8 22:39:56 web1 sshd\[22987\]: Failed password for invalid user admin from 119.29.11.242 port 52706 ssh2 Nov 8 22:45:44 web1 sshd\[23499\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.11.242 user=root Nov 8 22:45:46 web1 sshd\[23499\]: Failed password for root from 119.29.11.242 port 59334 ssh2 |
2019-11-09 20:47:30 |
| 45.227.253.141 | attack | 2019-11-09T13:16:44.061069mail01 postfix/smtpd[5812]: warning: unknown[45.227.253.141]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 2019-11-09T13:16:50.417190mail01 postfix/smtpd[15804]: warning: unknown[45.227.253.141]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 2019-11-09T13:16:51.417677mail01 postfix/smtpd[9558]: warning: unknown[45.227.253.141]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 |
2019-11-09 20:26:06 |
| 167.114.157.86 | attackspam | Nov 9 13:21:15 SilenceServices sshd[6911]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.114.157.86 Nov 9 13:21:17 SilenceServices sshd[6911]: Failed password for invalid user 1234567 from 167.114.157.86 port 41989 ssh2 Nov 9 13:24:47 SilenceServices sshd[7944]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.114.157.86 |
2019-11-09 20:53:23 |
| 179.83.194.167 | attackbotsspam | Automatic report - Port Scan Attack |
2019-11-09 20:55:40 |
| 45.143.220.21 | attack | SIPVicious Scanner Detection, PTR: PTR record not found |
2019-11-09 20:49:11 |
| 119.29.121.229 | attack | $f2bV_matches |
2019-11-09 20:23:58 |
| 111.20.234.58 | attackbotsspam | IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/111.20.234.58/ CN - 1H : (116) Protection Against DDoS WordPress plugin : "odzyskiwanie danych help-dysk" IP Address Ranges by Country : CN NAME ASN : ASN9808 IP : 111.20.234.58 CIDR : 111.20.0.0/16 PREFIX COUNT : 3598 UNIQUE IP COUNT : 18819072 ATTACKS DETECTED ASN9808 : 1H - 1 3H - 1 6H - 2 12H - 3 24H - 8 DateTime : 2019-11-09 07:20:35 INFO : Port MAX SCAN Scan Detected and Blocked by ADMIN - data recovery |
2019-11-09 20:53:08 |
| 218.1.18.78 | attack | SSH Brute Force |
2019-11-09 20:44:36 |