城市(city): unknown
省份(region): unknown
国家(country): South Africa
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.53.37.145
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 39000
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;139.53.37.145. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012201 1800 900 604800 86400
;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 23 07:53:34 CST 2025
;; MSG SIZE rcvd: 106
Host 145.37.53.139.in-addr.arpa not found: 2(SERVFAIL)
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server: 183.60.82.98
Address: 183.60.82.98#53
** server can't find 145.37.53.139.in-addr.arpa: SERVFAIL
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 104.244.75.153 | attackspambots | (sshd) Failed SSH login from 104.244.75.153 (US/United States/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep 6 17:44:42 amsweb01 sshd[25791]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.244.75.153 user=root Sep 6 17:44:44 amsweb01 sshd[25791]: Failed password for root from 104.244.75.153 port 42074 ssh2 Sep 6 17:44:46 amsweb01 sshd[25791]: Failed password for root from 104.244.75.153 port 42074 ssh2 Sep 6 17:44:48 amsweb01 sshd[25791]: Failed password for root from 104.244.75.153 port 42074 ssh2 Sep 6 17:44:50 amsweb01 sshd[25791]: Failed password for root from 104.244.75.153 port 42074 ssh2 |
2020-09-06 23:55:55 |
| 170.106.33.194 | attack | 29442/tcp 8259/tcp 4611/tcp... [2020-07-15/09-06]11pkt,11pt.(tcp) |
2020-09-07 00:17:53 |
| 117.102.76.182 | attack | Sep 5 18:48:36 ns381471 sshd[3761]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.102.76.182 Sep 5 18:48:38 ns381471 sshd[3761]: Failed password for invalid user ubuntu from 117.102.76.182 port 37034 ssh2 |
2020-09-06 23:53:55 |
| 185.220.101.206 | attack | (sshd) Failed SSH login from 185.220.101.206 (DE/Germany/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep 6 17:50:47 amsweb01 sshd[26838]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.220.101.206 user=root Sep 6 17:50:50 amsweb01 sshd[26838]: Failed password for root from 185.220.101.206 port 16454 ssh2 Sep 6 17:50:51 amsweb01 sshd[26838]: Failed password for root from 185.220.101.206 port 16454 ssh2 Sep 6 17:50:53 amsweb01 sshd[26838]: Failed password for root from 185.220.101.206 port 16454 ssh2 Sep 6 17:50:55 amsweb01 sshd[26838]: Failed password for root from 185.220.101.206 port 16454 ssh2 |
2020-09-06 23:55:14 |
| 112.85.42.89 | attackbotsspam | Sep 6 17:44:48 ns381471 sshd[32248]: Failed password for root from 112.85.42.89 port 18658 ssh2 |
2020-09-06 23:53:39 |
| 73.255.154.127 | attack | 73.255.154.127 - - \[05/Sep/2020:23:40:07 +0300\] "POST /xmlrpc.php HTTP/1.1" 403 5589 "-" "Mozilla/5.0 \(X11\; Linux i686\; rv:2.0.1\) Gecko/20100101 Firefox/4.0.1"73.255.154.127 - - \[05/Sep/2020:23:47:57 +0300\] "POST /xmlrpc.php HTTP/1.1" 403 5589 "-" "Mozilla/5.0 \(X11\; Linux i686\; rv:2.0.1\) Gecko/20100101 Firefox/4.0.1" ... |
2020-09-07 00:04:42 |
| 223.235.185.241 | attack | 2020-09-05 11:36:29.170007-0500 localhost smtpd[41784]: NOQUEUE: reject: RCPT from unknown[223.235.185.241]: 554 5.7.1 Service unavailable; Client host [223.235.185.241] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/223.235.185.241; from= |
2020-09-07 00:15:52 |
| 52.125.140.56 | attackspambots | Unauthorized IMAP connection attempt |
2020-09-07 00:04:56 |
| 134.202.64.131 | attackspambots | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found staytunedchiropractic.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-09-06 23:49:07 |
| 51.77.135.89 | attackspam | Cowrie Honeypot: 3 unauthorised SSH/Telnet login attempts between 2020-09-06T15:18:12Z and 2020-09-06T15:18:14Z |
2020-09-06 23:34:11 |
| 101.78.149.142 | attackbots | Sep 6 08:19:22 sshgateway sshd\[32427\]: Invalid user jira from 101.78.149.142 Sep 6 08:19:22 sshgateway sshd\[32427\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.78.149.142 Sep 6 08:19:24 sshgateway sshd\[32427\]: Failed password for invalid user jira from 101.78.149.142 port 51386 ssh2 Sep 6 08:34:38 sshgateway sshd\[7738\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.78.149.142 user=root Sep 6 08:34:40 sshgateway sshd\[7738\]: Failed password for root from 101.78.149.142 port 49266 ssh2 Sep 6 08:36:19 sshgateway sshd\[8698\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.78.149.142 user=root Sep 6 08:36:21 sshgateway sshd\[8698\]: Failed password for root from 101.78.149.142 port 59244 ssh2 Sep 6 08:41:23 sshgateway sshd\[11681\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.78.149.142 user=root S |
2020-09-06 23:48:38 |
| 103.63.215.38 | attack |
|
2020-09-06 23:46:14 |
| 91.106.38.182 | attackspambots | 2020-09-05 11:37:41.137096-0500 localhost smtpd[41784]: NOQUEUE: reject: RCPT from unknown[91.106.38.182]: 554 5.7.1 Service unavailable; Client host [91.106.38.182] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/91.106.38.182; from= |
2020-09-07 00:17:10 |
| 124.158.12.202 | attack | 124.158.12.202 - - [06/Sep/2020:12:08:28 +0200] "GET /wp-login.php HTTP/1.1" 200 9184 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 124.158.12.202 - - [06/Sep/2020:12:08:31 +0200] "POST /wp-login.php HTTP/1.1" 200 9435 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 124.158.12.202 - - [06/Sep/2020:12:08:33 +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-09-07 00:02:30 |
| 51.75.87.58 | attack | 2020-09-05 12:39:32.540258-0500 localhost smtpd[46585]: NOQUEUE: reject: RCPT from unknown[51.75.87.58]: 450 4.7.25 Client host rejected: cannot find your hostname, [51.75.87.58]; from= |
2020-09-07 00:15:31 |