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 <<>> 204.121.169.12
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 11170
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;204.121.169.12. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020302 1800 900 604800 86400
;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 04 06:46:12 CST 2025
;; MSG SIZE rcvd: 107Host 12.169.121.204.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 12.169.121.204.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 94.253.196.33 | attackspam | xmlrpc attack |
2020-06-04 03:20:08 |
| 107.174.248.194 | attackbots | (From eric@talkwithwebvisitor.com) Good day, My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations What for? Part of my job is to check out websites and the work you’ve done with advancedchirosolutions.com definitely stands out. It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality. There is, however, a catch… more accurately, a question… So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know? More importantly, how do you make a connection with that person? Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind. Here’s a way to create INSTANT engagement that you may not have known about… Talk With Web Visitor is a software widget that’s works on your site, ready to capt |
2020-06-04 03:25:54 |
| 142.93.103.141 | attackspam | Jun 3 07:55:58 server1 sshd\[24401\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.103.141 user=root Jun 3 07:56:00 server1 sshd\[24401\]: Failed password for root from 142.93.103.141 port 38182 ssh2 Jun 3 07:59:34 server1 sshd\[25866\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.103.141 user=root Jun 3 07:59:36 server1 sshd\[25866\]: Failed password for root from 142.93.103.141 port 43072 ssh2 Jun 3 08:03:06 server1 sshd\[27075\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.103.141 user=root ... |
2020-06-04 03:23:56 |
| 78.171.62.226 | attackbotsspam | xmlrpc attack |
2020-06-04 03:34:17 |
| 194.26.149.204 | attack | From softreturn@acertenacotacao.live Wed Jun 03 08:47:11 2020 Received: from acertemx4.acertenacotacao.live ([194.26.149.204]:38448) |
2020-06-04 03:41:54 |
| 62.234.145.195 | attackspam | 2020-06-03T18:21:18.207644ns386461 sshd\[10055\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.145.195 user=root 2020-06-03T18:21:20.914680ns386461 sshd\[10055\]: Failed password for root from 62.234.145.195 port 37158 ssh2 2020-06-03T18:36:26.033925ns386461 sshd\[23971\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.145.195 user=root 2020-06-03T18:36:27.392849ns386461 sshd\[23971\]: Failed password for root from 62.234.145.195 port 56678 ssh2 2020-06-03T18:39:20.392051ns386461 sshd\[26801\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.145.195 user=root ... |
2020-06-04 03:47:06 |
| 46.148.20.25 | attackspambots | 2020-06-03T11:37:57.104773shield sshd\[32071\]: Invalid user admin from 46.148.20.25 port 33442 2020-06-03T11:37:57.109056shield sshd\[32071\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.148.20.25 2020-06-03T11:37:58.876279shield sshd\[32071\]: Failed password for invalid user admin from 46.148.20.25 port 33442 ssh2 2020-06-03T11:47:42.866463shield sshd\[998\]: Invalid user admin from 46.148.20.25 port 53470 2020-06-03T11:47:42.870852shield sshd\[998\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.148.20.25 |
2020-06-04 03:24:34 |
| 129.211.85.214 | attack | Jun 3 09:27:22 pixelmemory sshd[92468]: Failed password for root from 129.211.85.214 port 53152 ssh2 Jun 3 09:30:27 pixelmemory sshd[98101]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.85.214 user=root Jun 3 09:30:29 pixelmemory sshd[98101]: Failed password for root from 129.211.85.214 port 56330 ssh2 Jun 3 09:33:27 pixelmemory sshd[100626]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.85.214 user=root Jun 3 09:33:28 pixelmemory sshd[100626]: Failed password for root from 129.211.85.214 port 59506 ssh2 ... |
2020-06-04 03:34:47 |
| 5.173.32.4 | attackbotsspam | xmlrpc attack |
2020-06-04 03:19:00 |
| 217.182.54.227 | attack | Jun 3 18:42:21 [host] sshd[9223]: pam_unix(sshd:a Jun 3 18:42:23 [host] sshd[9223]: Failed password Jun 3 18:47:34 [host] sshd[9346]: pam_unix(sshd:a |
2020-06-04 03:22:38 |
| 218.211.12.26 | attackbots | SMB Server BruteForce Attack |
2020-06-04 03:55:21 |
| 196.52.43.85 | attack | Honeypot hit. |
2020-06-04 03:51:17 |
| 182.61.30.252 | attack |
|
2020-06-04 03:17:19 |
| 87.251.74.141 | attack | Jun 3 21:10:39 debian-2gb-nbg1-2 kernel: \[13470200.952542\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=87.251.74.141 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=36035 PROTO=TCP SPT=55115 DPT=8639 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-06-04 03:28:34 |
| 159.65.136.196 | attackbotsspam | Jun 3 13:47:50 |
2020-06-04 03:17:42 |