城市(city): unknown
省份(region): unknown
国家(country): Republic of China (ROC)
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 106.104.74.191
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16205
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;106.104.74.191. IN A
;; AUTHORITY SECTION:
. 547 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022021701 1800 900 604800 86400
;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 05:13:18 CST 2022
;; MSG SIZE rcvd: 107
191.74.104.106.in-addr.arpa domain name pointer 106-104-74-191.adsl.static.seed.net.tw.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
191.74.104.106.in-addr.arpa name = 106-104-74-191.adsl.static.seed.net.tw.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 138.128.14.239 | 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:21:33 |
| 185.181.208.225 | attackbots | 6822/tcp [2020-06-22]1pkt |
2020-06-23 07:00:24 |
| 45.148.10.92 | attackbotsspam |
|
2020-06-23 06:55:13 |
| 193.148.70.68 | attack | Jun 22 20:26:29 localhost sshd[126168]: Invalid user diana from 193.148.70.68 port 38166 Jun 22 20:26:29 localhost sshd[126168]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.148.70.68 Jun 22 20:26:29 localhost sshd[126168]: Invalid user diana from 193.148.70.68 port 38166 Jun 22 20:26:31 localhost sshd[126168]: Failed password for invalid user diana from 193.148.70.68 port 38166 ssh2 Jun 22 20:34:56 localhost sshd[127263]: Invalid user student05 from 193.148.70.68 port 38190 ... |
2020-06-23 07:37:59 |
| 62.234.62.206 | attackbotsspam | Jun 22 23:42:02 inter-technics sshd[526]: Invalid user pierre from 62.234.62.206 port 47622 Jun 22 23:42:02 inter-technics sshd[526]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.62.206 Jun 22 23:42:02 inter-technics sshd[526]: Invalid user pierre from 62.234.62.206 port 47622 Jun 22 23:42:04 inter-technics sshd[526]: Failed password for invalid user pierre from 62.234.62.206 port 47622 ssh2 Jun 22 23:51:32 inter-technics sshd[1160]: Invalid user hanshow from 62.234.62.206 port 34028 ... |
2020-06-23 07:22:25 |
| 106.12.172.207 | attack | Jun 22 23:36:33 sip sshd[736574]: Failed password for invalid user minecraft from 106.12.172.207 port 33602 ssh2 Jun 22 23:39:45 sip sshd[736591]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.172.207 user=news Jun 22 23:39:46 sip sshd[736591]: Failed password for news from 106.12.172.207 port 50558 ssh2 ... |
2020-06-23 06:59:25 |
| 180.70.138.57 | attackbots | 54068/udp 54068/udp 54068/udp... [2020-06-22]6pkt,1pt.(udp) |
2020-06-23 07:06:33 |
| 45.142.152.240 | attack | IP 45.142.152.240 attacked honeypot on port: 5001 at 6/22/2020 1:35:25 PM |
2020-06-23 06:56:29 |
| 46.38.145.253 | attackspam | Jun 22 23:47:03 blackbee postfix/smtpd\[1020\]: warning: unknown\[46.38.145.253\]: SASL LOGIN authentication failed: authentication failure Jun 22 23:47:54 blackbee postfix/smtpd\[1020\]: warning: unknown\[46.38.145.253\]: SASL LOGIN authentication failed: authentication failure Jun 22 23:48:41 blackbee postfix/smtpd\[1020\]: warning: unknown\[46.38.145.253\]: SASL LOGIN authentication failed: authentication failure Jun 22 23:49:25 blackbee postfix/smtpd\[1058\]: warning: unknown\[46.38.145.253\]: SASL LOGIN authentication failed: authentication failure Jun 22 23:50:10 blackbee postfix/smtpd\[1058\]: warning: unknown\[46.38.145.253\]: SASL LOGIN authentication failed: authentication failure ... |
2020-06-23 06:59:48 |
| 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 |
| 122.51.18.119 | attackspam | prod11 ... |
2020-06-23 07:12:00 |
| 37.187.7.95 | attack | 2020-06-22T20:30:03.141171shield sshd\[29292\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ks3372588.kimsufi.com user=root 2020-06-22T20:30:05.223011shield sshd\[29292\]: Failed password for root from 37.187.7.95 port 43883 ssh2 2020-06-22T20:35:25.701024shield sshd\[30163\]: Invalid user wuwu from 37.187.7.95 port 44542 2020-06-22T20:35:25.703740shield sshd\[30163\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ks3372588.kimsufi.com 2020-06-22T20:35:26.986950shield sshd\[30163\]: Failed password for invalid user wuwu from 37.187.7.95 port 44542 ssh2 |
2020-06-23 07:00:43 |
| 182.190.4.53 | attackspam | CMS (WordPress or Joomla) login attempt. |
2020-06-23 07:03:43 |
| 211.24.68.170 | attackbots | SSH Brute Force |
2020-06-23 07:32:58 |
| 77.57.204.34 | attackbotsspam | SSH Brute Force |
2020-06-23 07:05:22 |