City: unknown
Region: unknown
Country: Japan
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 49.242.41.100
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 11678
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;49.242.41.100. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020901 1800 900 604800 86400
;; Query time: 40 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 11:24:49 CST 2025
;; MSG SIZE rcvd: 106
100.41.242.49.in-addr.arpa domain name pointer 100.41.242.49.ap.yournet.ne.jp.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
100.41.242.49.in-addr.arpa name = 100.41.242.49.ap.yournet.ne.jp.
Authoritative answers can be found from:
| IP | Type | Details | Datetime |
|---|---|---|---|
| 129.45.76.52 | attack | 2020-09-05 11:35:48.851568-0500 localhost smtpd[41784]: NOQUEUE: reject: RCPT from unknown[129.45.76.52]: 554 5.7.1 Service unavailable; Client host [129.45.76.52] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/129.45.76.52; from= |
2020-09-06 15:39:38 |
| 62.234.137.26 | attackbots | Port Scan ... |
2020-09-06 15:35:04 |
| 134.202.64.131 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found staytunedchiropractic.com 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 softwa |
2020-09-06 15:12:16 |
| 171.13.47.75 | attack | Lines containing failures of 171.13.47.75 (max 1000) ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=171.13.47.75 |
2020-09-06 15:12:30 |
| 91.192.46.209 | attack | (ftpd) Failed FTP login from 91.192.46.209 (UA/Ukraine/-): 10 in the last 3600 secs |
2020-09-06 15:28:29 |
| 62.234.78.62 | attackbots | Invalid user ahmed from 62.234.78.62 port 47318 |
2020-09-06 15:28:42 |
| 191.240.39.77 | attackbots | Sep 5 18:47:52 *host* postfix/smtps/smtpd\[6352\]: warning: unknown\[191.240.39.77\]: SASL PLAIN authentication failed: |
2020-09-06 15:46:35 |
| 78.154.217.251 | attack | Aug 31 07:15:38 uapps sshd[25225]: Invalid user admin from 78.154.217.251 port 48203 Aug 31 07:15:40 uapps sshd[25225]: Failed password for invalid user admin from 78.154.217.251 port 48203 ssh2 Aug 31 07:15:41 uapps sshd[25225]: Received disconnect from 78.154.217.251 port 48203:11: Bye Bye [preauth] Aug 31 07:15:41 uapps sshd[25225]: Disconnected from invalid user admin 78.154.217.251 port 48203 [preauth] Aug 31 07:15:42 uapps sshd[25227]: Invalid user admin from 78.154.217.251 port 48273 Aug 31 07:15:44 uapps sshd[25227]: Failed password for invalid user admin from 78.154.217.251 port 48273 ssh2 Aug 31 07:15:46 uapps sshd[25227]: Received disconnect from 78.154.217.251 port 48273:11: Bye Bye [preauth] Aug 31 07:15:46 uapps sshd[25227]: Disconnected from invalid user admin 78.154.217.251 port 48273 [preauth] Aug 31 07:15:47 uapps sshd[25229]: Invalid user admin from 78.154.217.251 port 48435 Aug 31 07:15:49 uapps sshd[25229]: Failed password for invalid user admin fro........ ------------------------------- |
2020-09-06 15:33:52 |
| 147.78.64.77 | attackspam | SP-Scan 3390:3390 detected 2020.09.05 03:17:02 blocked until 2020.10.24 20:19:49 |
2020-09-06 15:41:59 |
| 110.86.183.70 | attackbotsspam | Multiple SSH authentication failures from 110.86.183.70 |
2020-09-06 15:24:13 |
| 222.186.180.8 | attack | Sep 6 08:58:05 minden010 sshd[21624]: Failed password for root from 222.186.180.8 port 49334 ssh2 Sep 6 08:58:08 minden010 sshd[21624]: Failed password for root from 222.186.180.8 port 49334 ssh2 Sep 6 08:58:17 minden010 sshd[21624]: Failed password for root from 222.186.180.8 port 49334 ssh2 Sep 6 08:58:17 minden010 sshd[21624]: error: maximum authentication attempts exceeded for root from 222.186.180.8 port 49334 ssh2 [preauth] ... |
2020-09-06 15:13:18 |
| 117.102.76.182 | attackbotsspam | Sep 5 18:48:36 ns381471 sshd[3761]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.102.76.182 Sep 5 18:48:38 ns381471 sshd[3761]: Failed password for invalid user ubuntu from 117.102.76.182 port 37034 ssh2 |
2020-09-06 15:15:59 |
| 89.248.167.131 | attackspam | 1515/tcp 2087/tcp 1194/udp... [2020-07-06/09-06]263pkt,164pt.(tcp),28pt.(udp) |
2020-09-06 15:42:53 |
| 104.244.75.153 | attack | SSH Login Bruteforce |
2020-09-06 15:18:36 |
| 126.203.36.46 | attackspam | Aug 31 07:14:37 v26 sshd[27039]: Invalid user pi from 126.203.36.46 port 39026 Aug 31 07:14:37 v26 sshd[27037]: Invalid user pi from 126.203.36.46 port 39024 Aug 31 07:14:37 v26 sshd[27037]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=126.203.36.46 Aug 31 07:14:37 v26 sshd[27039]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=126.203.36.46 Aug 31 07:14:39 v26 sshd[27039]: Failed password for invalid user pi from 126.203.36.46 port 39026 ssh2 Aug 31 07:14:39 v26 sshd[27037]: Failed password for invalid user pi from 126.203.36.46 port 39024 ssh2 Aug 31 07:14:39 v26 sshd[27039]: Connection closed by 126.203.36.46 port 39026 [preauth] Aug 31 07:14:39 v26 sshd[27037]: Connection closed by 126.203.36.46 port 39024 [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=126.203.36.46 |
2020-09-06 15:22:21 |