City: unknown
Region: unknown
Country: Slovenia
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 89.116.185.16
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 35969
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;89.116.185.16. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020600 1800 900 604800 86400
;; Query time: 33 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 06 21:02:06 CST 2025
;; MSG SIZE rcvd: 106
16.185.116.89.in-addr.arpa domain name pointer 16.185.116.89.static.lrtc.lt.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
16.185.116.89.in-addr.arpa name = 16.185.116.89.static.lrtc.lt.
Authoritative answers can be found from:
| IP | Type | Details | Datetime |
|---|---|---|---|
| 118.150.144.122 | attackbots | Honeypot attack, port: 4567, PTR: n144-h122.150.118.dynamic.da.net.tw. |
2020-04-22 20:48:16 |
| 191.102.156.130 | attackbots | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found millenniumchiro.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-04-22 20:42:48 |
| 37.59.123.166 | attackbotsspam | $f2bV_matches |
2020-04-22 20:56:29 |
| 95.155.36.152 | attackbots | Honeypot attack, port: 445, PTR: adsl-bb36-l152.crnagora.net. |
2020-04-22 20:30:08 |
| 94.177.188.152 | attackbots | Apr 22 14:04:44 163-172-32-151 sshd[12876]: Invalid user postgres from 94.177.188.152 port 38222 ... |
2020-04-22 20:40:47 |
| 183.15.177.0 | attack | Lines containing failures of 183.15.177.0 Apr 22 10:17:22 shared03 sshd[28066]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.15.177.0 user=r.r Apr 22 10:17:24 shared03 sshd[28066]: Failed password for r.r from 183.15.177.0 port 29681 ssh2 Apr 22 10:17:25 shared03 sshd[28066]: Received disconnect from 183.15.177.0 port 29681:11: Bye Bye [preauth] Apr 22 10:17:25 shared03 sshd[28066]: Disconnected from authenticating user r.r 183.15.177.0 port 29681 [preauth] Apr 22 10:53:52 shared03 sshd[10782]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.15.177.0 user=r.r Apr 22 10:53:54 shared03 sshd[10782]: Failed password for r.r from 183.15.177.0 port 62918 ssh2 Apr 22 10:53:54 shared03 sshd[10782]: Received disconnect from 183.15.177.0 port 62918:11: Bye Bye [preauth] Apr 22 10:53:54 shared03 sshd[10782]: Disconnected from authenticating user r.r 183.15.177.0 port 62918 [preauth] Apr 22 ........ ------------------------------ |
2020-04-22 20:38:15 |
| 34.87.83.116 | attackspam | (sshd) Failed SSH login from 34.87.83.116 (US/United States/116.83.87.34.bc.googleusercontent.com): 5 in the last 3600 secs |
2020-04-22 20:28:01 |
| 49.88.157.233 | attack | Honeypot attack, port: 5555, PTR: PTR record not found |
2020-04-22 20:44:10 |
| 111.206.198.92 | attackbots | Bad bot/spoofed identity |
2020-04-22 21:00:10 |
| 111.67.193.92 | attackbots | Apr 22 02:01:26 web1 sshd\[4996\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.67.193.92 user=root Apr 22 02:01:28 web1 sshd\[4996\]: Failed password for root from 111.67.193.92 port 59500 ssh2 Apr 22 02:04:41 web1 sshd\[5369\]: Invalid user ug from 111.67.193.92 Apr 22 02:04:41 web1 sshd\[5369\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.67.193.92 Apr 22 02:04:43 web1 sshd\[5369\]: Failed password for invalid user ug from 111.67.193.92 port 55078 ssh2 |
2020-04-22 20:39:58 |
| 176.114.199.56 | attackspam | 2020-04-22T08:01:00.8598111495-001 sshd[31606]: Invalid user qd from 176.114.199.56 port 41434 2020-04-22T08:01:00.8631781495-001 sshd[31606]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.114.199.56 2020-04-22T08:01:00.8598111495-001 sshd[31606]: Invalid user qd from 176.114.199.56 port 41434 2020-04-22T08:01:02.7832631495-001 sshd[31606]: Failed password for invalid user qd from 176.114.199.56 port 41434 ssh2 2020-04-22T08:05:12.3687021495-001 sshd[31838]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.114.199.56 user=root 2020-04-22T08:05:14.2199191495-001 sshd[31838]: Failed password for root from 176.114.199.56 port 55034 ssh2 ... |
2020-04-22 20:28:28 |
| 51.77.41.246 | attackspambots | Apr 22 14:17:13 meumeu sshd[5162]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.77.41.246 Apr 22 14:17:16 meumeu sshd[5162]: Failed password for invalid user admin from 51.77.41.246 port 47178 ssh2 Apr 22 14:21:28 meumeu sshd[5751]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.77.41.246 ... |
2020-04-22 20:33:32 |
| 78.167.127.117 | attack | Port scan on 2 port(s): 8291 8728 |
2020-04-22 20:53:26 |
| 176.113.115.42 | attackspambots | Apr 22 14:04:55 tuxlinux sshd[11163]: Invalid user test from 176.113.115.42 port 55310 Apr 22 14:04:55 tuxlinux sshd[11163]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.113.115.42 Apr 22 14:04:55 tuxlinux sshd[11163]: Invalid user test from 176.113.115.42 port 55310 Apr 22 14:04:55 tuxlinux sshd[11163]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.113.115.42 ... |
2020-04-22 20:33:08 |
| 209.17.96.226 | attack | Automatic report - Banned IP Access |
2020-04-22 20:37:21 |