City: unknown
Region: unknown
Country: Austria
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 195.230.44.94
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 52775
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;195.230.44.94. IN A
;; AUTHORITY SECTION:
. 473 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022010600 1800 900 604800 86400
;; Query time: 57 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 06 22:22:09 CST 2022
;; MSG SIZE rcvd: 106
94.44.230.195.in-addr.arpa domain name pointer 195-230-44-94.adsl.highway.telekom.at.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
94.44.230.195.in-addr.arpa name = 195-230-44-94.adsl.highway.telekom.at.
Authoritative answers can be found from:
| IP | Type | Details | Datetime |
|---|---|---|---|
| 212.81.180.201 | attackbots | $f2bV_matches |
2020-02-26 23:26:22 |
| 177.200.115.65 | attackbots | 1582724254 - 02/26/2020 14:37:34 Host: 177.200.115.65/177.200.115.65 Port: 445 TCP Blocked |
2020-02-26 23:05:25 |
| 212.64.88.97 | attackspambots | $f2bV_matches |
2020-02-26 23:30:23 |
| 213.182.92.37 | attack | $f2bV_matches |
2020-02-26 23:03:59 |
| 157.230.239.167 | attack | DigitalOcean BotNet attack - 10s of requests to non-existent pages - :443/app-ads.txt - typically bursts of 8 requests per second - undefined, XSS attacks node-superagent/4.1.0 |
2020-02-26 23:36:38 |
| 139.59.80.65 | attackspam | Feb 26 22:19:57 webhost01 sshd[19360]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.80.65 Feb 26 22:19:59 webhost01 sshd[19360]: Failed password for invalid user nagios from 139.59.80.65 port 36756 ssh2 ... |
2020-02-26 23:26:57 |
| 212.95.137.151 | attack | DATE:2020-02-26 15:58:45, IP:212.95.137.151, PORT:ssh SSH brute force auth (docker-dc) |
2020-02-26 23:24:57 |
| 212.68.208.120 | attack | $f2bV_matches |
2020-02-26 23:28:56 |
| 45.152.32.21 | attackbots | (From eric@talkwithwebvisitor.com) Cool website! My name’s Eric, and I just found your site - drbrianferris.info - 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 drbrianferris.info, 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 looking over you |
2020-02-26 23:23:29 |
| 213.14.112.92 | attack | $f2bV_matches |
2020-02-26 23:19:24 |
| 23.81.231.161 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found serenityfamilychiropractic.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 s |
2020-02-26 23:13:18 |
| 71.165.90.119 | attack | Feb 26 19:09:27 gw1 sshd[25463]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=71.165.90.119 Feb 26 19:09:28 gw1 sshd[25463]: Failed password for invalid user ackerjapan from 71.165.90.119 port 33766 ssh2 ... |
2020-02-26 22:56:45 |
| 212.64.12.154 | attackspam | $f2bV_matches |
2020-02-26 23:40:08 |
| 213.217.5.23 | attackspambots | Feb 26 03:39:47 hpm sshd\[19453\]: Invalid user direction from 213.217.5.23 Feb 26 03:39:47 hpm sshd\[19453\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.217.5.23 Feb 26 03:39:49 hpm sshd\[19453\]: Failed password for invalid user direction from 213.217.5.23 port 34216 ssh2 Feb 26 03:48:53 hpm sshd\[20186\]: Invalid user userftp from 213.217.5.23 Feb 26 03:48:53 hpm sshd\[20186\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.217.5.23 |
2020-02-26 22:55:58 |
| 212.64.71.225 | attack | Feb 26 15:22:32 rotator sshd\[11170\]: Invalid user laojiang from 212.64.71.225Feb 26 15:22:34 rotator sshd\[11170\]: Failed password for invalid user laojiang from 212.64.71.225 port 40496 ssh2Feb 26 15:26:29 rotator sshd\[11955\]: Invalid user solr from 212.64.71.225Feb 26 15:26:31 rotator sshd\[11955\]: Failed password for invalid user solr from 212.64.71.225 port 51802 ssh2Feb 26 15:30:27 rotator sshd\[12732\]: Invalid user admins from 212.64.71.225Feb 26 15:30:28 rotator sshd\[12732\]: Failed password for invalid user admins from 212.64.71.225 port 34878 ssh2 ... |
2020-02-26 23:30:57 |