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 <<>> 139.125.60.190
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40599
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;139.125.60.190. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021800 1800 900 604800 86400
;; Query time: 37 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 22:21:59 CST 2025
;; MSG SIZE rcvd: 107190.60.125.139.in-addr.arpa domain name pointer nothing.attdns.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
190.60.125.139.in-addr.arpa name = nothing.attdns.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 62.234.2.59 | attackspambots | Apr 18 11:24:37 pornomens sshd\[12624\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.2.59 user=root Apr 18 11:24:39 pornomens sshd\[12624\]: Failed password for root from 62.234.2.59 port 59476 ssh2 Apr 18 11:54:34 pornomens sshd\[12962\]: Invalid user lh from 62.234.2.59 port 54400 Apr 18 11:54:34 pornomens sshd\[12962\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.2.59 ... |
2020-04-18 18:33:11 |
| 152.136.157.34 | attackspambots | Invalid user xt from 152.136.157.34 port 59298 |
2020-04-18 18:23:34 |
| 178.128.144.14 | attackspam | 2020-04-18T05:11:57.731969homeassistant sshd[24457]: Invalid user oi from 178.128.144.14 port 54374 2020-04-18T05:11:57.738449homeassistant sshd[24457]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.144.14 ... |
2020-04-18 19:02:38 |
| 199.249.230.80 | attack | CMS (WordPress or Joomla) login attempt. |
2020-04-18 18:30:50 |
| 77.247.109.5 | attackspam | Apr 18 10:50:50 debian-2gb-nbg1-2 kernel: \[9458822.573585\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=77.247.109.5 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=49989 PROTO=TCP SPT=57661 DPT=8888 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-04-18 18:47:53 |
| 111.229.48.141 | attackbotsspam | Apr 18 05:40:38 server sshd[30797]: Failed password for root from 111.229.48.141 port 36152 ssh2 Apr 18 05:47:02 server sshd[31880]: Failed password for invalid user test from 111.229.48.141 port 44968 ssh2 Apr 18 05:50:29 server sshd[32449]: Failed password for invalid user git from 111.229.48.141 port 52858 ssh2 |
2020-04-18 18:48:52 |
| 23.108.47.56 | attack | (From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across medenchiropractic.com a few minutes ago. Looks great… but now what? By that I mean, when someone like me finds your website – either through Search or just bouncing around – what happens next? Do you get a lot of leads from your site, or at least enough to make you happy? Honestly, most business websites fall a bit short when it comes to generating paying customers. Studies show that 70% of a site’s visitors disappear and are gone forever after just a moment. Here’s an idea… How about making it really EASY for every visitor who shows up to get a personal phone call you as soon as they hit your site… 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 signals you the moment they let you know they’re interested – so that you can talk to that lead while they’re literally looking over your site. CLICK HERE http://www |
2020-04-18 18:44:30 |
| 78.30.36.76 | attack | Unauthorized connection attempt detected from IP address 78.30.36.76 to port 81 |
2020-04-18 18:59:29 |
| 180.104.23.125 | attackbotsspam | Email rejected due to spam filtering |
2020-04-18 18:26:23 |
| 185.202.2.210 | attackbotsspam | Brute forcing RDP port 3389 |
2020-04-18 18:58:30 |
| 51.75.208.181 | attackbotsspam | $f2bV_matches |
2020-04-18 19:03:10 |
| 138.197.151.129 | attackbots | web-1 [ssh] SSH Attack |
2020-04-18 18:44:46 |
| 128.199.225.104 | attackspam | Apr 18 12:00:34 pkdns2 sshd\[30822\]: Invalid user ubuntu from 128.199.225.104Apr 18 12:00:36 pkdns2 sshd\[30822\]: Failed password for invalid user ubuntu from 128.199.225.104 port 53370 ssh2Apr 18 12:04:31 pkdns2 sshd\[30932\]: Invalid user admin from 128.199.225.104Apr 18 12:04:32 pkdns2 sshd\[30932\]: Failed password for invalid user admin from 128.199.225.104 port 59460 ssh2Apr 18 12:08:17 pkdns2 sshd\[31102\]: Invalid user py from 128.199.225.104Apr 18 12:08:19 pkdns2 sshd\[31102\]: Failed password for invalid user py from 128.199.225.104 port 37320 ssh2 ... |
2020-04-18 19:07:00 |
| 125.209.110.173 | attack | SSH brutforce |
2020-04-18 19:06:17 |
| 14.116.150.230 | attackspam | 2020-04-18T09:49:59.916338abusebot.cloudsearch.cf sshd[7673]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.116.150.230 user=root 2020-04-18T09:50:01.800367abusebot.cloudsearch.cf sshd[7673]: Failed password for root from 14.116.150.230 port 50252 ssh2 2020-04-18T09:55:21.949447abusebot.cloudsearch.cf sshd[8085]: Invalid user w from 14.116.150.230 port 45338 2020-04-18T09:55:21.956400abusebot.cloudsearch.cf sshd[8085]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.116.150.230 2020-04-18T09:55:21.949447abusebot.cloudsearch.cf sshd[8085]: Invalid user w from 14.116.150.230 port 45338 2020-04-18T09:55:24.377489abusebot.cloudsearch.cf sshd[8085]: Failed password for invalid user w from 14.116.150.230 port 45338 ssh2 2020-04-18T09:57:00.785126abusebot.cloudsearch.cf sshd[8182]: Invalid user admin from 14.116.150.230 port 52814 ... |
2020-04-18 18:38:08 |