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 <<>> 199.68.18.4
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1307
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;199.68.18.4. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021800 1800 900 604800 86400
;; Query time: 53 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 21:44:10 CST 2025
;; MSG SIZE rcvd: 104Host 4.18.68.199.in-addr.arpa not found: 2(SERVFAIL);; Got SERVFAIL reply from 183.60.83.19, trying next server
Server: 183.60.82.98
Address: 183.60.82.98#53
** server can't find 4.18.68.199.in-addr.arpa: SERVFAIL| IP | Type | Details | Datetime |
|---|---|---|---|
| 61.177.172.102 | attackspam | 2020-08-15T09:19:16.323566snf-827550 sshd[3960]: Failed password for root from 61.177.172.102 port 21353 ssh2 2020-08-15T09:19:18.844188snf-827550 sshd[3960]: Failed password for root from 61.177.172.102 port 21353 ssh2 2020-08-15T09:19:21.780359snf-827550 sshd[3960]: Failed password for root from 61.177.172.102 port 21353 ssh2 ... |
2020-08-15 14:22:04 |
| 23.95.224.43 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found decubellisfamilychiropractic.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 |
2020-08-15 14:25:42 |
| 91.222.58.28 | attackspambots | Aug 15 01:50:35 mail.srvfarm.net postfix/smtps/smtpd[945232]: warning: unknown[91.222.58.28]: SASL PLAIN authentication failed: Aug 15 01:50:35 mail.srvfarm.net postfix/smtps/smtpd[945232]: lost connection after AUTH from unknown[91.222.58.28] Aug 15 01:55:19 mail.srvfarm.net postfix/smtpd[948188]: warning: unknown[91.222.58.28]: SASL PLAIN authentication failed: Aug 15 01:55:19 mail.srvfarm.net postfix/smtpd[948188]: lost connection after AUTH from unknown[91.222.58.28] Aug 15 01:56:03 mail.srvfarm.net postfix/smtps/smtpd[949850]: warning: unknown[91.222.58.28]: SASL PLAIN authentication failed: |
2020-08-15 13:54:50 |
| 103.58.117.244 | attackspambots | Aug 15 01:51:05 mail.srvfarm.net postfix/smtpd[947514]: warning: unknown[103.58.117.244]: SASL PLAIN authentication failed: Aug 15 01:51:06 mail.srvfarm.net postfix/smtpd[947514]: lost connection after AUTH from unknown[103.58.117.244] Aug 15 01:56:39 mail.srvfarm.net postfix/smtps/smtpd[949098]: warning: unknown[103.58.117.244]: SASL PLAIN authentication failed: Aug 15 01:56:39 mail.srvfarm.net postfix/smtps/smtpd[949098]: lost connection after AUTH from unknown[103.58.117.244] Aug 15 01:59:46 mail.srvfarm.net postfix/smtpd[947515]: warning: unknown[103.58.117.244]: SASL PLAIN authentication failed: |
2020-08-15 13:51:57 |
| 177.54.251.146 | attack | 2020-08-14 18:38 SMTP:25 IP autobanned - 2 attempts a day |
2020-08-15 14:02:34 |
| 111.229.48.141 | attackbots | $f2bV_matches |
2020-08-15 14:25:20 |
| 23.94.5.52 | attackspambots | (From eric@talkwithwebvisitor.com) Hey, my name’s Eric and for just a second, imagine this… - Someone does a search and winds up at hughesfamilychiro.com. - They hang out for a minute to check it out. “I’m interested… but… maybe…” - And then they hit the back button and check out the other search results instead. - Bottom line – you got an eyeball, but nothing else to show for it. - There they go. This isn’t really your fault – it happens a LOT – studies show 7 out of 10 visitors to any site disappear without leaving a trace. But you CAN fix that. Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number. It lets you know right then and there – enabling you to call that lead while they’re literally looking over your site. CLICK HERE http://www.talkwithwebvisitors.com to try out a Live Demo with Talk With Web Visitor now to see exactly how it works. Time is money when it comes to connecting with lea |
2020-08-15 14:31:56 |
| 154.120.242.70 | attackbots | 2020-08-15T06:03:15.512181randservbullet-proofcloud-66.localdomain sshd[15704]: Invalid user abse from 154.120.242.70 port 51148 2020-08-15T06:03:15.516945randservbullet-proofcloud-66.localdomain sshd[15704]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.120.242.70 2020-08-15T06:03:15.512181randservbullet-proofcloud-66.localdomain sshd[15704]: Invalid user abse from 154.120.242.70 port 51148 2020-08-15T06:03:17.418676randservbullet-proofcloud-66.localdomain sshd[15704]: Failed password for invalid user abse from 154.120.242.70 port 51148 ssh2 ... |
2020-08-15 14:29:55 |
| 87.246.7.13 | attackbotsspam | Aug 15 01:30:18 mail.srvfarm.net postfix/smtpd[929438]: warning: unknown[87.246.7.13]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Aug 15 01:30:18 mail.srvfarm.net postfix/smtpd[929438]: lost connection after AUTH from unknown[87.246.7.13] Aug 15 01:30:37 mail.srvfarm.net postfix/smtpd[928329]: warning: unknown[87.246.7.13]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Aug 15 01:30:37 mail.srvfarm.net postfix/smtpd[928329]: lost connection after AUTH from unknown[87.246.7.13] Aug 15 01:30:52 mail.srvfarm.net postfix/smtpd[929429]: warning: unknown[87.246.7.13]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 |
2020-08-15 14:06:02 |
| 213.45.29.13 | attackspambots | Port 22 Scan, PTR: None |
2020-08-15 14:27:22 |
| 94.102.49.159 | attackbots | Aug 15 08:05:44 *hidden* kernel: [UFW BLOCK] IN=eth0 OUT= MAC=00:50:56:3e:4a:cc:28:99:3a:4d:23:91:08:00 SRC=94.102.49.159 DST=173.212.244.83 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=41383 PROTO=TCP SPT=45696 DPT=22092 WINDOW=1024 RES=0x00 SYN URGP=0 Aug 15 08:10:49 *hidden* kernel: [UFW BLOCK] IN=eth0 OUT= MAC=00:50:56:3e:4a:cc:28:99:3a:4d:23:91:08:00 SRC=94.102.49.159 DST=173.212.244.83 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=10752 PROTO=TCP SPT=45696 DPT=23476 WINDOW=1024 RES=0x00 SYN URGP=0 Aug 15 08:16:24 *hidden* kernel: [UFW BLOCK] IN=eth0 OUT= MAC=00:50:56:3e:4a:cc:28:99:3a:4d:23:91:08:00 SRC=94.102.49.159 DST=173.212.244.83 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=52777 PROTO=TCP SPT=45696 DPT=22157 WINDOW=1024 RES=0x00 SYN URGP=0 Aug 15 08:20:06 *hidden* kernel: [UFW BLOCK] IN=eth0 OUT= MAC=00:50:56:3e:4a:cc:28:99:3a:4d:23:91:08:00 SRC=94.102.49.159 DST=173.212.244.83 LEN=40 TOS=0x00 PREC=0x00 TTL=248 ID=6156 PROTO=TCP SPT=45696 DPT=22139 WINDOW=1024 RES=0x00 SYN URGP=0 Aug 15 08:22:54 * ... |
2020-08-15 14:33:48 |
| 193.169.253.27 | attack | Aug 15 08:13:15 srv01 postfix/smtpd\[29611\]: warning: unknown\[193.169.253.27\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Aug 15 08:16:03 srv01 postfix/smtpd\[29358\]: warning: unknown\[193.169.253.27\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Aug 15 08:19:15 srv01 postfix/smtpd\[4056\]: warning: unknown\[193.169.253.27\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Aug 15 08:20:02 srv01 postfix/smtpd\[4056\]: warning: unknown\[193.169.253.27\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Aug 15 08:20:35 srv01 postfix/smtpd\[4949\]: warning: unknown\[193.169.253.27\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-08-15 14:23:56 |
| 141.98.9.161 | attackbotsspam | $f2bV_matches |
2020-08-15 14:23:10 |
| 106.12.69.68 | attackspambots | firewall-block, port(s): 24996/tcp |
2020-08-15 14:19:08 |
| 144.64.3.101 | attackspambots | frenzy |
2020-08-15 14:16:49 |