City: Kokshetau
Region: Aqmola
Country: Kazakhstan
Internet Service Provider: Kazakhtelecom
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 95.58.92.75
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54596
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;95.58.92.75. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021902 1800 900 604800 86400
;; Query time: 38 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 12:19:20 CST 2025
;; MSG SIZE rcvd: 10475.92.58.95.in-addr.arpa domain name pointer 95.58.92.75.dynamic.telecom.kz.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
75.92.58.95.in-addr.arpa name = 95.58.92.75.dynamic.telecom.kz.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 111.68.103.113 | attackbots | k+ssh-bruteforce |
2020-08-30 06:22:49 |
| 180.121.134.9 | attack | SMTP AUTH on honeypot |
2020-08-30 06:36:50 |
| 23.90.29.149 | attackbots | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found singerfamilychiropractic.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 sof |
2020-08-30 06:11:32 |
| 114.67.104.59 | attack | Aug 30 00:26:54 marvibiene sshd[30037]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.67.104.59 Aug 30 00:26:56 marvibiene sshd[30037]: Failed password for invalid user wetserver from 114.67.104.59 port 47142 ssh2 |
2020-08-30 06:28:36 |
| 82.65.35.189 | attack | $lgm |
2020-08-30 06:15:16 |
| 93.150.110.52 | attack | Port probing on unauthorized port 23 |
2020-08-30 06:26:55 |
| 64.227.0.234 | attack | 64.227.0.234 - - [29/Aug/2020:23:59:51 +0200] "GET /wp-login.php HTTP/1.1" 200 8775 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 64.227.0.234 - - [29/Aug/2020:23:59:53 +0200] "POST /wp-login.php HTTP/1.1" 200 9092 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 64.227.0.234 - - [29/Aug/2020:23:59:54 +0200] "POST /xmlrpc.php HTTP/1.1" 200 427 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" |
2020-08-30 06:29:53 |
| 181.114.211.175 | attackbotsspam | (smtpauth) Failed SMTP AUTH login from 181.114.211.175 (AR/Argentina/host-211-175.adc.net.ar): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-08-30 00:56:04 plain authenticator failed for ([181.114.211.175]) [181.114.211.175]: 535 Incorrect authentication data (set_id=info) |
2020-08-30 06:14:12 |
| 51.210.13.215 | attackbotsspam | SSH Invalid Login |
2020-08-30 06:35:05 |
| 39.108.133.34 | attackspam | Aug 29 22:13:59 ns392434 sshd[4418]: Invalid user huanghao from 39.108.133.34 port 48100 Aug 29 22:13:59 ns392434 sshd[4418]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=39.108.133.34 Aug 29 22:13:59 ns392434 sshd[4418]: Invalid user huanghao from 39.108.133.34 port 48100 Aug 29 22:14:02 ns392434 sshd[4418]: Failed password for invalid user huanghao from 39.108.133.34 port 48100 ssh2 Aug 29 22:22:42 ns392434 sshd[4488]: Invalid user fi from 39.108.133.34 port 52264 Aug 29 22:22:42 ns392434 sshd[4488]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=39.108.133.34 Aug 29 22:22:42 ns392434 sshd[4488]: Invalid user fi from 39.108.133.34 port 52264 Aug 29 22:22:43 ns392434 sshd[4488]: Failed password for invalid user fi from 39.108.133.34 port 52264 ssh2 Aug 29 22:24:30 ns392434 sshd[4518]: Invalid user postgres from 39.108.133.34 port 43172 |
2020-08-30 06:46:57 |
| 118.89.228.58 | attackbotsspam | Aug 29 22:28:48 vps-51d81928 sshd[95573]: Invalid user gold from 118.89.228.58 port 39319 Aug 29 22:28:49 vps-51d81928 sshd[95573]: Failed password for invalid user gold from 118.89.228.58 port 39319 ssh2 Aug 29 22:31:46 vps-51d81928 sshd[95604]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.89.228.58 user=root Aug 29 22:31:49 vps-51d81928 sshd[95604]: Failed password for root from 118.89.228.58 port 9231 ssh2 Aug 29 22:34:52 vps-51d81928 sshd[95643]: Invalid user alex from 118.89.228.58 port 35142 ... |
2020-08-30 06:47:50 |
| 195.54.160.180 | attackbotsspam | Aug 30 00:11:35 theomazars sshd[6739]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.54.160.180 user=root Aug 30 00:11:37 theomazars sshd[6739]: Failed password for root from 195.54.160.180 port 32338 ssh2 |
2020-08-30 06:13:57 |
| 125.26.179.34 | attackspam | Unauthorised access (Aug 29) SRC=125.26.179.34 LEN=52 TTL=52 ID=13156 DF TCP DPT=445 WINDOW=8192 SYN |
2020-08-30 06:45:04 |
| 72.49.197.119 | attackbots | Invalid user admin from 72.49.197.119 |
2020-08-30 06:30:29 |
| 222.186.173.201 | attackbots | Aug 29 22:39:58 scw-6657dc sshd[9764]: Failed password for root from 222.186.173.201 port 33414 ssh2 Aug 29 22:39:58 scw-6657dc sshd[9764]: Failed password for root from 222.186.173.201 port 33414 ssh2 Aug 29 22:40:01 scw-6657dc sshd[9764]: Failed password for root from 222.186.173.201 port 33414 ssh2 ... |
2020-08-30 06:47:37 |