城市(city): unknown
省份(region): unknown
国家(country): Austria
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 185.42.140.62
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30858
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;185.42.140.62. IN A
;; AUTHORITY SECTION:
. 331 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022051900 1800 900 604800 86400
;; Query time: 70 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu May 19 14:36:16 CST 2022
;; MSG SIZE rcvd: 106Host 62.140.42.185.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 62.140.42.185.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 1.71.140.71 | attackbotsspam | Apr 16 14:04:20 Ubuntu-1404-trusty-64-minimal sshd\[31451\]: Invalid user ubuntu from 1.71.140.71 Apr 16 14:04:20 Ubuntu-1404-trusty-64-minimal sshd\[31451\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.71.140.71 Apr 16 14:04:22 Ubuntu-1404-trusty-64-minimal sshd\[31451\]: Failed password for invalid user ubuntu from 1.71.140.71 port 45070 ssh2 Apr 16 14:14:50 Ubuntu-1404-trusty-64-minimal sshd\[6657\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.71.140.71 user=root Apr 16 14:14:52 Ubuntu-1404-trusty-64-minimal sshd\[6657\]: Failed password for root from 1.71.140.71 port 51382 ssh2 |
2020-04-16 21:38:01 |
| 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 |
| 139.59.61.118 | attack | odoo8 ... |
2020-04-16 21:06:17 |
| 67.205.144.244 | attackbotsspam | 2020-04-16T12:43:05.096820shield sshd\[11058\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.205.144.244 user=root 2020-04-16T12:43:07.367078shield sshd\[11058\]: Failed password for root from 67.205.144.244 port 49223 ssh2 2020-04-16T12:47:04.135498shield sshd\[11589\]: Invalid user admin from 67.205.144.244 port 52582 2020-04-16T12:47:04.139236shield sshd\[11589\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=67.205.144.244 2020-04-16T12:47:06.218833shield sshd\[11589\]: Failed password for invalid user admin from 67.205.144.244 port 52582 ssh2 |
2020-04-16 21:44:39 |
| 82.138.61.157 | attackbotsspam | Unauthorized connection attempt from IP address 82.138.61.157 on Port 445(SMB) |
2020-04-16 21:08:35 |
| 91.192.46.209 | attackbotsspam | Apr 16 14:14:43 prod4 vsftpd\[19679\]: \[anonymous\] FAIL LOGIN: Client "91.192.46.209" Apr 16 14:14:44 prod4 vsftpd\[19689\]: \[www\] FAIL LOGIN: Client "91.192.46.209" Apr 16 14:14:45 prod4 vsftpd\[19694\]: \[www\] FAIL LOGIN: Client "91.192.46.209" Apr 16 14:14:47 prod4 vsftpd\[19709\]: \[www\] FAIL LOGIN: Client "91.192.46.209" Apr 16 14:14:48 prod4 vsftpd\[19718\]: \[www\] FAIL LOGIN: Client "91.192.46.209" ... |
2020-04-16 21:45:18 |
| 182.253.68.122 | attackspam | Apr 16 09:11:55 firewall sshd[27072]: Invalid user admin from 182.253.68.122 Apr 16 09:11:57 firewall sshd[27072]: Failed password for invalid user admin from 182.253.68.122 port 43712 ssh2 Apr 16 09:15:19 firewall sshd[27124]: Invalid user dx from 182.253.68.122 ... |
2020-04-16 21:05:39 |
| 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 |
| 139.199.224.172 | attackbots | Apr 16 09:09:58 NPSTNNYC01T sshd[19566]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.224.172 Apr 16 09:10:01 NPSTNNYC01T sshd[19566]: Failed password for invalid user firefart from 139.199.224.172 port 60888 ssh2 Apr 16 09:14:09 NPSTNNYC01T sshd[19882]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.224.172 ... |
2020-04-16 21:37:48 |
| 103.11.117.116 | attackbotsspam | Bruteforce detected by fail2ban |
2020-04-16 21:23:28 |
| 222.186.175.217 | attack | Apr 16 15:05:28 vps sshd[681611]: Failed password for root from 222.186.175.217 port 13010 ssh2 Apr 16 15:05:31 vps sshd[681611]: Failed password for root from 222.186.175.217 port 13010 ssh2 Apr 16 15:05:34 vps sshd[681611]: Failed password for root from 222.186.175.217 port 13010 ssh2 Apr 16 15:05:37 vps sshd[681611]: Failed password for root from 222.186.175.217 port 13010 ssh2 Apr 16 15:05:41 vps sshd[681611]: Failed password for root from 222.186.175.217 port 13010 ssh2 ... |
2020-04-16 21:17:28 |
| 106.12.155.146 | attack | Apr 16 12:15:16 *** sshd[6163]: User root from 106.12.155.146 not allowed because not listed in AllowUsers |
2020-04-16 21:10:44 |
| 152.32.215.160 | attack | Apr 16 14:31:08 ms-srv sshd[56693]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=152.32.215.160 user=root Apr 16 14:31:10 ms-srv sshd[56693]: Failed password for invalid user root from 152.32.215.160 port 55896 ssh2 |
2020-04-16 21:35:00 |
| 180.242.53.112 | attack | Attempt to attack host OS, exploiting network vulnerabilities, on 16-04-2020 13:15:17. |
2020-04-16 21:09:43 |
| 139.155.22.165 | attackspambots | (sshd) Failed SSH login from 139.155.22.165 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr 16 15:04:57 srv sshd[9046]: Invalid user admin from 139.155.22.165 port 38722 Apr 16 15:04:59 srv sshd[9046]: Failed password for invalid user admin from 139.155.22.165 port 38722 ssh2 Apr 16 15:11:10 srv sshd[9263]: Invalid user admin from 139.155.22.165 port 39302 Apr 16 15:11:12 srv sshd[9263]: Failed password for invalid user admin from 139.155.22.165 port 39302 ssh2 Apr 16 15:14:42 srv sshd[9345]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.22.165 user=root |
2020-04-16 21:45:58 |