城市(city): unknown
省份(region): unknown
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 34.70.47.81
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40148
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;34.70.47.81. IN A
;; AUTHORITY SECTION:
. 187 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2021122501 1800 900 604800 86400
;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Dec 26 06:12:54 CST 2021
;; MSG SIZE rcvd: 10481.47.70.34.in-addr.arpa domain name pointer 81.47.70.34.bc.googleusercontent.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
81.47.70.34.in-addr.arpa name = 81.47.70.34.bc.googleusercontent.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 106.54.253.152 | attack | Aug 27 15:02:00 lnxmail61 sshd[11367]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.253.152 |
2020-08-27 22:29:23 |
| 2.139.209.78 | attack | $f2bV_matches |
2020-08-27 22:09:42 |
| 104.140.184.109 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found mtjulietchiropractic.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well. So here’s my question – what happens AFTER someone lands on your site? Anything? Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever. That means that all the work and effort you put into getting them to show up, goes down the tubes. Why would you want all that good work – and the great site you’ve built – go to waste? Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry. But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket? You can – thanks to revolutionary new softwar |
2020-08-27 22:25:53 |
| 189.101.238.48 | attackspambots | 2020-08-27T16:15:38.016187galaxy.wi.uni-potsdam.de sshd[24292]: Invalid user leo from 189.101.238.48 port 32878 2020-08-27T16:15:38.020748galaxy.wi.uni-potsdam.de sshd[24292]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.101.238.48 2020-08-27T16:15:38.016187galaxy.wi.uni-potsdam.de sshd[24292]: Invalid user leo from 189.101.238.48 port 32878 2020-08-27T16:15:40.241069galaxy.wi.uni-potsdam.de sshd[24292]: Failed password for invalid user leo from 189.101.238.48 port 32878 ssh2 2020-08-27T16:18:23.767856galaxy.wi.uni-potsdam.de sshd[24600]: Invalid user redis from 189.101.238.48 port 41925 2020-08-27T16:18:23.769785galaxy.wi.uni-potsdam.de sshd[24600]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=189.101.238.48 2020-08-27T16:18:23.767856galaxy.wi.uni-potsdam.de sshd[24600]: Invalid user redis from 189.101.238.48 port 41925 2020-08-27T16:18:25.308439galaxy.wi.uni-potsdam.de sshd[24600]: Failed passwo ... |
2020-08-27 22:31:56 |
| 190.144.135.118 | attackspambots | Aug 27 14:01:59 rush sshd[20885]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.144.135.118 Aug 27 14:02:01 rush sshd[20885]: Failed password for invalid user ah from 190.144.135.118 port 47832 ssh2 Aug 27 14:07:31 rush sshd[21019]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.144.135.118 ... |
2020-08-27 22:12:53 |
| 51.75.255.250 | attackbots | $f2bV_matches |
2020-08-27 21:49:52 |
| 218.92.0.199 | attack | 2020-08-27T15:59:04.565059rem.lavrinenko.info sshd[6372]: refused connect from 218.92.0.199 (218.92.0.199) 2020-08-27T16:02:45.132424rem.lavrinenko.info sshd[6392]: refused connect from 218.92.0.199 (218.92.0.199) 2020-08-27T16:04:30.541775rem.lavrinenko.info sshd[6394]: refused connect from 218.92.0.199 (218.92.0.199) 2020-08-27T16:06:14.978836rem.lavrinenko.info sshd[6396]: refused connect from 218.92.0.199 (218.92.0.199) 2020-08-27T16:08:12.408472rem.lavrinenko.info sshd[6397]: refused connect from 218.92.0.199 (218.92.0.199) ... |
2020-08-27 22:16:38 |
| 200.54.242.46 | attackbots | SSH auth scanning - multiple failed logins |
2020-08-27 22:07:12 |
| 51.222.25.197 | attackspambots | $f2bV_matches |
2020-08-27 22:09:02 |
| 113.190.44.39 | attack | 1598533348 - 08/27/2020 15:02:28 Host: 113.190.44.39/113.190.44.39 Port: 445 TCP Blocked ... |
2020-08-27 21:59:11 |
| 155.4.138.99 | attackspambots | Aug 27 12:00:36 host-itldc-nl sshd[28125]: User root from 155.4.138.99 not allowed because not listed in AllowUsers Aug 27 15:01:54 host-itldc-nl sshd[16093]: User root from 155.4.138.99 not allowed because not listed in AllowUsers Aug 27 15:02:06 host-itldc-nl sshd[16966]: User root from 155.4.138.99 not allowed because not listed in AllowUsers ... |
2020-08-27 22:23:29 |
| 93.124.46.232 | attackspambots | Aug 27 03:03:56 host-itldc-nl sshd[47004]: User root from 93.124.46.232 not allowed because not listed in AllowUsers Aug 27 03:04:09 host-itldc-nl sshd[49450]: User root from 93.124.46.232 not allowed because not listed in AllowUsers Aug 27 15:02:20 host-itldc-nl sshd[17641]: User root from 93.124.46.232 not allowed because not listed in AllowUsers ... |
2020-08-27 22:08:20 |
| 64.137.120.60 | attackbotsspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found mtjulietchiropractic.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well. So here’s my question – what happens AFTER someone lands on your site? Anything? Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever. That means that all the work and effort you put into getting them to show up, goes down the tubes. Why would you want all that good work – and the great site you’ve built – go to waste? Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry. But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket? You can – thanks to revolutionary new softwar |
2020-08-27 22:03:32 |
| 140.86.12.31 | attackbotsspam | Aug 27 15:42:34 rotator sshd\[2006\]: Invalid user git from 140.86.12.31Aug 27 15:42:35 rotator sshd\[2006\]: Failed password for invalid user git from 140.86.12.31 port 34261 ssh2Aug 27 15:46:52 rotator sshd\[2813\]: Invalid user g from 140.86.12.31Aug 27 15:46:54 rotator sshd\[2813\]: Failed password for invalid user g from 140.86.12.31 port 9249 ssh2Aug 27 15:51:03 rotator sshd\[3607\]: Invalid user upload from 140.86.12.31Aug 27 15:51:05 rotator sshd\[3607\]: Failed password for invalid user upload from 140.86.12.31 port 40711 ssh2 ... |
2020-08-27 22:00:37 |
| 185.10.68.152 | attack | ft-1848-fussball.de 185.10.68.152 [27/Aug/2020:15:01:58 +0200] "POST /xmlrpc.php HTTP/1.0" 301 505 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Edge/16.16299" ft-1848-fussball.de 185.10.68.152 [27/Aug/2020:15:02:00 +0200] "POST /xmlrpc.php HTTP/1.0" 200 3707 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Edge/16.16299" |
2020-08-27 22:27:47 |