城市(city): unknown
省份(region): unknown
国家(country): Norway
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.145.49.192
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 64409
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;139.145.49.192. IN A
;; AUTHORITY SECTION:
. 193 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022010600 1800 900 604800 86400
;; Query time: 69 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 06 18:22:30 CST 2022
;; MSG SIZE rcvd: 107
Host 192.49.145.139.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 192.49.145.139.in-addr.arpa: NXDOMAIN
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 43.229.153.76 | attackbotsspam | 1135. On Jun 22 2020 experienced a Brute Force SSH login attempt -> 17 unique times by 43.229.153.76. |
2020-06-23 07:52:19 |
| 51.91.120.67 | attackspam | SSH Invalid Login |
2020-06-23 07:53:29 |
| 75.75.232.194 | 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 serenityfamilychiropractic.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 |
2020-06-23 07:29:05 |
| 222.186.30.112 | attackspam | Jun 23 01:18:39 ovpn sshd\[16483\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.112 user=root Jun 23 01:18:41 ovpn sshd\[16483\]: Failed password for root from 222.186.30.112 port 55668 ssh2 Jun 23 01:18:48 ovpn sshd\[16529\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.112 user=root Jun 23 01:18:50 ovpn sshd\[16529\]: Failed password for root from 222.186.30.112 port 42830 ssh2 Jun 23 01:18:52 ovpn sshd\[16529\]: Failed password for root from 222.186.30.112 port 42830 ssh2 |
2020-06-23 07:20:36 |
| 218.22.36.135 | attack | Invalid user jake from 218.22.36.135 port 16706 |
2020-06-23 07:48:57 |
| 128.199.128.215 | attackspambots | $f2bV_matches |
2020-06-23 07:43:36 |
| 34.105.41.147 | attack | Jun 23 00:05:52 buvik sshd[8190]: Failed password for root from 34.105.41.147 port 43777 ssh2 Jun 23 00:08:50 buvik sshd[8572]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=34.105.41.147 user=root Jun 23 00:08:52 buvik sshd[8572]: Failed password for root from 34.105.41.147 port 40775 ssh2 ... |
2020-06-23 07:36:59 |
| 211.112.18.37 | attackbotsspam | 980. On Jun 22 2020 experienced a Brute Force SSH login attempt -> 1 unique times by 211.112.18.37. |
2020-06-23 07:31:24 |
| 193.112.171.201 | attackspambots | 20 attempts against mh-ssh on ice |
2020-06-23 07:56:39 |
| 211.24.68.170 | attackbots | SSH Brute Force |
2020-06-23 07:32:58 |
| 139.155.71.154 | attackspam | $f2bV_matches |
2020-06-23 07:28:44 |
| 192.35.168.77 | attackbots | 16992/tcp [2020-06-16/22]2pkt |
2020-06-23 07:38:21 |
| 200.117.104.4 | attackbotsspam | 23/tcp [2020-06-22]1pkt |
2020-06-23 07:24:17 |
| 200.152.70.14 | attack | 445/tcp 445/tcp [2020-06-22]2pkt |
2020-06-23 07:21:07 |
| 108.41.115.54 | attackspambots | 60001/tcp [2020-06-22]1pkt |
2020-06-23 07:18:07 |