City: unknown
Region: unknown
Country: Netherlands (the)
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 145.137.95.53
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 20625
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;145.137.95.53. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021601 1800 900 604800 86400
;; Query time: 239 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 17 13:36:39 CST 2025
;; MSG SIZE rcvd: 10653.95.137.145.in-addr.arpa domain name pointer 145-137-95-53.wlan.hro.nl.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
53.95.137.145.in-addr.arpa name = 145-137-95-53.wlan.hro.nl.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 186.147.129.110 | attackspam | (sshd) Failed SSH login from 186.147.129.110 (CO/Colombia/static-ip-186147129110.cable.net.co): 3 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Mar 16 14:27:20 andromeda sshd[14430]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.147.129.110 user=root Mar 16 14:27:22 andromeda sshd[14430]: Failed password for root from 186.147.129.110 port 58552 ssh2 Mar 16 14:40:22 andromeda sshd[15020]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.147.129.110 user=root |
2020-03-17 03:14:46 |
| 63.245.45.135 | attack | Mar 16 15:36:16 web8 sshd\[17624\]: Invalid user testsftp from 63.245.45.135 Mar 16 15:36:16 web8 sshd\[17624\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=63.245.45.135 Mar 16 15:36:18 web8 sshd\[17624\]: Failed password for invalid user testsftp from 63.245.45.135 port 38415 ssh2 Mar 16 15:39:10 web8 sshd\[19027\]: Invalid user teamspeak from 63.245.45.135 Mar 16 15:39:10 web8 sshd\[19027\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=63.245.45.135 |
2020-03-17 03:18:01 |
| 178.255.169.45 | attack | Chat Spam |
2020-03-17 03:39:43 |
| 23.105.171.117 | attackspam | SpamScore above: 10.0 |
2020-03-17 03:16:35 |
| 178.171.67.92 | attackbotsspam | Chat Spam |
2020-03-17 03:35:03 |
| 23.83.179.123 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found alicebehrchiropractic.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 softwa |
2020-03-17 03:24:40 |
| 1.209.72.151 | attackspam | firewall-block, port(s): 4567/tcp |
2020-03-17 03:40:59 |
| 41.202.79.182 | attackspam | 20/3/16@10:39:22: FAIL: Alarm-Intrusion address from=41.202.79.182 ... |
2020-03-17 03:58:18 |
| 45.143.220.28 | attackbotsspam | Automatic report - Banned IP Access |
2020-03-17 03:25:58 |
| 123.31.45.35 | attackbotsspam | 2020-03-16T19:19:04.384892shield sshd\[6828\]: Invalid user plex from 123.31.45.35 port 50708 2020-03-16T19:19:04.394867shield sshd\[6828\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.31.45.35 2020-03-16T19:19:06.694020shield sshd\[6828\]: Failed password for invalid user plex from 123.31.45.35 port 50708 ssh2 2020-03-16T19:27:07.679980shield sshd\[7473\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.31.45.35 user=root 2020-03-16T19:27:09.282177shield sshd\[7473\]: Failed password for root from 123.31.45.35 port 54300 ssh2 |
2020-03-17 03:55:04 |
| 124.156.174.167 | attackbots | 16.03.2020 14:50:40 SSH access blocked by firewall |
2020-03-17 03:56:51 |
| 222.186.180.6 | attackspambots | Mar 16 20:49:46 v22018076622670303 sshd\[32589\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.6 user=root Mar 16 20:49:47 v22018076622670303 sshd\[32589\]: Failed password for root from 222.186.180.6 port 53612 ssh2 Mar 16 20:49:50 v22018076622670303 sshd\[32589\]: Failed password for root from 222.186.180.6 port 53612 ssh2 ... |
2020-03-17 03:55:53 |
| 14.175.51.107 | attackbotsspam | Attempt to attack host OS, exploiting network vulnerabilities, on 16-03-2020 14:40:10. |
2020-03-17 03:31:25 |
| 23.231.110.145 | attack | (From eric@talkwithwebvisitor.com) Cool website! My name’s Eric, and I just found your site - norburgchiro.com - while surfing the net. You showed up at the top of the search results, so I checked you out. Looks like what you’re doing is pretty cool. But if you don’t mind me asking – after someone like me stumbles across norburgchiro.com, what usually happens? Is your site generating leads for your business? I’m guessing some, but I also bet you’d like more… studies show that 7 out 10 who land on a site wind up leaving without a trace. Not good. Here’s a thought – what if there was an easy way for every visitor to “raise their hand” to get a phone call from you INSTANTLY… the second they hit your site and said, “call me now.” You can – 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 IMMEDIATELY – so that you can talk to that lead while they’re literally looking over your si |
2020-03-17 03:22:54 |
| 222.186.180.17 | attackbotsspam | Mar 16 15:21:14 NPSTNNYC01T sshd[15458]: Failed password for root from 222.186.180.17 port 39534 ssh2 Mar 16 15:21:28 NPSTNNYC01T sshd[15458]: error: maximum authentication attempts exceeded for root from 222.186.180.17 port 39534 ssh2 [preauth] Mar 16 15:21:34 NPSTNNYC01T sshd[15462]: Failed password for root from 222.186.180.17 port 47930 ssh2 ... |
2020-03-17 03:32:08 |