City: unknown
Region: unknown
Country: None
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 114.99.95.237
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46284
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;114.99.95.237. IN A
;; AUTHORITY SECTION:
. 144 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022030400 1800 900 604800 86400
;; Query time: 71 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 05 03:48:28 CST 2022
;; MSG SIZE rcvd: 106Host 237.95.99.114.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 237.95.99.114.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 209.141.61.233 | attackspam | Fail2Ban Ban Triggered |
2020-08-29 06:10:33 |
| 217.30.175.101 | attackbotsspam | 2020-08-29T03:23:38.427159hostname sshd[88392]: Invalid user snd from 217.30.175.101 port 50962 ... |
2020-08-29 06:07:32 |
| 193.35.51.20 | attackbotsspam | (smtpauth) Failed SMTP AUTH login from 193.35.51.20 (RU/Russia/-): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-08-29 02:26:20 login authenticator failed for ([193.35.51.20]) [193.35.51.20]: 535 Incorrect authentication data (set_id=vbnirou-cl@nirouchlor.com) |
2020-08-29 06:05:02 |
| 154.16.203.118 | attackbots | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found drjamieswellnesscenter.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 softw |
2020-08-29 06:08:24 |
| 61.133.232.252 | attackspambots | $f2bV_matches |
2020-08-29 05:54:16 |
| 189.4.2.58 | attackspambots | SSH Invalid Login |
2020-08-29 05:52:07 |
| 181.189.144.206 | attack | Invalid user sysbackup from 181.189.144.206 port 39488 |
2020-08-29 06:03:05 |
| 88.225.212.254 | attack | Automatic report - Port Scan Attack |
2020-08-29 06:22:40 |
| 128.199.128.98 | attackspam | SSH Invalid Login |
2020-08-29 06:09:51 |
| 222.186.180.130 | attackbots | 2020-08-28T21:45:10.578879shield sshd\[392\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.130 user=root 2020-08-28T21:45:12.470240shield sshd\[392\]: Failed password for root from 222.186.180.130 port 54814 ssh2 2020-08-28T21:45:14.575304shield sshd\[392\]: Failed password for root from 222.186.180.130 port 54814 ssh2 2020-08-28T21:45:16.963742shield sshd\[392\]: Failed password for root from 222.186.180.130 port 54814 ssh2 2020-08-28T21:45:20.599034shield sshd\[468\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.130 user=root |
2020-08-29 05:52:40 |
| 14.186.15.141 | attackspam | 2020-08-2822:23:251kBkuC-00013d-KY\<=simone@gedacom.chH=\(localhost\)[122.155.39.250]:50003P=esmtpsaX=TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256CV=noA=dovecot_login:simone@gedacom.chS=1890id=DDD86E3D36E2CC7FA3A6EF57936D6451@gedacom.chT="Thereiscertainlynotonepersonjustlikemyselfonthisplanet"forhanad338@gmail.com2020-08-2822:23:021kBktq-00012R-FC\<=simone@gedacom.chH=\(localhost\)[14.186.15.141]:45356P=esmtpsaX=TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256CV=noA=dovecot_login:simone@gedacom.chS=1896id=C7C274272CF8D665B9BCF54D891F458D@gedacom.chT="Iamactuallyseekingoutapersonwithawonderfulsoul"formartinmunozmota863@gmail.com2020-08-2822:22:431kBktX-00011W-Px\<=simone@gedacom.chH=host-79-7-86-18.business.telecomitalia.it\(localhost\)[79.7.86.18]:50862P=esmtpsaX=TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256CV=noA=dovecot_login:simone@gedacom.chS=1827id=1217A1F2F92D03B06C6920985C0CAFB9@gedacom.chT="Imayofferexactlywhatthemajorityoffemalescannot"forperaltaaaron99@yahoo.com2020-08-2822:23:111kBkty-000130-Gz\<=simone@gedacom.chH |
2020-08-29 06:15:25 |
| 120.203.29.78 | attackspam | web-1 [ssh] SSH Attack |
2020-08-29 05:53:43 |
| 45.176.208.50 | attackspambots | Invalid user friedrich from 45.176.208.50 port 43039 |
2020-08-29 06:01:23 |
| 85.209.0.101 | attack | Aug 23 03:12:49 : SSH login attempts with invalid user |
2020-08-29 06:09:11 |
| 180.100.213.63 | attack | Aug 28 21:58:26 ns382633 sshd\[11467\]: Invalid user ts3 from 180.100.213.63 port 44642 Aug 28 21:58:26 ns382633 sshd\[11467\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.100.213.63 Aug 28 21:58:28 ns382633 sshd\[11467\]: Failed password for invalid user ts3 from 180.100.213.63 port 44642 ssh2 Aug 28 22:23:23 ns382633 sshd\[15951\]: Invalid user sultan from 180.100.213.63 port 58926 Aug 28 22:23:23 ns382633 sshd\[15951\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.100.213.63 |
2020-08-29 06:23:45 |