City: unknown
Region: unknown
Country: IANA Special-Purpose Address
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 242.40.92.149
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 6049
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;242.40.92.149. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020600 1800 900 604800 86400
;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 06 21:27:31 CST 2025
;; MSG SIZE rcvd: 106
Host 149.92.40.242.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 149.92.40.242.in-addr.arpa: NXDOMAIN
| IP | Type | Details | Datetime |
|---|---|---|---|
| 139.99.125.230 | attack | SmallBizIT.US 1 packets to tcp(22) |
2020-09-01 18:25:28 |
| 49.88.112.69 | attack | Sep 1 09:52:58 email sshd\[5393\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.69 user=root Sep 1 09:53:00 email sshd\[5393\]: Failed password for root from 49.88.112.69 port 41203 ssh2 Sep 1 09:53:56 email sshd\[5551\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.69 user=root Sep 1 09:53:58 email sshd\[5551\]: Failed password for root from 49.88.112.69 port 12662 ssh2 Sep 1 09:56:20 email sshd\[5951\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.69 user=root ... |
2020-09-01 18:15:39 |
| 181.215.204.180 | attackbots | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found mccombchiropractor.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 software |
2020-09-01 18:33:35 |
| 223.207.227.94 | attack | Port Scan ... |
2020-09-01 18:36:19 |
| 195.39.160.245 | attackspambots | 2020-08-31 22:34:19.382290-0500 localhost smtpd[42821]: NOQUEUE: reject: RCPT from unknown[195.39.160.245]: 554 5.7.1 Service unavailable; Client host [195.39.160.245] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/195.39.160.245 / https://www.spamhaus.org/sbl/query/SBLCSS; from= |
2020-09-01 18:01:13 |
| 185.202.2.68 | attackbots | 1/9/2020 00:30 RDP login failed multiple times. (185.202.2.68) |
2020-09-01 18:12:38 |
| 103.238.68.57 | attackspambots | 20/9/1@01:58:00: FAIL: Alarm-Network address from=103.238.68.57 ... |
2020-09-01 18:24:06 |
| 106.13.136.8 | attack | Failed password for invalid user ubuntu from 106.13.136.8 port 57612 ssh2 |
2020-09-01 18:32:47 |
| 159.89.236.71 | attackspambots |
|
2020-09-01 18:13:51 |
| 180.164.176.50 | attack | Invalid user dante from 180.164.176.50 port 43250 |
2020-09-01 18:37:32 |
| 119.28.101.249 | attackspambots | Brute force attempt |
2020-09-01 18:19:16 |
| 157.55.39.162 | attack | Automatic report - Banned IP Access |
2020-09-01 18:07:45 |
| 202.131.69.18 | attackspambots | Connection to SSH Honeypot - Detected by HoneypotDB |
2020-09-01 18:21:07 |
| 112.85.42.185 | attackbotsspam | Sep 1 10:27:51 localhost sshd[2494513]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.185 user=root Sep 1 10:27:54 localhost sshd[2494513]: Failed password for root from 112.85.42.185 port 20058 ssh2 Sep 1 10:27:51 localhost sshd[2494513]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.185 user=root Sep 1 10:27:54 localhost sshd[2494513]: Failed password for root from 112.85.42.185 port 20058 ssh2 Sep 1 10:27:58 localhost sshd[2494513]: Failed password for root from 112.85.42.185 port 20058 ssh2 ... |
2020-09-01 18:34:36 |
| 213.217.1.38 | attack | firewall-block, port(s): 58259/tcp |
2020-09-01 18:04:35 |