城市(city): unknown
省份(region): unknown
国家(country): United States of America (the)
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 69.116.141.105
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 11014
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;69.116.141.105. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021100 1800 900 604800 86400
;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 11 13:49:26 CST 2025
;; MSG SIZE rcvd: 107
105.141.116.69.in-addr.arpa domain name pointer ool-45748d69.dyn.optonline.net.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
105.141.116.69.in-addr.arpa name = ool-45748d69.dyn.optonline.net.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 103.13.58.4 | attack | Apr 9 14:44:35 h1637304 sshd[14541]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.13.58.4 Apr 9 14:44:37 h1637304 sshd[14541]: Failed password for invalid user user from 103.13.58.4 port 56668 ssh2 Apr 9 14:44:37 h1637304 sshd[14541]: Received disconnect from 103.13.58.4: 11: Bye Bye [preauth] Apr 9 14:46:57 h1637304 sshd[19091]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.13.58.4 Apr 9 14:46:59 h1637304 sshd[19091]: Failed password for invalid user a1 from 103.13.58.4 port 51894 ssh2 Apr 9 14:47:00 h1637304 sshd[19091]: Received disconnect from 103.13.58.4: 11: Bye Bye [preauth] Apr 9 14:48:27 h1637304 sshd[19122]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.13.58.4 Apr 9 14:48:29 h1637304 sshd[19122]: Failed password for invalid user serverson from 103.13.58.4 port 38322 ssh2 Apr 9 14:48:30 h1637304 sshd[19122]: Rec........ ------------------------------- |
2020-04-10 09:03:46 |
| 139.99.219.208 | attack | Apr 9 21:50:21 ip-172-31-61-156 sshd[9614]: Failed password for ubuntu from 139.99.219.208 port 59764 ssh2 Apr 9 21:53:43 ip-172-31-61-156 sshd[9708]: Invalid user asakura from 139.99.219.208 Apr 9 21:53:43 ip-172-31-61-156 sshd[9708]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.99.219.208 Apr 9 21:53:43 ip-172-31-61-156 sshd[9708]: Invalid user asakura from 139.99.219.208 Apr 9 21:53:45 ip-172-31-61-156 sshd[9708]: Failed password for invalid user asakura from 139.99.219.208 port 57085 ssh2 ... |
2020-04-10 09:24:21 |
| 129.211.104.34 | attackbotsspam | Apr 10 00:50:55 icinga sshd[34692]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.104.34 Apr 10 00:50:57 icinga sshd[34692]: Failed password for invalid user discover from 129.211.104.34 port 59966 ssh2 Apr 10 00:58:07 icinga sshd[45796]: Failed password for root from 129.211.104.34 port 42006 ssh2 ... |
2020-04-10 09:22:29 |
| 45.133.99.16 | attackspambots | Apr 10 00:24:48 mail postfix/smtpd\[5525\]: warning: unknown\[45.133.99.16\]: SASL PLAIN authentication failed: \ Apr 10 00:25:05 mail postfix/smtpd\[5525\]: warning: unknown\[45.133.99.16\]: SASL PLAIN authentication failed: \ Apr 10 00:26:06 mail postfix/smtpd\[5462\]: warning: unknown\[45.133.99.16\]: SASL PLAIN authentication failed: \ Apr 10 01:04:14 mail postfix/smtpd\[6186\]: warning: unknown\[45.133.99.16\]: SASL PLAIN authentication failed: \ Apr 10 01:04:14 mail postfix/smtpd\[6311\]: warning: unknown\[45.133.99.16\]: SASL PLAIN authentication failed: \ Apr 10 01:04:14 mail postfix/smtpd\[6414\]: warning: unknown\[45.133.99.16\]: SASL PLAIN authentication failed: \ |
2020-04-10 09:06:39 |
| 219.139.131.131 | attack | SASL PLAIN auth failed: ruser=... |
2020-04-10 09:20:58 |
| 164.132.196.134 | attack | Apr 10 00:49:13 lukav-desktop sshd\[1110\]: Invalid user tomcat from 164.132.196.134 Apr 10 00:49:13 lukav-desktop sshd\[1110\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.196.134 Apr 10 00:49:15 lukav-desktop sshd\[1110\]: Failed password for invalid user tomcat from 164.132.196.134 port 35480 ssh2 Apr 10 00:54:12 lukav-desktop sshd\[2312\]: Invalid user aiswaria from 164.132.196.134 Apr 10 00:54:12 lukav-desktop sshd\[2312\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=164.132.196.134 |
2020-04-10 09:02:23 |
| 122.51.198.90 | attackspam | Apr 9 23:53:50 ip-172-31-62-245 sshd\[25427\]: Invalid user postgres from 122.51.198.90\ Apr 9 23:53:51 ip-172-31-62-245 sshd\[25427\]: Failed password for invalid user postgres from 122.51.198.90 port 50886 ssh2\ Apr 9 23:59:27 ip-172-31-62-245 sshd\[25588\]: Invalid user user1 from 122.51.198.90\ Apr 9 23:59:29 ip-172-31-62-245 sshd\[25588\]: Failed password for invalid user user1 from 122.51.198.90 port 50080 ssh2\ Apr 10 00:02:35 ip-172-31-62-245 sshd\[25666\]: Invalid user chef from 122.51.198.90\ |
2020-04-10 09:02:52 |
| 92.154.73.22 | attack | WordPress login Brute force / Web App Attack on client site. |
2020-04-10 09:24:46 |
| 182.219.172.224 | attackbotsspam | Apr 10 07:47:49 itv-usvr-02 sshd[22943]: Invalid user crack from 182.219.172.224 port 32888 Apr 10 07:47:49 itv-usvr-02 sshd[22943]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.219.172.224 Apr 10 07:47:49 itv-usvr-02 sshd[22943]: Invalid user crack from 182.219.172.224 port 32888 Apr 10 07:47:52 itv-usvr-02 sshd[22943]: Failed password for invalid user crack from 182.219.172.224 port 32888 ssh2 Apr 10 07:51:55 itv-usvr-02 sshd[23105]: Invalid user bot from 182.219.172.224 port 41876 |
2020-04-10 09:27:04 |
| 23.254.69.107 | attackspam | (From kruger.ezra@gmail.com) Hello , I'm sure you already know how important it is to have a list... And there are a bunch of autoresponders already on the market to choose from... BUT they have all gotten complacent and are going the way of the dinosaurs! Why? It's because you need to meet your customers where THEY are by using the 3 Most Powerful Platforms on the planet! 1. Email 2. Facebook Messenger (using chatbots) 3. Web Push Notifications When you combine these 3 powerful communication services into your list building your ROI goes through the Roof! Check Out the Demo Video Here: https://digitalmarketinghacks.net/smartengage Because the bottom line is...the more eyes you have seeing your messages, the more money you make! And today, a BREAKTHROUGH autoresponder has been released to the masses which allows you to do EXACTLY that. This new platform seamlessly combines Email with Facebook Messenger, & Web Push notifications in a completely integrated and centralized das |
2020-04-10 08:57:31 |
| 73.253.70.51 | attackbotsspam | Apr 9 22:17:38 vps46666688 sshd[31495]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=73.253.70.51 Apr 9 22:17:39 vps46666688 sshd[31495]: Failed password for invalid user postgres from 73.253.70.51 port 47442 ssh2 ... |
2020-04-10 09:28:37 |
| 128.199.212.194 | attack | 128.199.212.194 - - [09/Apr/2020:23:54:00 +0200] "GET /wp-login.php HTTP/1.1" 200 5702 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 128.199.212.194 - - [09/Apr/2020:23:54:04 +0200] "POST /wp-login.php HTTP/1.1" 200 6601 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 128.199.212.194 - - [09/Apr/2020:23:54:10 +0200] "POST /xmlrpc.php HTTP/1.1" 200 427 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" |
2020-04-10 09:05:50 |
| 106.13.216.231 | attackspam | Apr 10 01:30:28 odroid64 sshd\[30824\]: Invalid user admin from 106.13.216.231 Apr 10 01:30:28 odroid64 sshd\[30824\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.216.231 ... |
2020-04-10 09:21:35 |
| 121.15.2.178 | attack | Apr 10 02:50:06 srv-ubuntu-dev3 sshd[120555]: Invalid user ubuntu from 121.15.2.178 Apr 10 02:50:06 srv-ubuntu-dev3 sshd[120555]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.15.2.178 Apr 10 02:50:06 srv-ubuntu-dev3 sshd[120555]: Invalid user ubuntu from 121.15.2.178 Apr 10 02:50:07 srv-ubuntu-dev3 sshd[120555]: Failed password for invalid user ubuntu from 121.15.2.178 port 44698 ssh2 Apr 10 02:51:59 srv-ubuntu-dev3 sshd[120890]: Invalid user deploy from 121.15.2.178 Apr 10 02:51:59 srv-ubuntu-dev3 sshd[120890]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.15.2.178 Apr 10 02:51:59 srv-ubuntu-dev3 sshd[120890]: Invalid user deploy from 121.15.2.178 Apr 10 02:52:02 srv-ubuntu-dev3 sshd[120890]: Failed password for invalid user deploy from 121.15.2.178 port 38056 ssh2 Apr 10 02:53:40 srv-ubuntu-dev3 sshd[121258]: Invalid user ubuntu from 121.15.2.178 ... |
2020-04-10 09:17:19 |
| 89.40.73.201 | attackspambots | apr/10 00:42:49 firewall,info PORTSCAN input: in:PPPOE proto TCP (SYN), 89.40.73.201:6000->188.x.x.x:8085, len 44 apr/10 00:42:49 firewall,info PORTSCAN input: in:PPPOE proto TCP (RST), 89.40.73.201:6000->188.x.x.x:88, len 40 apr/10 00:42:50 firewall,info PORTSCAN input: in:PPPOE proto TCP (RST), 89.40.73.201:6000->188.x.x.x:88, len 40 apr/10 00:42:52 firewall,info PORTSCAN input: in:PPPOE proto TCP (RST), 89.40.73.201:6000->188.x.x.x:88, len 40 apr/10 00:42:57 firewall,info PORTSCAN input: in:PPPOE proto TCP (RST), 89.40.73.201:6000->188.x.x.x:88, len 40 apr/10 00:43:05 firewall,info PORTSCAN input: in:PPPOE proto TCP (RST), 89.40.73.201:6000->188.x.x.x:88, len 40 |
2020-04-10 09:02:11 |