City: Bloomington
Region: Indiana
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 68.50.39.135
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16813
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;68.50.39.135. IN A
;; AUTHORITY SECTION:
. 170 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019092401 1800 900 604800 86400
;; Query time: 579 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Sep 25 02:54:18 CST 2019
;; MSG SIZE rcvd: 116135.39.50.68.in-addr.arpa domain name pointer c-68-50-39-135.hsd1.in.comcast.net.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
135.39.50.68.in-addr.arpa name = c-68-50-39-135.hsd1.in.comcast.net.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 107.174.226.240 | attackspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found neighborhoodchiropractic.net 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 sof |
2020-08-21 04:52:54 |
| 5.188.84.115 | attack | 0,31-01/02 [bc01/m13] PostRequest-Spammer scoring: brussels |
2020-08-21 04:50:06 |
| 206.189.176.134 | attack | Aug 20 13:47:35 dignus sshd[32563]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.176.134 Aug 20 13:47:38 dignus sshd[32563]: Failed password for invalid user oracle from 206.189.176.134 port 41382 ssh2 Aug 20 13:47:43 dignus sshd[32594]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.176.134 user=root Aug 20 13:47:46 dignus sshd[32594]: Failed password for root from 206.189.176.134 port 50686 ssh2 Aug 20 13:47:50 dignus sshd[32602]: Invalid user postgres from 206.189.176.134 port 59890 ... |
2020-08-21 05:02:57 |
| 222.186.175.212 | attack | "Unauthorized connection attempt on SSHD detected" |
2020-08-21 05:17:44 |
| 222.186.15.158 | attackbotsspam | Aug 20 22:40:02 abendstille sshd\[26135\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.15.158 user=root Aug 20 22:40:04 abendstille sshd\[26135\]: Failed password for root from 222.186.15.158 port 11715 ssh2 Aug 20 22:40:20 abendstille sshd\[26541\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.15.158 user=root Aug 20 22:40:22 abendstille sshd\[26541\]: Failed password for root from 222.186.15.158 port 44242 ssh2 Aug 20 22:40:29 abendstille sshd\[26613\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.15.158 user=root ... |
2020-08-21 04:42:48 |
| 117.50.3.142 | attackspam | " " |
2020-08-21 04:40:48 |
| 192.241.234.57 | attack | trying to access non-authorized port |
2020-08-21 04:55:34 |
| 49.235.109.97 | attackbotsspam | Aug 20 22:06:56 ns382633 sshd\[24045\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.109.97 user=root Aug 20 22:06:58 ns382633 sshd\[24045\]: Failed password for root from 49.235.109.97 port 40416 ssh2 Aug 20 22:29:17 ns382633 sshd\[27686\]: Invalid user tech from 49.235.109.97 port 39554 Aug 20 22:29:17 ns382633 sshd\[27686\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.109.97 Aug 20 22:29:19 ns382633 sshd\[27686\]: Failed password for invalid user tech from 49.235.109.97 port 39554 ssh2 |
2020-08-21 04:46:27 |
| 139.198.191.86 | attackspambots | detected by Fail2Ban |
2020-08-21 05:02:07 |
| 211.208.225.110 | attack | Aug 20 22:18:42 Ubuntu-1404-trusty-64-minimal sshd\[14933\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.208.225.110 user=root Aug 20 22:18:44 Ubuntu-1404-trusty-64-minimal sshd\[14933\]: Failed password for root from 211.208.225.110 port 45076 ssh2 Aug 20 22:29:21 Ubuntu-1404-trusty-64-minimal sshd\[23367\]: Invalid user moo from 211.208.225.110 Aug 20 22:29:21 Ubuntu-1404-trusty-64-minimal sshd\[23367\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.208.225.110 Aug 20 22:29:24 Ubuntu-1404-trusty-64-minimal sshd\[23367\]: Failed password for invalid user moo from 211.208.225.110 port 58740 ssh2 |
2020-08-21 04:40:25 |
| 220.249.114.237 | attackspambots | Invalid user winter from 220.249.114.237 port 45020 |
2020-08-21 05:17:08 |
| 23.95.97.213 | attackbotsspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found neighborhoodchiropractic.net 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 sof |
2020-08-21 04:55:15 |
| 149.56.141.170 | attack | Aug 20 21:56:24 rocket sshd[21603]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.56.141.170 Aug 20 21:56:26 rocket sshd[21603]: Failed password for invalid user rk from 149.56.141.170 port 54378 ssh2 ... |
2020-08-21 05:18:02 |
| 103.139.190.18 | attackbotsspam | $f2bV_matches |
2020-08-21 04:46:44 |
| 222.186.31.83 | attack | 2020-08-20T23:36:15.887547lavrinenko.info sshd[30318]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.83 user=root 2020-08-20T23:36:18.391051lavrinenko.info sshd[30318]: Failed password for root from 222.186.31.83 port 32303 ssh2 2020-08-20T23:36:15.887547lavrinenko.info sshd[30318]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.83 user=root 2020-08-20T23:36:18.391051lavrinenko.info sshd[30318]: Failed password for root from 222.186.31.83 port 32303 ssh2 2020-08-20T23:36:22.326404lavrinenko.info sshd[30318]: Failed password for root from 222.186.31.83 port 32303 ssh2 ... |
2020-08-21 04:41:20 |