City: unknown
Region: unknown
Country: United States of America (the)
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 68.245.199.135
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1507
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;68.245.199.135. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021701 1800 900 604800 86400
;; Query time: 62 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 05:40:53 CST 2025
;; MSG SIZE rcvd: 107
Host 135.199.245.68.in-addr.arpa not found: 2(SERVFAIL)
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server: 183.60.82.98
Address: 183.60.82.98#53
** server can't find 135.199.245.68.in-addr.arpa: SERVFAIL
| IP | Type | Details | Datetime |
|---|---|---|---|
| 89.233.112.6 | attack |
|
2020-10-04 04:41:15 |
| 190.163.7.156 | attack | C1,WP GET /wp-login.php |
2020-10-04 04:28:21 |
| 170.0.160.165 | attackspam | Oct 2 16:27:05 cumulus sshd[22622]: Did not receive identification string from 170.0.160.165 port 56894 Oct 2 16:27:05 cumulus sshd[22624]: Did not receive identification string from 170.0.160.165 port 56901 Oct 2 16:27:05 cumulus sshd[22623]: Did not receive identification string from 170.0.160.165 port 56900 Oct 2 16:27:06 cumulus sshd[22625]: Did not receive identification string from 170.0.160.165 port 57113 Oct 2 16:27:06 cumulus sshd[22626]: Did not receive identification string from 170.0.160.165 port 57110 Oct 2 16:27:06 cumulus sshd[22627]: Did not receive identification string from 170.0.160.165 port 57122 Oct 2 16:27:06 cumulus sshd[22628]: Did not receive identification string from 170.0.160.165 port 57151 Oct 2 16:27:08 cumulus sshd[22631]: Invalid user guest from 170.0.160.165 port 57170 Oct 2 16:27:08 cumulus sshd[22634]: Invalid user guest from 170.0.160.165 port 57173 Oct 2 16:27:08 cumulus sshd[22632]: Invalid user guest from 170.0.160.165 po........ ------------------------------- |
2020-10-04 04:43:49 |
| 104.131.110.155 | attack | web-1 [ssh] SSH Attack |
2020-10-04 04:44:08 |
| 195.54.167.152 | attackbotsspam | Cowrie Honeypot: 10 unauthorised SSH/Telnet login attempts between 2020-10-03T18:13:48Z and 2020-10-03T20:13:36Z |
2020-10-04 04:43:36 |
| 222.186.42.57 | attackbots | Oct 3 22:36:08 vps639187 sshd\[6862\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.57 user=root Oct 3 22:36:10 vps639187 sshd\[6862\]: Failed password for root from 222.186.42.57 port 25794 ssh2 Oct 3 22:36:13 vps639187 sshd\[6862\]: Failed password for root from 222.186.42.57 port 25794 ssh2 ... |
2020-10-04 04:43:21 |
| 46.105.75.105 | attackbots | $f2bV_matches |
2020-10-04 04:50:32 |
| 222.186.180.130 | attackspambots | Oct 3 22:49:59 theomazars sshd[14242]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.130 user=root Oct 3 22:50:01 theomazars sshd[14242]: Failed password for root from 222.186.180.130 port 14879 ssh2 |
2020-10-04 04:51:49 |
| 122.176.84.178 | attackbots | 1601670773 - 10/02/2020 22:32:53 Host: 122.176.84.178/122.176.84.178 Port: 445 TCP Blocked ... |
2020-10-04 04:17:36 |
| 40.77.167.237 | attackspambots | caw-Joomla User : try to access forms... |
2020-10-04 04:30:39 |
| 180.76.118.175 | attackbotsspam | Connection to SSH Honeypot - Detected by HoneypotDB |
2020-10-04 04:21:46 |
| 165.22.98.186 | attackspambots | Cowrie Honeypot: 3 unauthorised SSH/Telnet login attempts between 2020-10-03T15:04:51Z and 2020-10-03T15:15:01Z |
2020-10-04 04:46:14 |
| 182.74.25.246 | attackbots | Oct 3 21:19:55 gospond sshd[30931]: Invalid user jake from 182.74.25.246 port 54965 ... |
2020-10-04 04:26:57 |
| 154.92.19.140 | attackbots | Brute force SMTP login attempted. ... |
2020-10-04 04:27:47 |
| 1.255.48.197 | 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-04 04:44:26 |