City: unknown
Region: unknown
Country: Germany
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 50.114.162.213
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 5202
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;50.114.162.213. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025022703 1800 900 604800 86400
;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 28 10:13:49 CST 2025
;; MSG SIZE rcvd: 107213.162.114.50.in-addr.arpa domain name pointer 50-114-162-213.ips.acedatacenter.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
213.162.114.50.in-addr.arpa name = 50-114-162-213.ips.acedatacenter.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 104.223.197.3 | attackspam | Too many connections or unauthorized access detected from Arctic banned ip |
2020-06-16 06:16:21 |
| 45.148.10.217 | attackspam | 2020-06-15 22:32:30 auth_plain authenticator failed for (User) [45.148.10.217]: 535 Incorrect authentication data (set_id=louis@csmailer.org,) 2020-06-15 22:32:30 auth_plain authenticator failed for (User) [45.148.10.217]: 535 Incorrect authentication data (set_id=louis@csmailer.org,) 2020-06-15 22:32:30 auth_plain authenticator failed for (User) [45.148.10.217]: 535 Incorrect authentication data (set_id=louis@csmailer.org,) 2020-06-15 22:32:30 auth_plain authenticator failed for (User) [45.148.10.217]: 535 Incorrect authentication data (set_id=louis@csmailer.org,) 2020-06-15 22:32:30 auth_plain authenticator failed for (User) [45.148.10.217]: 535 Incorrect authentication data (set_id=louis@csmailer.org,) ... |
2020-06-16 06:46:52 |
| 89.187.177.134 | attackbots | (From reed.christian@gmail.com) Hi, “According to Gartner’s recent research, data decays on an average of 7 to 9% every month because of various reasons.” Do you have a large database of contacts/companies in-house? If yes, is it up-to-date? We can cleanse, validate and enrich your in-house database with relevant fields that can get you connected with the most premium target profiles of your choice. Please let me know of a convenient time for a quick call to discuss this further. Also, feel free to seek any specific clarifications or assistance that we can help you with. Thank you for your time, wishing you a great day ahead. Best Regards, Diana Baker Marketing Data Specialist Just Validate- https://bit.ly/www-justvalidate-com Email: diana.baker@justvalidate.com |
2020-06-16 06:44:50 |
| 14.162.151.139 | attackspambots | Invalid user adam from 14.162.151.139 port 56932 |
2020-06-16 06:25:20 |
| 103.195.142.154 | attackbotsspam | Invalid user user from 103.195.142.154 port 49460 |
2020-06-16 06:43:41 |
| 209.97.160.105 | attackbots | Brute-force attempt banned |
2020-06-16 06:34:15 |
| 193.56.28.176 | attack | Rude login attack (40 tries in 1d) |
2020-06-16 06:14:50 |
| 106.53.40.211 | attackspam | Jun 16 00:34:37 cosmoit sshd[9424]: Failed password for root from 106.53.40.211 port 36616 ssh2 |
2020-06-16 06:45:58 |
| 216.105.139.66 | attackbotsspam | bruteforce detected |
2020-06-16 06:21:51 |
| 222.186.175.167 | attack | 2020-06-16T00:17:58.816127 sshd[8733]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.167 user=root 2020-06-16T00:18:00.622264 sshd[8733]: Failed password for root from 222.186.175.167 port 49624 ssh2 2020-06-16T00:18:04.618380 sshd[8733]: Failed password for root from 222.186.175.167 port 49624 ssh2 2020-06-16T00:17:58.816127 sshd[8733]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.167 user=root 2020-06-16T00:18:00.622264 sshd[8733]: Failed password for root from 222.186.175.167 port 49624 ssh2 2020-06-16T00:18:04.618380 sshd[8733]: Failed password for root from 222.186.175.167 port 49624 ssh2 ... |
2020-06-16 06:24:10 |
| 140.238.246.49 | attackbots | 252. On Jun 15 2020 experienced a Brute Force SSH login attempt -> 1 unique times by 140.238.246.49. |
2020-06-16 06:41:45 |
| 104.248.48.16 | attackbotsspam | 2020-06-15T22:08:06.595669shield sshd\[2039\]: Invalid user tech from 104.248.48.16 port 47284 2020-06-15T22:08:06.600015shield sshd\[2039\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.48.16 2020-06-15T22:08:09.132939shield sshd\[2039\]: Failed password for invalid user tech from 104.248.48.16 port 47284 ssh2 2020-06-15T22:12:34.040808shield sshd\[3687\]: Invalid user ubuntu from 104.248.48.16 port 47792 2020-06-15T22:12:34.044435shield sshd\[3687\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.48.16 |
2020-06-16 06:42:32 |
| 180.76.181.152 | attackspam | Jun 15 23:10:13 gestao sshd[29778]: Failed password for root from 180.76.181.152 port 43732 ssh2 Jun 15 23:13:42 gestao sshd[29861]: Failed password for root from 180.76.181.152 port 37806 ssh2 ... |
2020-06-16 06:34:33 |
| 120.133.1.16 | attackspam | Jun 16 00:34:35 lnxmail61 sshd[30428]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.133.1.16 Jun 16 00:34:37 lnxmail61 sshd[30428]: Failed password for invalid user debug from 120.133.1.16 port 44044 ssh2 Jun 16 00:38:03 lnxmail61 sshd[30817]: Failed password for root from 120.133.1.16 port 60616 ssh2 |
2020-06-16 06:43:07 |
| 195.12.188.230 | attack | (sshd) Failed SSH login from 195.12.188.230 (LT/Lithuania/-): 5 in the last 3600 secs |
2020-06-16 06:29:22 |