城市(city): unknown
省份(region): unknown
国家(country): United States
运营商(isp): Verizon
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 75.242.200.14
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 29262
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;75.242.200.14. IN A
;; AUTHORITY SECTION:
. 347 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022020300 1800 900 604800 86400
;; Query time: 62 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 03 19:36:37 CST 2022
;; MSG SIZE rcvd: 10614.200.242.75.in-addr.arpa domain name pointer 14.sub-75-242-200.myvzw.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
14.200.242.75.in-addr.arpa name = 14.sub-75-242-200.myvzw.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 165.22.103.237 | attackbotsspam | Apr 27 05:38:01 xeon sshd[33115]: Failed password for invalid user hzt from 165.22.103.237 port 38146 ssh2 |
2020-04-27 19:20:49 |
| 78.128.113.42 | attackbotsspam | Apr 27 12:57:31 debian-2gb-nbg1-2 kernel: \[10243982.723985\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=78.128.113.42 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=31917 PROTO=TCP SPT=52340 DPT=7393 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-04-27 19:18:59 |
| 103.129.223.101 | attackbots | Apr 27 11:48:12 [host] sshd[14860]: pam_unix(sshd: Apr 27 11:48:13 [host] sshd[14860]: Failed passwor Apr 27 11:51:19 [host] sshd[15002]: Invalid user u |
2020-04-27 19:16:22 |
| 91.209.114.181 | attackbots | (From sam@ukvirtuallysorted.com) Hello, First, I'd just like to say that I hope that you, your colleagues and loved ones are all healthy and well. Whilst self-isolation is affecting the whole country and is making office life impossible, we find many companies having to revert to working from home “online” and with current circumstances being uncertain, there’s likely going to be a period of adjustment whilst you implement the infrastructure required to support this new way of working. We, at Virtually Sorted UK, firmly believe Virtual Assistants have a huge role to play in helping businesses navigate the waters during this unsettling period. Here are some of the services Virtually Sorted UK supports businesses with: • Diary & Inbox Management • Complex Travel Arrangements & Logistics • Reports & Presentation • Expenses & Invoicing • Proofreading • Minute takings • Research • CRM • Recruitment If you have some time in the next few days, let me know and I will schedule a call to d |
2020-04-27 19:26:53 |
| 80.82.78.104 | attack | scans once in preceeding hours on the ports (in chronological order) 4567 resulting in total of 59 scans from 80.82.64.0/20 block. |
2020-04-27 19:25:37 |
| 159.89.177.46 | attack | Apr 27 13:42:59 lukav-desktop sshd\[24604\]: Invalid user prakash from 159.89.177.46 Apr 27 13:42:59 lukav-desktop sshd\[24604\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.177.46 Apr 27 13:43:01 lukav-desktop sshd\[24604\]: Failed password for invalid user prakash from 159.89.177.46 port 32902 ssh2 Apr 27 13:47:02 lukav-desktop sshd\[24820\]: Invalid user augustine from 159.89.177.46 Apr 27 13:47:02 lukav-desktop sshd\[24820\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.177.46 |
2020-04-27 19:16:43 |
| 190.129.49.62 | attackbotsspam | 2020-04-27T13:20:32.808659struts4.enskede.local sshd\[32303\]: Invalid user bt from 190.129.49.62 port 33084 2020-04-27T13:20:32.814588struts4.enskede.local sshd\[32303\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.129.49.62 2020-04-27T13:20:36.331651struts4.enskede.local sshd\[32303\]: Failed password for invalid user bt from 190.129.49.62 port 33084 ssh2 2020-04-27T13:25:25.677295struts4.enskede.local sshd\[32438\]: Invalid user mai from 190.129.49.62 port 47064 2020-04-27T13:25:25.683560struts4.enskede.local sshd\[32438\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.129.49.62 ... |
2020-04-27 19:32:35 |
| 138.118.56.22 | attackbotsspam | firewall-block, port(s): 1433/tcp |
2020-04-27 19:15:08 |
| 89.35.39.180 | attackspam | C1,WP GET /wp-login.php GET /buecher/wp-login.php |
2020-04-27 19:12:09 |
| 162.12.217.214 | attack | Apr 27 11:38:26 melroy-server sshd[14351]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.12.217.214 Apr 27 11:38:27 melroy-server sshd[14351]: Failed password for invalid user hy from 162.12.217.214 port 58664 ssh2 ... |
2020-04-27 19:29:23 |
| 43.241.63.44 | attackspambots | (sshd) Failed SSH login from 43.241.63.44 (IN/India/-): 5 in the last 3600 secs |
2020-04-27 19:13:50 |
| 128.199.253.228 | attack | Apr 27 05:50:16 raspberrypi sshd[5186]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.253.228 |
2020-04-27 19:06:02 |
| 178.62.248.185 | attackbotsspam | Apr 27 08:49:17 debian-2gb-nbg1-2 kernel: \[10229089.697588\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=178.62.248.185 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=242 ID=53308 PROTO=TCP SPT=50697 DPT=12528 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-04-27 19:11:40 |
| 106.13.160.55 | attackbots | $f2bV_matches |
2020-04-27 19:32:11 |
| 79.137.33.20 | attack | (sshd) Failed SSH login from 79.137.33.20 (FR/France/20.ip-79-137-33.eu): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr 27 10:37:10 srv sshd[19492]: Invalid user carlos from 79.137.33.20 port 33390 Apr 27 10:37:12 srv sshd[19492]: Failed password for invalid user carlos from 79.137.33.20 port 33390 ssh2 Apr 27 10:45:58 srv sshd[19734]: Invalid user aurore from 79.137.33.20 port 41372 Apr 27 10:46:00 srv sshd[19734]: Failed password for invalid user aurore from 79.137.33.20 port 41372 ssh2 Apr 27 10:49:06 srv sshd[19814]: Invalid user mg from 79.137.33.20 port 38962 |
2020-04-27 18:59:36 |