City: unknown
Region: unknown
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 149.2.14.103
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 64185
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;149.2.14.103. IN A
;; AUTHORITY SECTION:
. 120 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022102900 1800 900 604800 86400
;; Query time: 65 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Oct 29 15:07:02 CST 2022
;; MSG SIZE rcvd: 105Host 103.14.2.149.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 103.14.2.149.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 105.242.150.10 | attackbots | Automatic report - Banned IP Access |
2020-09-07 15:05:30 |
| 34.126.118.178 | attack | 2020-09-07T06:30:24+0000 Failed SSH Authentication/Brute Force Attack. (Server 6) |
2020-09-07 15:59:53 |
| 119.29.53.107 | attackbots | $f2bV_matches |
2020-09-07 15:13:40 |
| 191.102.156.164 | attackspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found ottochiropractic.net after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well. So here’s my question – what happens AFTER someone lands on your site? Anything? Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever. That means that all the work and effort you put into getting them to show up, goes down the tubes. Why would you want all that good work – and the great site you’ve built – go to waste? Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry. But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket? You can – thanks to revolutionary new software th |
2020-09-07 15:05:48 |
| 128.199.212.15 | attack | Sep 3 09:25:17 ihweb003 sshd[31292]: Connection from 128.199.212.15 port 37106 on 139.59.173.177 port 22 Sep 3 09:25:17 ihweb003 sshd[31292]: Did not receive identification string from 128.199.212.15 port 37106 Sep 3 09:26:48 ihweb003 sshd[31391]: Connection from 128.199.212.15 port 50044 on 139.59.173.177 port 22 Sep 3 09:26:49 ihweb003 sshd[31391]: User r.r from 128.199.212.15 not allowed because none of user's groups are listed in AllowGroups Sep 3 09:26:49 ihweb003 sshd[31391]: Received disconnect from 128.199.212.15 port 50044:11: Normal Shutdown, Thank you for playing [preauth] Sep 3 09:26:49 ihweb003 sshd[31391]: Disconnected from 128.199.212.15 port 50044 [preauth] Sep 3 09:27:44 ihweb003 sshd[31487]: Connection from 128.199.212.15 port 35944 on 139.59.173.177 port 22 Sep 3 09:27:45 ihweb003 sshd[31487]: User r.r from 128.199.212.15 not allowed because none of user's groups are listed in AllowGroups Sep 3 09:27:45 ihweb003 sshd[31487]: Received disconne........ ------------------------------- |
2020-09-07 15:15:29 |
| 104.155.213.9 | attack | Sep 7 10:01:35 root sshd[14929]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.155.213.9 ... |
2020-09-07 16:05:54 |
| 106.12.45.32 | attackbots | ET CINS Active Threat Intelligence Poor Reputation IP group 97 - port: 2167 proto: tcp cat: Misc Attackbytes: 60 |
2020-09-07 15:48:38 |
| 104.131.118.160 | attackbots | Sep 2 01:42:33 bbl sshd[30823]: Did not receive identification string from 104.131.118.160 port 51928 Sep 2 01:43:20 bbl sshd[3577]: Received disconnect from 104.131.118.160 port 49256:11: Normal Shutdown, Thank you for playing [preauth] Sep 2 01:43:20 bbl sshd[3577]: Disconnected from 104.131.118.160 port 49256 [preauth] Sep 2 01:43:43 bbl sshd[6163]: Invalid user ftpuser from 104.131.118.160 port 44062 Sep 2 01:43:43 bbl sshd[6163]: Received disconnect from 104.131.118.160 port 44062:11: Normal Shutdown, Thank you for playing [preauth] Sep 2 01:43:43 bbl sshd[6163]: Disconnected from 104.131.118.160 port 44062 [preauth] Sep 2 01:44:07 bbl sshd[8872]: Invalid user ghostname from 104.131.118.160 port 38862 Sep 2 01:44:07 bbl sshd[8872]: Received disconnect from 104.131.118.160 port 38862:11: Normal Shutdown, Thank you for playing [preauth] Sep 2 01:44:07 bbl sshd[8872]: Disconnected from 104.131.118.160 port 38862 [preauth] Sep 2 01:44:31 bbl sshd[12270]: Inva........ ------------------------------- |
2020-09-07 16:00:31 |
| 94.176.187.142 | attackbotsspam | Unauthorised access (Sep 7) SRC=94.176.187.142 LEN=52 TTL=117 ID=25822 DF TCP DPT=445 WINDOW=8192 SYN |
2020-09-07 15:06:05 |
| 93.107.187.162 | attack | SSH brute force |
2020-09-07 15:06:31 |
| 49.88.112.69 | attackspam | Sep 7 10:37:53 pkdns2 sshd\[5758\]: Failed password for root from 49.88.112.69 port 29960 ssh2Sep 7 10:37:58 pkdns2 sshd\[5758\]: Failed password for root from 49.88.112.69 port 29960 ssh2Sep 7 10:38:00 pkdns2 sshd\[5758\]: Failed password for root from 49.88.112.69 port 29960 ssh2Sep 7 10:45:53 pkdns2 sshd\[6228\]: Failed password for root from 49.88.112.69 port 27178 ssh2Sep 7 10:45:55 pkdns2 sshd\[6228\]: Failed password for root from 49.88.112.69 port 27178 ssh2Sep 7 10:45:59 pkdns2 sshd\[6228\]: Failed password for root from 49.88.112.69 port 27178 ssh2 ... |
2020-09-07 16:07:50 |
| 106.54.221.104 | attackspam | 106.54.221.104 (CN/China/-), 6 distributed sshd attacks on account [root] in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_DISTATTACK; Logs: Sep 6 18:06:53 server4 sshd[12279]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.167.94 user=root Sep 6 18:06:56 server4 sshd[12279]: Failed password for root from 106.13.167.94 port 55670 ssh2 Sep 6 18:12:39 server4 sshd[15381]: Failed password for root from 186.83.66.217 port 55096 ssh2 Sep 6 18:14:37 server4 sshd[16649]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.221.104 user=root Sep 6 18:05:57 server4 sshd[11726]: Failed password for root from 81.182.248.193 port 47394 ssh2 Sep 6 18:12:37 server4 sshd[15381]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.83.66.217 user=root IP Addresses Blocked: 106.13.167.94 (CN/China/-) 186.83.66.217 (CO/Colombia/-) |
2020-09-07 15:50:26 |
| 185.100.87.206 | attack | $f2bV_matches |
2020-09-07 15:07:32 |
| 119.29.89.190 | attack | ... |
2020-09-07 16:02:48 |
| 178.62.37.78 | attackbots | <6 unauthorized SSH connections |
2020-09-07 15:17:35 |