城市(city): unknown
省份(region): unknown
国家(country): Japan
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.154.142.11
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 5955
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;139.154.142.11. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012401 1800 900 604800 86400
;; Query time: 37 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Jan 25 01:44:40 CST 2025
;; MSG SIZE rcvd: 107Host 11.142.154.139.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 11.142.154.139.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 112.85.42.188 | attackspam | 04/16/2020-10:14:29.845997 112.85.42.188 Protocol: 6 ET SCAN Potential SSH Scan |
2020-04-16 22:15:02 |
| 198.199.103.92 | attackspam | Apr 16 14:01:44 ns382633 sshd\[26144\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.199.103.92 user=root Apr 16 14:01:46 ns382633 sshd\[26144\]: Failed password for root from 198.199.103.92 port 43779 ssh2 Apr 16 14:14:37 ns382633 sshd\[28654\]: Invalid user oracle from 198.199.103.92 port 42118 Apr 16 14:14:37 ns382633 sshd\[28654\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=198.199.103.92 Apr 16 14:14:39 ns382633 sshd\[28654\]: Failed password for invalid user oracle from 198.199.103.92 port 42118 ssh2 |
2020-04-16 21:54:41 |
| 106.12.69.90 | attack | SSH Brute-Force reported by Fail2Ban |
2020-04-16 22:18:43 |
| 107.174.231.173 | attack | (From eric@talkwithwebvisitor.com) Good day, My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations What for? Part of my job is to check out websites and the work you’ve done with plinkechiropractic.com definitely stands out. It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality. There is, however, a catch… more accurately, a question… So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know? More importantly, how do you make a connection with that person? Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind. Here’s a way to create INSTANT engagement that you may not have known about… Talk With Web Visitor is a software widget that’s works on your site, ready to capture |
2020-04-16 21:48:15 |
| 222.186.190.17 | attack | Apr 16 13:15:49 ip-172-31-62-245 sshd\[19804\]: Failed password for root from 222.186.190.17 port 38551 ssh2\ Apr 16 13:16:27 ip-172-31-62-245 sshd\[19825\]: Failed password for root from 222.186.190.17 port 45137 ssh2\ Apr 16 13:17:44 ip-172-31-62-245 sshd\[19836\]: Failed password for root from 222.186.190.17 port 54857 ssh2\ Apr 16 13:18:22 ip-172-31-62-245 sshd\[19840\]: Failed password for root from 222.186.190.17 port 56351 ssh2\ Apr 16 13:18:25 ip-172-31-62-245 sshd\[19840\]: Failed password for root from 222.186.190.17 port 56351 ssh2\ |
2020-04-16 21:56:21 |
| 165.227.58.61 | attackspam | Apr 16 05:08:31 pixelmemory sshd[3205]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.58.61 Apr 16 05:08:33 pixelmemory sshd[3205]: Failed password for invalid user www from 165.227.58.61 port 41850 ssh2 Apr 16 05:21:16 pixelmemory sshd[6708]: Failed password for root from 165.227.58.61 port 40500 ssh2 ... |
2020-04-16 22:27:51 |
| 182.180.128.132 | attackbotsspam | Apr 16 15:36:18 haigwepa sshd[2457]: Failed password for root from 182.180.128.132 port 54494 ssh2 ... |
2020-04-16 21:59:14 |
| 46.102.175.105 | attack | firewall-block, port(s): 5564/tcp |
2020-04-16 22:06:17 |
| 181.55.127.245 | attack | Apr 16 14:07:23 *** sshd[7261]: Invalid user git from 181.55.127.245 |
2020-04-16 22:09:34 |
| 185.176.27.246 | attackbotsspam | 04/16/2020-09:50:28.920202 185.176.27.246 Protocol: 6 ET SCAN NMAP -sS window 1024 |
2020-04-16 21:58:43 |
| 79.72.70.205 | attack | Apr 16 14:14:50 debian-2gb-nbg1-2 kernel: \[9298270.694327\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=79.72.70.205 DST=195.201.40.59 LEN=44 TOS=0x00 PREC=0x00 TTL=53 ID=8624 PROTO=TCP SPT=11319 DPT=88 WINDOW=14127 RES=0x00 SYN URGP=0 |
2020-04-16 21:43:01 |
| 49.233.130.95 | attackspam | (sshd) Failed SSH login from 49.233.130.95 (CN/China/-): 3 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr 16 11:52:19 andromeda sshd[3066]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.233.130.95 user=root Apr 16 11:52:22 andromeda sshd[3066]: Failed password for root from 49.233.130.95 port 37732 ssh2 Apr 16 12:14:13 andromeda sshd[4241]: Invalid user yn from 49.233.130.95 port 55364 |
2020-04-16 22:17:47 |
| 201.226.239.98 | attackspambots | Brute force attempt |
2020-04-16 22:25:36 |
| 220.120.106.254 | attack | Apr 16 15:28:25 markkoudstaal sshd[17066]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.120.106.254 Apr 16 15:28:27 markkoudstaal sshd[17066]: Failed password for invalid user qo from 220.120.106.254 port 38978 ssh2 Apr 16 15:34:05 markkoudstaal sshd[17797]: Failed password for root from 220.120.106.254 port 37414 ssh2 |
2020-04-16 22:20:23 |
| 173.234.48.51 | attackspam | (From eric@talkwithwebvisitor.com) Good day, My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations What for? Part of my job is to check out websites and the work you’ve done with plinkechiropractic.com definitely stands out. It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality. There is, however, a catch… more accurately, a question… So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know? More importantly, how do you make a connection with that person? Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind. Here’s a way to create INSTANT engagement that you may not have known about… Talk With Web Visitor is a software widget that’s works on your site, ready to capture |
2020-04-16 21:44:09 |