City: unknown
Region: unknown
Country: Germany
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.21.205.196
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 15815
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;139.21.205.196. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021200 1800 900 604800 86400
;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 12 18:39:06 CST 2025
;; MSG SIZE rcvd: 107Host 196.205.21.139.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 196.205.21.139.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 69.229.6.11 | attackspambots | Mar 22 13:00:48 localhost sshd\[7825\]: Invalid user mattelyn from 69.229.6.11 port 38612 Mar 22 13:00:48 localhost sshd\[7825\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.229.6.11 Mar 22 13:00:50 localhost sshd\[7825\]: Failed password for invalid user mattelyn from 69.229.6.11 port 38612 ssh2 ... |
2020-03-23 00:02:13 |
| 37.57.110.181 | attackspam | Unauthorized connection attempt from IP address 37.57.110.181 on Port 445(SMB) |
2020-03-22 23:52:05 |
| 45.152.34.11 | attackspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found middletonchiropractic.net 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-03-22 23:17:37 |
| 132.232.90.20 | attack | Mar 22 14:01:07 mailserver sshd\[23031\]: Invalid user patrycja from 132.232.90.20 ... |
2020-03-22 23:44:48 |
| 197.45.135.9 | attackspam | Unauthorized connection attempt from IP address 197.45.135.9 on Port 445(SMB) |
2020-03-22 23:40:29 |
| 93.88.176.27 | attackspambots | 2020-03-22T13:47:29.230785rocketchat.forhosting.nl sshd[14348]: Invalid user ts4 from 93.88.176.27 port 44988 2020-03-22T13:47:31.031679rocketchat.forhosting.nl sshd[14348]: Failed password for invalid user ts4 from 93.88.176.27 port 44988 ssh2 2020-03-22T14:01:43.806676rocketchat.forhosting.nl sshd[14484]: Invalid user deffer from 93.88.176.27 port 35098 ... |
2020-03-22 23:11:49 |
| 177.53.98.150 | attackbots | Unauthorized connection attempt from IP address 177.53.98.150 on Port 445(SMB) |
2020-03-22 23:43:18 |
| 197.45.189.211 | attackbots | Unauthorized connection attempt from IP address 197.45.189.211 on Port 445(SMB) |
2020-03-22 23:12:45 |
| 14.232.218.241 | attack | Mar 22 14:01:04 andromeda sshd\[28851\]: Invalid user admin from 14.232.218.241 port 59450 Mar 22 14:01:04 andromeda sshd\[28851\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.232.218.241 Mar 22 14:01:06 andromeda sshd\[28851\]: Failed password for invalid user admin from 14.232.218.241 port 59450 ssh2 |
2020-03-22 23:48:34 |
| 176.195.42.178 | attack | Honeypot attack, port: 445, PTR: ip-176-195-42-178.bb.netbynet.ru. |
2020-03-23 00:00:57 |
| 92.50.249.92 | attackspam | Mar 22 13:57:25 silence02 sshd[12946]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.50.249.92 Mar 22 13:57:27 silence02 sshd[12946]: Failed password for invalid user ts3 from 92.50.249.92 port 39504 ssh2 Mar 22 14:01:19 silence02 sshd[13115]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.50.249.92 |
2020-03-22 23:31:21 |
| 114.84.148.162 | attackbotsspam | Unauthorized connection attempt from IP address 114.84.148.162 on Port 445(SMB) |
2020-03-22 23:59:15 |
| 92.50.249.166 | attackbotsspam | 2020-03-22T14:34:36.509267abusebot-3.cloudsearch.cf sshd[30522]: Invalid user deploy from 92.50.249.166 port 46732 2020-03-22T14:34:36.514575abusebot-3.cloudsearch.cf sshd[30522]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.50.249.166 2020-03-22T14:34:36.509267abusebot-3.cloudsearch.cf sshd[30522]: Invalid user deploy from 92.50.249.166 port 46732 2020-03-22T14:34:38.296094abusebot-3.cloudsearch.cf sshd[30522]: Failed password for invalid user deploy from 92.50.249.166 port 46732 ssh2 2020-03-22T14:37:48.894807abusebot-3.cloudsearch.cf sshd[30846]: Invalid user esadmin from 92.50.249.166 port 48972 2020-03-22T14:37:48.902617abusebot-3.cloudsearch.cf sshd[30846]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.50.249.166 2020-03-22T14:37:48.894807abusebot-3.cloudsearch.cf sshd[30846]: Invalid user esadmin from 92.50.249.166 port 48972 2020-03-22T14:37:51.376414abusebot-3.cloudsearch.cf sshd[30846]: ... |
2020-03-22 23:54:16 |
| 180.183.64.121 | attackspam | Unauthorized connection attempt from IP address 180.183.64.121 on Port 445(SMB) |
2020-03-23 00:03:52 |
| 60.52.126.228 | attackbotsspam | Automatic report - Port Scan Attack |
2020-03-22 23:08:16 |