| 59.148.43.97 |
attackspam |
Jul 23 00:44:34 itv-usvr-02 sshd[1361]: Invalid user admin from 59.148.43.97 port 35588
Jul 23 00:44:34 itv-usvr-02 sshd[1361]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.148.43.97
Jul 23 00:44:34 itv-usvr-02 sshd[1361]: Invalid user admin from 59.148.43.97 port 35588
Jul 23 00:44:36 itv-usvr-02 sshd[1361]: Failed password for invalid user admin from 59.148.43.97 port 35588 ssh2
Jul 23 00:44:34 itv-usvr-02 sshd[1361]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.148.43.97
Jul 23 00:44:34 itv-usvr-02 sshd[1361]: Invalid user admin from 59.148.43.97 port 35588
Jul 23 00:44:36 itv-usvr-02 sshd[1361]: Failed password for invalid user admin from 59.148.43.97 port 35588 ssh2
Jul 23 00:44:37 itv-usvr-02 sshd[1361]: Failed password for invalid user admin from 59.148.43.97 port 35588 ssh2 |
2019-07-23 05:13:42 |
| 31.172.134.50 |
attackbots |
Jul 23 00:47:42 our-server-hostname postfix/smtpd[15096]: connect from unknown[31.172.134.50]
Jul x@x
Jul 23 00:48:26 our-server-hostname postfix/smtpd[15096]: 94339A400A7: client=unknown[31.172.134.50]
Jul 23 00:48:27 our-server-hostname postfix/smtpd[19916]: 5B1F0A400AA: client=unknown[127.0.0.1], orig_client=unknown[31.172.134.50]
Jul 23 00:48:27 our-server-hostname amavis[12904]: (12904-08) Passed CLEAN, [31.172.134.50] [31.172.134.50] , mail_id: 8INu6MD6ygSU, Hhostnames: -, size: 4241, queued_as: 5B1F0A400AA, 95 ms
Jul 23 00:48:27 our-server-hostname postfix/smtpd[15096]: disconnect from unknown[31.172.134.50]
Jul 23 01:04:21 our-server-hostname postfix/smtpd[28768]: connect from unknown[31.172.134.50]
Jul x@x
Jul 23 01:05:02 our-server-hostname postfix/smtpd[28768]: 2D566A400AC: client=unknown[31.172.134.50]
Jul 23 01:05:02 our-server-hostname postfix/smtpd[19990]: E5554A400AE: client=unknown[127.0.0.1], orig_client=unknown[31.172.134.50]
Jul 23 01:05:02 our-........
------------------------------- |
2019-07-23 05:32:14 |
| 189.205.46.250 |
attackbotsspam |
Honeypot attack, port: 23, PTR: wimax-cpe-189-205-46-250.cdgen.static.axtel.net. |
2019-07-23 04:54:48 |
| 182.254.135.14 |
attackbotsspam |
Jul 22 16:19:26 icinga sshd[5475]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.254.135.14
Jul 22 16:19:28 icinga sshd[5475]: Failed password for invalid user webmaster from 182.254.135.14 port 58200 ssh2
... |
2019-07-23 05:16:29 |
| 190.13.129.34 |
attackbots |
Invalid user zope from 190.13.129.34 port 50220 |
2019-07-23 05:19:29 |
| 96.9.72.179 |
attackspam |
Honeypot attack, port: 23, PTR: 179.72.9.96.sinet.com.kh. |
2019-07-23 05:08:45 |
| 39.117.148.48 |
attack |
Honeypot attack, port: 23, PTR: PTR record not found |
2019-07-23 05:27:37 |
| 128.199.162.2 |
attack |
SSH Brute-Force reported by Fail2Ban |
2019-07-23 05:12:40 |
| 37.49.224.150 |
attackspam |
firewall-block, port(s): 81/tcp |
2019-07-23 05:34:11 |
| 107.172.100.48 |
attackspam |
(From kat@new.kathreadwrites.net) Hey
I wanted to share a quick ranking case study with you (I'm a copywriter and onpage SEO expert).
Google Loves the RIGHT WORDS in the RIGHT PLACE. I Got It Wrong.
I changed 8 words on a page...and you won't believe what happened.
So I wrote a case study about it.
Read it here: https://kathreadwrites.net/onpage-us/ ?
Put the WRONG WORDS in the WRONG PLACE
and you will not rank. PERIOD.
I hope this case study inspires you to check out your own on-page optimization.
Be Fantastic,
Kat
P.S. To get in touch, please use the contact form on my website instead of emailing me.
Unsubscribe |
2019-07-23 04:55:20 |
| 129.45.5.129 |
attack |
Jul 22 15:02:39 mxgate1 postfix/postscreen[7227]: CONNECT from [129.45.5.129]:18406 to [176.31.12.44]:25
Jul 22 15:02:39 mxgate1 postfix/dnsblog[7233]: addr 129.45.5.129 listed by domain zen.spamhaus.org as 127.0.0.4
Jul 22 15:02:39 mxgate1 postfix/dnsblog[7233]: addr 129.45.5.129 listed by domain zen.spamhaus.org as 127.0.0.11
Jul 22 15:02:39 mxgate1 postfix/dnsblog[7797]: addr 129.45.5.129 listed by domain cbl.abuseat.org as 127.0.0.2
Jul 22 15:02:45 mxgate1 postfix/postscreen[7227]: DNSBL rank 3 for [129.45.5.129]:18406
Jul x@x
Jul 22 15:02:46 mxgate1 postfix/postscreen[7227]: HANGUP after 0.29 from [129.45.5.129]:18406 in tests after SMTP handshake
Jul 22 15:02:46 mxgate1 postfix/postscreen[7227]: DISCONNECT [129.45.5.129]:18406
........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=129.45.5.129 |
2019-07-23 05:17:43 |
| 80.11.44.112 |
attackbotsspam |
Jul 22 15:39:52 dedicated sshd[7622]: Invalid user music from 80.11.44.112 port 50408 |
2019-07-23 05:02:19 |
| 198.20.180.70 |
attack |
(From cath@send.kathreadwrites.net) Hello
I wanted to share a quick ranking case study with you (I'm a copywriter and onpage SEO expert).
Google Loves the RIGHT WORDS in the RIGHT PLACE. I Got It Wrong.
I changed 8 words on a page...and you won't believe what happened.
So I wrote a case study about it.
Read it here: https://kathreadwrites.net/onpage-us/ ?
Put the WRONG WORDS in the WRONG PLACE
and you will not rank. PERIOD.
I hope this case study inspires you to check out your own on-page optimization.
Be Amazing
Cath
P.S. To get in touch, please use the contact form on my website instead of emailing me.
Unsubscribe |
2019-07-23 04:48:26 |
| 77.247.110.219 |
attackspambots |
[21/Jul/2019:00:51:52 -0400] "HEAD /robots.txt HTTP/1.0" Blank UA
[21/Jul/2019:11:00:06 -0400] "HEAD /robots.txt HTTP/1.0" Blank UA
[21/Jul/2019:21:15:47 -0400] "HEAD /robots.txt HTTP/1.0" Blank UA |
2019-07-23 05:29:41 |
| 178.32.141.39 |
attackspambots |
Jul 22 09:44:15 plusreed sshd[25769]: Invalid user pokemon from 178.32.141.39
... |
2019-07-23 05:17:26 |