City: unknown
Region: unknown
Country: None
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 141.138.140.234
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 33654
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;141.138.140.234. IN A
;; AUTHORITY SECTION:
. 295 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022022701 1800 900 604800 86400
;; Query time: 53 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 04:18:58 CST 2022
;; MSG SIZE rcvd: 108
234.140.138.141.in-addr.arpa domain name pointer server05.planck.org.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
234.140.138.141.in-addr.arpa name = server05.planck.org.
Authoritative answers can be found from:
IP | Type | Details | Datetime |
---|---|---|---|
167.99.233.117 | attackbots | Mar 18 01:58:45 firewall sshd[14218]: Invalid user postgres from 167.99.233.117 Mar 18 01:58:47 firewall sshd[14218]: Failed password for invalid user postgres from 167.99.233.117 port 42468 ssh2 Mar 18 02:03:20 firewall sshd[14494]: Invalid user justinbiberx from 167.99.233.117 ... |
2020-03-18 14:13:03 |
45.249.92.66 | attackbotsspam | Mar 18 07:02:46 tuxlinux sshd[57678]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.249.92.66 user=root Mar 18 07:02:48 tuxlinux sshd[57678]: Failed password for root from 45.249.92.66 port 43910 ssh2 Mar 18 07:02:46 tuxlinux sshd[57678]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.249.92.66 user=root Mar 18 07:02:48 tuxlinux sshd[57678]: Failed password for root from 45.249.92.66 port 43910 ssh2 Mar 18 07:11:28 tuxlinux sshd[57968]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.249.92.66 user=root ... |
2020-03-18 14:12:07 |
188.254.0.124 | attackspambots | SSH Authentication Attempts Exceeded |
2020-03-18 14:25:30 |
193.142.146.179 | attackspam | (sshd) Failed SSH login from 193.142.146.179 (NL/Netherlands/-): 5 in the last 3600 secs |
2020-03-18 13:50:40 |
49.233.69.138 | attackspam | Mar 18 09:42:41 gw1 sshd[9887]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.233.69.138 Mar 18 09:42:43 gw1 sshd[9887]: Failed password for invalid user rr from 49.233.69.138 port 5972 ssh2 ... |
2020-03-18 13:56:53 |
112.215.113.11 | attackbotsspam | Mar 18 04:51:07 vps691689 sshd[14488]: Failed password for root from 112.215.113.11 port 42027 ssh2 Mar 18 04:53:43 vps691689 sshd[14566]: Failed password for root from 112.215.113.11 port 53047 ssh2 ... |
2020-03-18 13:44:33 |
120.132.11.186 | attackbots | Invalid user liupeng from 120.132.11.186 port 59526 |
2020-03-18 14:08:17 |
111.175.186.150 | attackspam | Invalid user hubihao from 111.175.186.150 port 25561 |
2020-03-18 13:59:23 |
61.253.138.10 | attackspam | Unauthorised access (Mar 18) SRC=61.253.138.10 LEN=40 TTL=52 ID=53557 TCP DPT=8080 WINDOW=9102 SYN Unauthorised access (Mar 18) SRC=61.253.138.10 LEN=40 TTL=52 ID=29387 TCP DPT=8080 WINDOW=9102 SYN Unauthorised access (Mar 16) SRC=61.253.138.10 LEN=40 PREC=0x20 TTL=52 ID=41603 TCP DPT=8080 WINDOW=9102 SYN |
2020-03-18 13:58:31 |
66.150.69.237 | attackspam | (From eric@talkwithwebvisitor.com) Hey, this is Eric and I ran across performancechiroofga.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:// |
2020-03-18 14:35:28 |
181.177.114.65 | attack | Unauthorized access detected from black listed ip! |
2020-03-18 14:12:28 |
222.79.49.42 | attackspam | Fail2Ban Ban Triggered |
2020-03-18 14:15:29 |
150.223.13.40 | attackbots | Mar 17 19:40:36 tdfoods sshd\[26152\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=150.223.13.40 user=root Mar 17 19:40:38 tdfoods sshd\[26152\]: Failed password for root from 150.223.13.40 port 60398 ssh2 Mar 17 19:42:34 tdfoods sshd\[26334\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=150.223.13.40 user=root Mar 17 19:42:36 tdfoods sshd\[26334\]: Failed password for root from 150.223.13.40 port 43991 ssh2 Mar 17 19:44:34 tdfoods sshd\[26495\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=150.223.13.40 user=root |
2020-03-18 13:52:58 |
177.8.162.234 | attackspam | Unauthorized connection attempt detected from IP address 177.8.162.234 to port 445 |
2020-03-18 14:03:23 |
59.36.143.3 | attackbotsspam | Mar 18 06:19:57 pornomens sshd\[10025\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.36.143.3 user=root Mar 18 06:19:58 pornomens sshd\[10025\]: Failed password for root from 59.36.143.3 port 59129 ssh2 Mar 18 06:28:18 pornomens sshd\[10090\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.36.143.3 user=root ... |
2020-03-18 14:21:56 |