City: unknown
Region: unknown
Country: Canada
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 142.76.214.18
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16587
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;142.76.214.18. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021700 1800 900 604800 86400
;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 17 19:49:36 CST 2025
;; MSG SIZE rcvd: 106Host 18.214.76.142.in-addr.arpa not found: 2(SERVFAIL)
server can't find 142.76.214.18.in-addr.arpa: SERVFAIL| IP | Type | Details | Datetime |
|---|---|---|---|
| 80.244.179.6 | attack | Oct 10 13:01:57 ip-172-31-16-56 sshd\[27760\]: Invalid user admin from 80.244.179.6\ Oct 10 13:01:59 ip-172-31-16-56 sshd\[27760\]: Failed password for invalid user admin from 80.244.179.6 port 47108 ssh2\ Oct 10 13:05:26 ip-172-31-16-56 sshd\[27959\]: Failed password for root from 80.244.179.6 port 41964 ssh2\ Oct 10 13:08:53 ip-172-31-16-56 sshd\[27993\]: Invalid user manager from 80.244.179.6\ Oct 10 13:08:55 ip-172-31-16-56 sshd\[27993\]: Failed password for invalid user manager from 80.244.179.6 port 36806 ssh2\ |
2020-10-10 22:48:09 |
| 167.248.133.74 | attackbotsspam |
|
2020-10-10 23:16:44 |
| 5.39.77.167 | attackspambots | Oct 10 16:13:14 haigwepa sshd[20977]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.39.77.167 Oct 10 16:13:17 haigwepa sshd[20977]: Failed password for invalid user tests from 5.39.77.167 port 42850 ssh2 ... |
2020-10-10 22:52:21 |
| 58.61.145.26 | attackspam | Sep 12 16:13:14 *hidden* postfix/postscreen[29616]: DNSBL rank 3 for [58.61.145.26]:35164 |
2020-10-10 23:14:22 |
| 141.98.9.165 | attackbots | Invalid user user from 141.98.9.165 port 42841 |
2020-10-10 23:00:27 |
| 113.142.72.2 | attack | 20/10/9@16:48:25: FAIL: Alarm-Network address from=113.142.72.2 20/10/9@16:48:25: FAIL: Alarm-Network address from=113.142.72.2 ... |
2020-10-10 23:04:46 |
| 106.13.75.187 | attackspam | 106.13.75.187 (CN/China/-), 6 distributed sshd attacks on account [root] in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_DISTATTACK; Logs: Oct 10 09:09:49 jbs1 sshd[22002]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.75.187 user=root Oct 10 09:09:51 jbs1 sshd[22002]: Failed password for root from 106.13.75.187 port 36282 ssh2 Oct 10 09:07:56 jbs1 sshd[21525]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.6.215 user=root Oct 10 09:07:58 jbs1 sshd[21525]: Failed password for root from 178.62.6.215 port 57196 ssh2 Oct 10 09:13:14 jbs1 sshd[22934]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.129.38 user=root Oct 10 09:13:15 jbs1 sshd[22945]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.53.2.215 user=root IP Addresses Blocked: |
2020-10-10 23:28:23 |
| 209.58.151.124 | attackbotsspam | (From eric@talkwithwebvisitor.com) Cool website! My name’s Eric, and I just found your site - triumphchiropractic.com - while surfing the net. You showed up at the top of the search results, so I checked you out. Looks like what you’re doing is pretty cool. But if you don’t mind me asking – after someone like me stumbles across triumphchiropractic.com, what usually happens? Is your site generating leads for your business? I’m guessing some, but I also bet you’d like more… studies show that 7 out 10 who land on a site wind up leaving without a trace. Not good. Here’s a thought – what if there was an easy way for every visitor to “raise their hand” to get a phone call from you INSTANTLY… the second they hit your site and said, “call me now.” 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 lets you know IMMEDIATELY – so that you can talk to that lead while they’re literally lookin |
2020-10-10 22:53:37 |
| 185.14.186.121 | attackbotsspam | Lines containing failures of 185.14.186.121 Oct 8 07:28:30 nemesis sshd[20848]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.14.186.121 user=r.r Oct 8 07:28:33 nemesis sshd[20848]: Failed password for r.r from 185.14.186.121 port 38302 ssh2 Oct 8 07:28:33 nemesis sshd[20848]: Received disconnect from 185.14.186.121 port 38302:11: Bye Bye [preauth] Oct 8 07:28:33 nemesis sshd[20848]: Disconnected from authenticating user r.r 185.14.186.121 port 38302 [preauth] Oct 8 07:46:01 nemesis sshd[26636]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.14.186.121 user=r.r Oct 8 07:46:03 nemesis sshd[26636]: Failed password for r.r from 185.14.186.121 port 36202 ssh2 Oct 8 07:46:04 nemesis sshd[26636]: Received disconnect from 185.14.186.121 port 36202:11: Bye Bye [preauth] Oct 8 07:46:04 nemesis sshd[26636]: Disconnected from authenticating user r.r 185.14.186.121 port 36202 [preaut........ ------------------------------ |
2020-10-10 23:12:06 |
| 185.90.51.108 | attackspambots | Oct 9 09:13:42 XXX sshd[3683]: Did not receive identification string from 185.90.51.108 Oct 9 09:13:56 XXX sshd[3858]: Received disconnect from 185.90.51.108: 11: Normal Shutdown, Thank you for playing [preauth] Oct 9 09:14:04 XXX sshd[3867]: Received disconnect from 185.90.51.108: 11: Normal Shutdown, Thank you for playing [preauth] Oct 9 09:14:13 XXX sshd[3869]: Received disconnect from 185.90.51.108: 11: Normal Shutdown, Thank you for playing [preauth] Oct 9 09:14:22 XXX sshd[3875]: Received disconnect from 185.90.51.108: 11: Normal Shutdown, Thank you for playing [preauth] Oct 9 09:14:31 XXX sshd[3877]: Received disconnect from 185.90.51.108: 11: Normal Shutdown, Thank you for playing [preauth] Oct 9 09:14:41 XXX sshd[3879]: Received disconnect from 185.90.51.108: 11: Normal Shutdown, Thank you for playing [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=185.90.51.108 |
2020-10-10 23:05:46 |
| 144.91.89.95 | attack | 144.91.89.95 - - [10/Oct/2020:08:39:57 +0200] "POST /wp-login.php HTTP/1.0" 200 4794 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" ... |
2020-10-10 23:06:04 |
| 5.188.206.199 | attackbotsspam | Oct 10 14:33:25 mail postfix/smtpd\[4122\]: warning: unknown\[5.188.206.199\]: SASL PLAIN authentication failed: \ Oct 10 15:43:57 mail postfix/smtpd\[6478\]: warning: unknown\[5.188.206.199\]: SASL PLAIN authentication failed: \ Oct 10 15:44:16 mail postfix/smtpd\[6314\]: warning: unknown\[5.188.206.199\]: SASL PLAIN authentication failed: \ Oct 10 16:32:43 mail postfix/smtpd\[8364\]: warning: unknown\[5.188.206.199\]: SASL PLAIN authentication failed: \ |
2020-10-10 22:52:02 |
| 2.237.31.155 | attackbots | Automatic report - Banned IP Access |
2020-10-10 22:46:02 |
| 141.101.104.125 | attackspam | srv02 DDoS Malware Target(80:http) .. |
2020-10-10 22:59:48 |
| 47.17.177.110 | attack | Oct 10 15:10:22 h2865660 sshd[32411]: Invalid user test from 47.17.177.110 port 45054 Oct 10 15:10:22 h2865660 sshd[32411]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=47.17.177.110 Oct 10 15:10:22 h2865660 sshd[32411]: Invalid user test from 47.17.177.110 port 45054 Oct 10 15:10:23 h2865660 sshd[32411]: Failed password for invalid user test from 47.17.177.110 port 45054 ssh2 Oct 10 15:25:05 h2865660 sshd[497]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=47.17.177.110 user=root Oct 10 15:25:08 h2865660 sshd[497]: Failed password for root from 47.17.177.110 port 56894 ssh2 ... |
2020-10-10 23:22:59 |