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 <<>> 129.144.32.50
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 32082
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;129.144.32.50. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021301 1800 900 604800 86400
;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 14 05:37:20 CST 2025
;; MSG SIZE rcvd: 10650.32.144.129.in-addr.arpa domain name pointer oc-129-144-32-50.compute.oraclecloud.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
50.32.144.129.in-addr.arpa name = oc-129-144-32-50.compute.oraclecloud.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 86.104.34.253 | attack | Jun 11 20:10:34 our-server-hostname sshd[20528]: Invalid user admin from 86.104.34.253 Jun 11 20:10:34 our-server-hostname sshd[20528]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=86.104.34.253 Jun 11 20:10:37 our-server-hostname sshd[20528]: Failed password for invalid user admin from 86.104.34.253 port 39646 ssh2 Jun 11 20:24:02 our-server-hostname sshd[23660]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=86.104.34.253 user=r.r Jun 11 20:24:04 our-server-hostname sshd[23660]: Failed password for r.r from 86.104.34.253 port 55770 ssh2 Jun 11 20:26:23 our-server-hostname sshd[24093]: Invalid user vwalker from 86.104.34.253 Jun 11 20:26:23 our-server-hostname sshd[24093]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=86.104.34.253 Jun 11 20:26:26 our-server-hostname sshd[24093]: Failed password for invalid user vwalker from 86.104.34.253 por........ ------------------------------- |
2020-06-15 04:12:04 |
| 45.141.86.157 | attack | Jun 14 16:46:42 cp sshd[2100]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.141.86.157 Jun 14 16:46:44 cp sshd[2100]: Failed password for invalid user admin from 45.141.86.157 port 6199 ssh2 Jun 14 16:46:49 cp sshd[2175]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.141.86.157 |
2020-06-15 04:03:08 |
| 79.137.77.131 | attackbots | Jun 14 15:56:36 ws19vmsma01 sshd[128802]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.137.77.131 Jun 14 15:56:38 ws19vmsma01 sshd[128802]: Failed password for invalid user guest4 from 79.137.77.131 port 59754 ssh2 ... |
2020-06-15 04:12:35 |
| 49.235.153.220 | attackbotsspam | 2020-06-14T20:09:01.457660abusebot-7.cloudsearch.cf sshd[6405]: Invalid user user from 49.235.153.220 port 45882 2020-06-14T20:09:01.463839abusebot-7.cloudsearch.cf sshd[6405]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.153.220 2020-06-14T20:09:01.457660abusebot-7.cloudsearch.cf sshd[6405]: Invalid user user from 49.235.153.220 port 45882 2020-06-14T20:09:03.562719abusebot-7.cloudsearch.cf sshd[6405]: Failed password for invalid user user from 49.235.153.220 port 45882 ssh2 2020-06-14T20:13:20.011222abusebot-7.cloudsearch.cf sshd[6667]: Invalid user deploy from 49.235.153.220 port 60354 2020-06-14T20:13:20.015767abusebot-7.cloudsearch.cf sshd[6667]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.153.220 2020-06-14T20:13:20.011222abusebot-7.cloudsearch.cf sshd[6667]: Invalid user deploy from 49.235.153.220 port 60354 2020-06-14T20:13:22.004338abusebot-7.cloudsearch.cf sshd[6667]: Failed p ... |
2020-06-15 04:13:43 |
| 72.51.113.171 | attackspam | Unauthorised access (Jun 14) SRC=72.51.113.171 LEN=52 TTL=109 ID=29485 DF TCP DPT=445 WINDOW=8192 SYN |
2020-06-15 04:05:23 |
| 122.146.196.217 | attackspambots | Jun 14 14:44:03 sip sshd[646702]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.146.196.217 Jun 14 14:44:03 sip sshd[646702]: Invalid user abbery from 122.146.196.217 port 51550 Jun 14 14:44:05 sip sshd[646702]: Failed password for invalid user abbery from 122.146.196.217 port 51550 ssh2 ... |
2020-06-15 03:46:55 |
| 138.68.105.194 | attackspambots | Jun 14 21:40:22 meumeu sshd[505322]: Invalid user gok from 138.68.105.194 port 39780 Jun 14 21:40:22 meumeu sshd[505322]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.105.194 Jun 14 21:40:22 meumeu sshd[505322]: Invalid user gok from 138.68.105.194 port 39780 Jun 14 21:40:24 meumeu sshd[505322]: Failed password for invalid user gok from 138.68.105.194 port 39780 ssh2 Jun 14 21:44:25 meumeu sshd[505658]: Invalid user test from 138.68.105.194 port 41000 Jun 14 21:44:25 meumeu sshd[505658]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.105.194 Jun 14 21:44:25 meumeu sshd[505658]: Invalid user test from 138.68.105.194 port 41000 Jun 14 21:44:27 meumeu sshd[505658]: Failed password for invalid user test from 138.68.105.194 port 41000 ssh2 Jun 14 21:48:29 meumeu sshd[506047]: Invalid user erp from 138.68.105.194 port 42220 ... |
2020-06-15 04:06:24 |
| 128.199.72.32 | attackbotsspam | Attacks websites by trying to access known vulnerables of plugins, brute-force of backends or probing of administrative tools |
2020-06-15 03:59:08 |
| 177.45.251.70 | attack | 1592138621 - 06/14/2020 14:43:41 Host: 177.45.251.70/177.45.251.70 Port: 8080 TCP Blocked |
2020-06-15 04:09:14 |
| 148.72.209.9 | attack | 148.72.209.9 - - [14/Jun/2020:15:20:29 +0200] "POST /xmlrpc.php HTTP/1.1" 403 616 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 148.72.209.9 - - [14/Jun/2020:15:31:52 +0200] "POST /xmlrpc.php HTTP/1.1" 403 16471 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" ... |
2020-06-15 04:03:27 |
| 134.209.50.169 | attackbotsspam | Total attacks: 2 |
2020-06-15 03:55:35 |
| 77.210.180.9 | attackspambots | Jun 14 20:13:20 django-0 sshd\[7771\]: Failed password for daemon from 77.210.180.9 port 50042 ssh2Jun 14 20:16:37 django-0 sshd\[8149\]: Invalid user webaccess from 77.210.180.9Jun 14 20:16:39 django-0 sshd\[8149\]: Failed password for invalid user webaccess from 77.210.180.9 port 51472 ssh2 ... |
2020-06-15 04:18:47 |
| 220.132.97.164 | attackspambots | Jun 14 14:43:40 debian-2gb-nbg1-2 kernel: \[14397332.263977\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=220.132.97.164 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=52 ID=58052 PROTO=TCP SPT=40945 DPT=23 WINDOW=9681 RES=0x00 SYN URGP=0 |
2020-06-15 04:08:23 |
| 144.172.91.14 | attackspambots | (sshd) Failed SSH login from 144.172.91.14 (US/United States/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Jun 14 20:59:33 s1 sshd[28315]: Invalid user sk from 144.172.91.14 port 37488 Jun 14 20:59:35 s1 sshd[28315]: Failed password for invalid user sk from 144.172.91.14 port 37488 ssh2 Jun 14 21:12:09 s1 sshd[30032]: Invalid user vox from 144.172.91.14 port 54706 Jun 14 21:12:11 s1 sshd[30032]: Failed password for invalid user vox from 144.172.91.14 port 54706 ssh2 Jun 14 21:15:36 s1 sshd[30164]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.172.91.14 user=root |
2020-06-15 04:16:41 |
| 45.152.33.23 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found drtomalin.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 that can |
2020-06-15 04:25:40 |