City: unknown
Region: unknown
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 34.142.94.49
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12360
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;34.142.94.49. IN A
;; AUTHORITY SECTION:
. 535 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022021202 1800 900 604800 86400
;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 11:10:50 CST 2022
;; MSG SIZE rcvd: 105
49.94.142.34.in-addr.arpa domain name pointer 49.94.142.34.bc.googleusercontent.com.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
49.94.142.34.in-addr.arpa name = 49.94.142.34.bc.googleusercontent.com.
Authoritative answers can be found from:
IP | Type | Details | Datetime |
---|---|---|---|
66.150.69.237 | attackspam | (From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across performancechiroofga.com a few minutes ago. Looks great… but now what? By that I mean, when someone like me finds your website – either through Search or just bouncing around – what happens next? Do you get a lot of leads from your site, or at least enough to make you happy? Honestly, most business websites fall a bit short when it comes to generating paying customers. Studies show that 70% of a site’s visitors disappear and are gone forever after just a moment. Here’s an idea… How about making it really EASY for every visitor who shows up to get a personal phone call you as soon as they hit your site… 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 signals you the moment they let you know they’re interested – so that you can talk to that lead while they’re literally looking over your site. CLICK HERE http:// |
2020-03-18 14:35:28 |
91.210.224.130 | attack | Mar 18 09:07:11 server sshd\[22513\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.210.224.130 user=root Mar 18 09:07:14 server sshd\[22513\]: Failed password for root from 91.210.224.130 port 60014 ssh2 Mar 18 09:14:10 server sshd\[23963\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.210.224.130 user=root Mar 18 09:14:12 server sshd\[23963\]: Failed password for root from 91.210.224.130 port 39652 ssh2 Mar 18 09:18:27 server sshd\[25044\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.210.224.130 user=root ... |
2020-03-18 14:45:22 |
118.143.232.4 | attackbotsspam | $f2bV_matches |
2020-03-18 14:38:47 |
111.68.46.68 | attack | Mar 18 07:50:43 mout sshd[13405]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.68.46.68 user=root Mar 18 07:50:46 mout sshd[13405]: Failed password for root from 111.68.46.68 port 43262 ssh2 |
2020-03-18 14:54:27 |
209.97.161.46 | attackbotsspam | Invalid user rakesh from 209.97.161.46 port 49080 |
2020-03-18 14:43:44 |
213.55.90.49 | attackbotsspam | Unauthorized connection attempt detected from IP address 213.55.90.49 to port 445 |
2020-03-18 14:45:37 |
211.159.147.35 | attack | Mar 18 09:41:07 hosting sshd[6633]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.159.147.35 user=root Mar 18 09:41:10 hosting sshd[6633]: Failed password for root from 211.159.147.35 port 38394 ssh2 ... |
2020-03-18 14:45:05 |
139.199.89.157 | attackspambots | Brute-force attempt banned |
2020-03-18 15:13:23 |
89.187.178.175 | attack | (From jamison.dukes85@googlemail.com) Want to promote your advertisement on tons of online ad sites monthly? Pay one low monthly fee and get almost endless traffic to your site forever! To find out more check out our site here: http://bit.ly/adpostingrobot |
2020-03-18 15:02:31 |
122.51.191.69 | attack | Mar 18 07:22:00 mout sshd[10623]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.191.69 user=root Mar 18 07:22:02 mout sshd[10623]: Failed password for root from 122.51.191.69 port 38278 ssh2 |
2020-03-18 14:51:53 |
178.128.221.237 | attack | Mar 18 04:52:15 hosting180 sshd[4717]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.221.237 user=root Mar 18 04:52:16 hosting180 sshd[4717]: Failed password for root from 178.128.221.237 port 45774 ssh2 ... |
2020-03-18 14:55:47 |
103.60.214.110 | attackbots | Fail2Ban Ban Triggered (2) |
2020-03-18 15:00:51 |
195.69.222.166 | attack | Mar 17 19:15:54 web1 sshd\[13992\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.69.222.166 user=root Mar 17 19:15:56 web1 sshd\[13992\]: Failed password for root from 195.69.222.166 port 48176 ssh2 Mar 17 19:20:13 web1 sshd\[14469\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.69.222.166 user=root Mar 17 19:20:15 web1 sshd\[14469\]: Failed password for root from 195.69.222.166 port 22553 ssh2 Mar 17 19:24:30 web1 sshd\[14853\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.69.222.166 user=root |
2020-03-18 15:16:11 |
95.238.164.149 | attackspambots | Automatic report - Port Scan Attack |
2020-03-18 15:10:16 |
159.203.63.125 | attack | Mar 18 09:47:37 hosting sshd[7259]: Invalid user yli from 159.203.63.125 port 52951 Mar 18 09:47:37 hosting sshd[7259]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.63.125 Mar 18 09:47:37 hosting sshd[7259]: Invalid user yli from 159.203.63.125 port 52951 Mar 18 09:47:40 hosting sshd[7259]: Failed password for invalid user yli from 159.203.63.125 port 52951 ssh2 Mar 18 09:51:59 hosting sshd[7779]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.63.125 user=root Mar 18 09:52:01 hosting sshd[7779]: Failed password for root from 159.203.63.125 port 40179 ssh2 ... |
2020-03-18 15:15:40 |