城市(city): unknown
省份(region): unknown
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 97.139.106.126
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56856
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;97.139.106.126. IN A
;; AUTHORITY SECTION:
. 371 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019103000 1800 900 604800 86400
;; Query time: 181 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Oct 30 20:47:50 CST 2019
;; MSG SIZE rcvd: 118126.106.139.97.in-addr.arpa domain name pointer 126.sub-97-139-106.myvzw.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
126.106.139.97.in-addr.arpa name = 126.sub-97-139-106.myvzw.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 172.245.58.78 | attackspambots | (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 guarinochiropractic.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-09-05 14:41:04 |
| 203.195.205.202 | attackbotsspam | Sep 5 04:03:53 mavik sshd[8844]: Invalid user postgres from 203.195.205.202 Sep 5 04:03:53 mavik sshd[8844]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.195.205.202 Sep 5 04:03:55 mavik sshd[8844]: Failed password for invalid user postgres from 203.195.205.202 port 43824 ssh2 Sep 5 04:08:39 mavik sshd[9130]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.195.205.202 user=root Sep 5 04:08:42 mavik sshd[9130]: Failed password for root from 203.195.205.202 port 36340 ssh2 ... |
2020-09-05 14:57:47 |
| 191.233.199.68 | attack | Sep 5 02:13:30 django-0 sshd[17417]: Invalid user sakshi from 191.233.199.68 ... |
2020-09-05 14:49:18 |
| 118.24.126.48 | attackbots | Sep 4 18:35:31 ns382633 sshd\[6412\]: Invalid user pz from 118.24.126.48 port 45984 Sep 4 18:35:31 ns382633 sshd\[6412\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.126.48 Sep 4 18:35:33 ns382633 sshd\[6412\]: Failed password for invalid user pz from 118.24.126.48 port 45984 ssh2 Sep 4 18:50:15 ns382633 sshd\[8892\]: Invalid user rsync from 118.24.126.48 port 58296 Sep 4 18:50:15 ns382633 sshd\[8892\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.126.48 |
2020-09-05 14:58:40 |
| 141.98.10.209 | attackbots | $f2bV_matches |
2020-09-05 14:45:43 |
| 143.204.194.67 | attackbots | TCP Port: 443 invalid blocked Listed on zen-spamhaus Client xx.xx.6.14 (164) |
2020-09-05 14:57:27 |
| 185.200.118.53 | attack | 3128/tcp 3389/tcp 1080/tcp... [2020-07-08/09-04]24pkt,4pt.(tcp),1pt.(udp) |
2020-09-05 14:52:15 |
| 198.23.250.38 | attack | (From eric@talkwithwebvisitor.com) Cool website! My name’s Eric, and I just found your site - myvenicechiropractor.com - while surfing the net. You showed up at the top of the search results, so I checked you out. Looks like what you’re doing is pretty cool. But if you don’t mind me asking – after someone like me stumbles across myvenicechiropractor.com, what usually happens? Is your site generating leads for your business? I’m guessing some, but I also bet you’d like more… studies show that 7 out 10 who land on a site wind up leaving without a trace. Not good. Here’s a thought – what if there was an easy way for every visitor to “raise their hand” to get a phone call from you INSTANTLY… the second they hit your site and said, “call me now.” You can – Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number. It lets you know IMMEDIATELY – so that you can talk to that lead while they’re literally look |
2020-09-05 14:22:13 |
| 191.232.193.0 | attack | (sshd) Failed SSH login from 191.232.193.0 (BR/Brazil/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep 4 21:13:01 server2 sshd[7381]: Invalid user status from 191.232.193.0 Sep 4 21:13:01 server2 sshd[7381]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=191.232.193.0 Sep 4 21:13:03 server2 sshd[7381]: Failed password for invalid user status from 191.232.193.0 port 35612 ssh2 Sep 4 21:33:45 server2 sshd[25441]: Invalid user dines from 191.232.193.0 Sep 4 21:33:45 server2 sshd[25441]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=191.232.193.0 |
2020-09-05 14:15:54 |
| 222.186.173.201 | attack | Sep 5 08:20:49 vps639187 sshd\[11029\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.201 user=root Sep 5 08:20:50 vps639187 sshd\[11029\]: Failed password for root from 222.186.173.201 port 34612 ssh2 Sep 5 08:20:54 vps639187 sshd\[11029\]: Failed password for root from 222.186.173.201 port 34612 ssh2 ... |
2020-09-05 14:35:41 |
| 212.129.16.53 | attack | Sep 5 02:22:55 mail sshd\[23920\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.129.16.53 user=root ... |
2020-09-05 14:27:00 |
| 118.25.128.221 | attackbotsspam | Invalid user lorenzo from 118.25.128.221 port 45200 |
2020-09-05 14:17:40 |
| 222.186.169.194 | attack | $f2bV_matches |
2020-09-05 14:18:00 |
| 104.168.99.225 | attackbotsspam | Scanning |
2020-09-05 14:19:58 |
| 54.39.133.91 | attackbotsspam | ET CINS Active Threat Intelligence Poor Reputation IP group 38 - port: 16625 proto: tcp cat: Misc Attackbytes: 60 |
2020-09-05 14:33:25 |