City: Lithia Springs
Region: Georgia
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.95.209.68
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 41640
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.95.209.68. IN A
;; AUTHORITY SECTION:
. 599 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022032201 1800 900 604800 86400
;; Query time: 25 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 23 03:18:27 CST 2022
;; MSG SIZE rcvd: 10668.209.95.104.in-addr.arpa domain name pointer a104-95-209-68.deploy.static.akamaitechnologies.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
68.209.95.104.in-addr.arpa name = a104-95-209-68.deploy.static.akamaitechnologies.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 23.94.4.205 | attackbots | (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 palmerchiroga.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 any v |
2020-07-12 05:34:01 |
| 113.125.132.53 | attackspam | Failed password for invalid user dongjl from 113.125.132.53 port 58714 ssh2 |
2020-07-12 05:33:40 |
| 176.126.167.167 | attackbotsspam | bruteforce detected |
2020-07-12 05:10:08 |
| 191.234.176.158 | attack | 191.234.176.158 - - [11/Jul/2020:23:02:55 +0200] "GET /wp-login.php HTTP/1.1" 200 1901 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 191.234.176.158 - - [11/Jul/2020:23:02:56 +0200] "POST /wp-login.php HTTP/1.1" 200 2031 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 191.234.176.158 - - [11/Jul/2020:23:02:57 +0200] "GET /wp-login.php HTTP/1.1" 200 1901 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 191.234.176.158 - - [11/Jul/2020:23:02:58 +0200] "POST /wp-login.php HTTP/1.1" 200 2007 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 191.234.176.158 - - [11/Jul/2020:23:02:58 +0200] "GET /wp-login.php HTTP/1.1" 200 1901 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 191.234.176.158 - - [11/Jul/2020:23:02:59 +0200] "POST /wp-login.php HTTP/1.1" 200 2008 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/ ... |
2020-07-12 05:19:15 |
| 46.38.145.248 | attack | Jul 11 23:31:07 srv01 postfix/smtpd\[1946\]: warning: unknown\[46.38.145.248\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:31:25 srv01 postfix/smtpd\[1945\]: warning: unknown\[46.38.145.248\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:32:01 srv01 postfix/smtpd\[1946\]: warning: unknown\[46.38.145.248\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:32:10 srv01 postfix/smtpd\[1945\]: warning: unknown\[46.38.145.248\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:32:14 srv01 postfix/smtpd\[7596\]: warning: unknown\[46.38.145.248\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-07-12 05:36:40 |
| 5.39.86.52 | attack | Jul 11 22:12:01 ns392434 sshd[3413]: Invalid user xjf from 5.39.86.52 port 33052 Jul 11 22:12:01 ns392434 sshd[3413]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.39.86.52 Jul 11 22:12:01 ns392434 sshd[3413]: Invalid user xjf from 5.39.86.52 port 33052 Jul 11 22:12:03 ns392434 sshd[3413]: Failed password for invalid user xjf from 5.39.86.52 port 33052 ssh2 Jul 11 23:09:58 ns392434 sshd[4794]: Invalid user forest from 5.39.86.52 port 34156 Jul 11 23:09:58 ns392434 sshd[4794]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.39.86.52 Jul 11 23:09:58 ns392434 sshd[4794]: Invalid user forest from 5.39.86.52 port 34156 Jul 11 23:10:00 ns392434 sshd[4794]: Failed password for invalid user forest from 5.39.86.52 port 34156 ssh2 Jul 11 23:20:06 ns392434 sshd[4984]: Invalid user cas from 5.39.86.52 port 60896 |
2020-07-12 05:37:22 |
| 46.38.150.193 | attack | Jul 11 23:29:39 relay postfix/smtpd\[26823\]: warning: unknown\[46.38.150.193\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:29:59 relay postfix/smtpd\[24013\]: warning: unknown\[46.38.150.193\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:30:41 relay postfix/smtpd\[29094\]: warning: unknown\[46.38.150.193\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:30:58 relay postfix/smtpd\[26315\]: warning: unknown\[46.38.150.193\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:31:44 relay postfix/smtpd\[22904\]: warning: unknown\[46.38.150.193\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-07-12 05:34:46 |
| 221.125.52.192 | attackspambots | Jul 11 21:58:50 lnxweb61 sshd[19690]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.125.52.192 Jul 11 21:58:52 lnxweb61 sshd[19690]: Failed password for invalid user oracle from 221.125.52.192 port 60602 ssh2 Jul 11 22:07:16 lnxweb61 sshd[28161]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=221.125.52.192 |
2020-07-12 05:23:16 |
| 192.210.176.7 | attackbotsspam | (From eric@talkwithwebvisitor.com) My name’s Eric and I just came across your website - naturalhealthdcs.com - in the search results. Here’s what that means to me… Your SEO’s working. You’re getting eyeballs – mine at least. Your content’s pretty good, wouldn’t change a thing. BUT… Eyeballs don’t pay the bills. CUSTOMERS do. And studies show that 7 out of 10 visitors to a site like naturalhealthdcs.com will drop by, take a gander, and then head for the hills without doing anything else. It’s like they never were even there. You can fix this. You can make it super-simple for them to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket… thanks to Talk With Web Visitor. Talk With Web Visitor is a software widget that sits on your site, ready and waiting to capture any visitor’s Name, Email address and Phone Number. It lets you know immediately – so you can talk to that lead immediately… without delay… BEFORE they hea |
2020-07-12 05:27:25 |
| 112.85.42.181 | attackspambots | Jul 11 23:30:06 santamaria sshd\[4354\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.181 user=root Jul 11 23:30:08 santamaria sshd\[4354\]: Failed password for root from 112.85.42.181 port 47128 ssh2 Jul 11 23:30:24 santamaria sshd\[4356\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.181 user=root ... |
2020-07-12 05:31:16 |
| 112.85.42.187 | attack | 2020-07-11T17:41:44.955310uwu-server sshd[1496060]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.187 user=root 2020-07-11T17:41:46.901748uwu-server sshd[1496060]: Failed password for root from 112.85.42.187 port 54961 ssh2 2020-07-11T17:41:44.955310uwu-server sshd[1496060]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.187 user=root 2020-07-11T17:41:46.901748uwu-server sshd[1496060]: Failed password for root from 112.85.42.187 port 54961 ssh2 2020-07-11T17:41:50.965264uwu-server sshd[1496060]: Failed password for root from 112.85.42.187 port 54961 ssh2 ... |
2020-07-12 05:43:20 |
| 111.231.62.217 | attack | Jul 12 02:32:35 gw1 sshd[22770]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.62.217 Jul 12 02:32:37 gw1 sshd[22770]: Failed password for invalid user biology from 111.231.62.217 port 56688 ssh2 ... |
2020-07-12 05:41:31 |
| 104.153.96.154 | attack | Jul 12 00:21:32 journals sshd\[110811\]: Invalid user demo from 104.153.96.154 Jul 12 00:21:32 journals sshd\[110811\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.153.96.154 Jul 12 00:21:35 journals sshd\[110811\]: Failed password for invalid user demo from 104.153.96.154 port 37242 ssh2 Jul 12 00:28:26 journals sshd\[111403\]: Invalid user shiba from 104.153.96.154 Jul 12 00:28:26 journals sshd\[111403\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.153.96.154 ... |
2020-07-12 05:30:25 |
| 31.130.116.7 | attackspambots | Port probing on unauthorized port 8080 |
2020-07-12 05:42:52 |
| 185.143.72.23 | attackspam | Jul 11 23:29:52 srv01 postfix/smtpd\[2999\]: warning: unknown\[185.143.72.23\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:30:23 srv01 postfix/smtpd\[1946\]: warning: unknown\[185.143.72.23\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:30:53 srv01 postfix/smtpd\[1945\]: warning: unknown\[185.143.72.23\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:31:24 srv01 postfix/smtpd\[1946\]: warning: unknown\[185.143.72.23\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 11 23:31:55 srv01 postfix/smtpd\[7677\]: warning: unknown\[185.143.72.23\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-07-12 05:46:20 |