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 <<>> 69.111.49.77
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 25347
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;69.111.49.77. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012100 1800 900 604800 86400
;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 21 16:08:43 CST 2025
;; MSG SIZE rcvd: 105b'Host 77.49.111.69.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 77.49.111.69.in-addr.arpa: SERVFAIL
| IP | Type | Details | Datetime |
|---|---|---|---|
| 177.66.71.234 | attackspam | Honeypot attack, port: 445, PTR: 177-66-71-234.sapucainet.net.br. |
2020-09-07 23:12:25 |
| 49.235.1.23 | attackbots | Sep 7 15:27:14 [host] sshd[8425]: pam_unix(sshd:a Sep 7 15:27:16 [host] sshd[8425]: Failed password Sep 7 15:31:09 [host] sshd[8563]: pam_unix(sshd:a |
2020-09-07 23:41:14 |
| 61.64.54.207 | attack | Unauthorized connection attempt |
2020-09-07 23:40:38 |
| 222.89.70.216 | attack | ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: tcp cat: Potentially Bad Trafficbytes: 60 |
2020-09-07 23:47:20 |
| 23.108.46.43 | attackbotsspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found drmichaeltwalsh.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 tha |
2020-09-07 23:42:31 |
| 49.69.205.106 | attackbots | Aug 31 16:20:07 nxxxxxxx sshd[13756]: refused connect from 49.69.205.106 (49= .69.205.106) ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=49.69.205.106 |
2020-09-07 23:30:19 |
| 58.215.57.240 | attackbotsspam | Honeypot attack, port: 445, PTR: PTR record not found |
2020-09-07 23:01:15 |
| 103.75.209.51 | attack | Honeypot attack, port: 445, PTR: ip-103-75-209-51.moratelindo.net.id. |
2020-09-07 23:18:02 |
| 157.33.162.187 | attack | Honeypot attack, port: 445, PTR: PTR record not found |
2020-09-07 23:14:42 |
| 49.234.56.138 | attackbots | Sep 5 17:53:56 woof sshd[13292]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.56.138 user=r.r Sep 5 17:53:58 woof sshd[13292]: Failed password for r.r from 49.234.56.138 port 50218 ssh2 Sep 5 17:53:58 woof sshd[13292]: Received disconnect from 49.234.56.138: 11: Bye Bye [preauth] Sep 5 18:02:13 woof sshd[13854]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.56.138 user=r.r Sep 5 18:02:15 woof sshd[13854]: Failed password for r.r from 49.234.56.138 port 35694 ssh2 Sep 5 18:02:16 woof sshd[13854]: Received disconnect from 49.234.56.138: 11: Bye Bye [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=49.234.56.138 |
2020-09-07 23:46:15 |
| 222.186.175.163 | attackbots | 2020-09-07T17:31:04.833123 sshd[2886563]: Unable to negotiate with 222.186.175.163 port 8396: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1 [preauth] 2020-09-07T17:31:04.929882 sshd[2886565]: Unable to negotiate with 222.186.175.163 port 52780: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1 [preauth] 2020-09-07T17:37:51.778206 sshd[2890730]: Unable to negotiate with 222.186.175.163 port 27732: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1 [preauth] |
2020-09-07 23:44:17 |
| 210.55.3.250 | attack | $f2bV_matches |
2020-09-07 23:02:40 |
| 177.124.195.141 | attackspam | bruteforce detected |
2020-09-07 23:22:37 |
| 141.98.81.141 | attack | ET SCAN Potential SSH Scan - port: 22 proto: tcp cat: Attempted Information Leakbytes: 370 |
2020-09-07 23:15:39 |
| 218.249.73.36 | attack | Sep 7 09:22:05 Host-KEWR-E sshd[225832]: User root from 218.249.73.36 not allowed because not listed in AllowUsers ... |
2020-09-07 23:41:40 |