| 207.244.252.113 |
attackspambots |
(From annabelle@merchantpay.top) I have a quick question about working with your business. Like most business owners you just want to survive through to 2021. In order for that to happen you need to save every dollar possible right? This is an honest question, would you continue with the high credit card processing fees if there was another way? New laws are on your side. Test this newly released card processing model this October - just send a phone number and we'll call.
$24.99/mo Flat Fee Credit Card Processing (Unlimited)
1) As a small business owner accepting credit/debit, recently passed State Laws are on your side. - Were you aware?
New state regulations now in effect, the law was successfully passed in 46 states - effective since August 2019.
Since that date you shouldn't be paying above 0.75% Credit Card Processing Fees.
2) You're legally able to demand this new option.
Bottom Line: Your processor isn't telling you everything. Why are they hiding the lower fee options?
We repre |
2020-10-03 20:02:21 |
| 111.62.40.36 |
attack |
2020-10-02 UTC: (2x) - tomcat(2x) |
2020-10-03 20:22:26 |
| 160.124.103.55 |
attack |
Unauthorised connection attempt detected at AUO MAIN. System is sshd. Protected by AUO Stack Web Application Firewall (WAF) |
2020-10-03 20:38:18 |
| 167.114.96.156 |
attack |
Oct 3 15:06:51 master sshd[31402]: Failed password for invalid user cert from 167.114.96.156 port 52406 ssh2 |
2020-10-03 20:10:28 |
| 156.96.56.54 |
attackbots |
Port probe, connect, and relay attempt on SMTP:25.
Spammer. IP blocked. |
2020-10-03 20:23:37 |
| 188.159.162.13 |
attackbotsspam |
(pop3d) Failed POP3 login from 188.159.162.13 (IR/Iran/adsl-188-159-162-13.sabanet.ir): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: Oct 3 00:03:01 ir1 dovecot[1917636]: pop3-login: Aborted login (auth failed, 1 attempts in 2 secs): user=, method=PLAIN, rip=188.159.162.13, lip=5.63.12.44, session= |
2020-10-03 20:11:19 |
| 122.51.31.40 |
attackspam |
Invalid user it from 122.51.31.40 port 37358 |
2020-10-03 20:19:15 |
| 64.225.11.24 |
attackbotsspam |
Invalid user admin from 64.225.11.24 port 41874 |
2020-10-03 20:20:26 |
| 40.77.167.237 |
attackbotsspam |
caw-Joomla User : try to access forms... |
2020-10-03 20:37:37 |
| 180.76.118.175 |
attack |
SSH login attempts. |
2020-10-03 20:26:53 |
| 62.4.16.46 |
attackspambots |
Invalid user ralph from 62.4.16.46 port 46574 |
2020-10-03 20:26:31 |
| 134.209.153.36 |
attack |
$f2bV_matches |
2020-10-03 20:39:14 |
| 139.155.91.141 |
attackspam |
20 attempts against mh-ssh on star |
2020-10-03 20:38:54 |
| 120.9.254.171 |
attackspambots |
Port Scan detected!
... |
2020-10-03 20:31:24 |
| 212.70.149.36 |
attackbotsspam |
Oct 3 13:57:48 s1 postfix/submission/smtpd\[6789\]: warning: unknown\[212.70.149.36\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct 3 13:58:05 s1 postfix/submission/smtpd\[6789\]: warning: unknown\[212.70.149.36\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct 3 13:58:24 s1 postfix/submission/smtpd\[6789\]: warning: unknown\[212.70.149.36\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct 3 13:58:44 s1 postfix/submission/smtpd\[6789\]: warning: unknown\[212.70.149.36\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct 3 13:59:10 s1 postfix/submission/smtpd\[6789\]: warning: unknown\[212.70.149.36\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct 3 13:59:29 s1 postfix/submission/smtpd\[6789\]: warning: unknown\[212.70.149.36\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct 3 13:59:49 s1 postfix/submission/smtpd\[6789\]: warning: unknown\[212.70.149.36\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct 3 14:00:15 s1 postfix/submission/smtpd\[13467\]: warning: unknown\[212.70. |
2020-10-03 20:04:39 |