城市(city): unknown
省份(region): unknown
国家(country): Australia
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 143.42.34.12
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12467
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;143.42.34.12. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021401 1800 900 604800 86400
;; Query time: 40 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 15 07:56:41 CST 2025
;; MSG SIZE rcvd: 10512.34.42.143.in-addr.arpa domain name pointer 143-42-34-12.ip.linodeusercontent.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
12.34.42.143.in-addr.arpa name = 143-42-34-12.ip.linodeusercontent.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 126.203.36.46 | attackspam | Aug 31 07:14:37 v26 sshd[27039]: Invalid user pi from 126.203.36.46 port 39026 Aug 31 07:14:37 v26 sshd[27037]: Invalid user pi from 126.203.36.46 port 39024 Aug 31 07:14:37 v26 sshd[27037]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=126.203.36.46 Aug 31 07:14:37 v26 sshd[27039]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=126.203.36.46 Aug 31 07:14:39 v26 sshd[27039]: Failed password for invalid user pi from 126.203.36.46 port 39026 ssh2 Aug 31 07:14:39 v26 sshd[27037]: Failed password for invalid user pi from 126.203.36.46 port 39024 ssh2 Aug 31 07:14:39 v26 sshd[27039]: Connection closed by 126.203.36.46 port 39026 [preauth] Aug 31 07:14:39 v26 sshd[27037]: Connection closed by 126.203.36.46 port 39024 [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=126.203.36.46 |
2020-09-06 15:22:21 |
| 110.174.229.211 | attackspam | Aug 31 07:14:56 h2022099 sshd[11139]: Invalid user admin from 110.174.229.211 Aug 31 07:14:56 h2022099 sshd[11139]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=110-174-229-211.tpgi.com.au Aug 31 07:14:58 h2022099 sshd[11139]: Failed password for invalid user admin from 110.174.229.211 port 40781 ssh2 Aug 31 07:14:58 h2022099 sshd[11139]: Received disconnect from 110.174.229.211: 11: Bye Bye [preauth] Aug 31 07:15:01 h2022099 sshd[11141]: Invalid user admin from 110.174.229.211 Aug 31 07:15:01 h2022099 sshd[11141]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=110-174-229-211.tpgi.com.au ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=110.174.229.211 |
2020-09-06 15:27:23 |
| 41.82.99.183 | attackbots | Sep 5 23:22:31 mxgate1 postfix/postscreen[9512]: CONNECT from [41.82.99.183]:37756 to [176.31.12.44]:25 Sep 5 23:22:31 mxgate1 postfix/dnsblog[9554]: addr 41.82.99.183 listed by domain zen.spamhaus.org as 127.0.0.3 Sep 5 23:22:31 mxgate1 postfix/dnsblog[9554]: addr 41.82.99.183 listed by domain zen.spamhaus.org as 127.0.0.4 Sep 5 23:22:31 mxgate1 postfix/dnsblog[9554]: addr 41.82.99.183 listed by domain zen.spamhaus.org as 127.0.0.11 Sep 5 23:22:31 mxgate1 postfix/dnsblog[9555]: addr 41.82.99.183 listed by domain cbl.abuseat.org as 127.0.0.2 Sep 5 23:22:31 mxgate1 postfix/dnsblog[9553]: addr 41.82.99.183 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2 Sep 5 23:22:31 mxgate1 postfix/dnsblog[9552]: addr 41.82.99.183 listed by domain b.barracudacentral.org as 127.0.0.2 Sep 5 23:22:37 mxgate1 postfix/postscreen[9512]: DNSBL rank 5 for [41.82.99.183]:37756 Sep x@x Sep 5 23:22:39 mxgate1 postfix/postscreen[9512]: HANGUP after 1.6 from [41.82.99.183]:37756 in tests ........ ------------------------------- |
2020-09-06 15:35:24 |
| 145.239.211.242 | attack | 145.239.211.242 - - [06/Sep/2020:06:01:30 +0100] "POST /wp-login.php HTTP/1.1" 200 1792 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 145.239.211.242 - - [06/Sep/2020:06:01:30 +0100] "POST /wp-login.php HTTP/1.1" 200 1790 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 145.239.211.242 - - [06/Sep/2020:06:01:30 +0100] "POST /xmlrpc.php HTTP/1.1" 403 219 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" ... |
2020-09-06 15:26:34 |
| 61.147.53.136 | attackbotsspam | Cowrie Honeypot: Unauthorised SSH/Telnet login attempt with user "plexuser" at 2020-09-05T16:49:16Z |
2020-09-06 14:57:45 |
| 171.103.190.158 | attackspambots | failed attempts to access the website, searching for vulnerabilities, also using following IPs: 27.37.246.129 , 94.231.218.223 , 116.90.237.125 , 190.235.214.78 , 190.98.53.86 , 45.170.129.135 , 170.239.242.222 , 43.249.113.243 , 103.140.4.87 , 171.103.190.158 , 72.210.252.135 |
2020-09-06 15:33:29 |
| 45.95.168.96 | attackspam | Sep 6 09:15:13 mail postfix/smtpd\[27658\]: warning: unknown\[45.95.168.96\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\ Sep 6 09:16:15 mail postfix/smtpd\[27658\]: warning: unknown\[45.95.168.96\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\ Sep 6 09:16:15 mail postfix/smtpd\[27676\]: warning: unknown\[45.95.168.96\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\ Sep 6 09:16:15 mail postfix/smtpd\[27659\]: warning: unknown\[45.95.168.96\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6\ |
2020-09-06 15:29:16 |
| 14.141.244.114 | attackspam | RDP Bruteforce |
2020-09-06 15:32:24 |
| 2001:e68:544c:4780:f886:b12e:f6a:dbea | attackbotsspam | xmlrpc attack |
2020-09-06 15:00:44 |
| 134.202.64.131 | attack | (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 15:12:16 |
| 164.132.46.14 | attackbots | Sep 6 08:15:05 root sshd[16768]: Failed password for root from 164.132.46.14 port 55950 ssh2 ... |
2020-09-06 14:54:58 |
| 103.78.15.2 | attack | Automatic report - Banned IP Access |
2020-09-06 15:09:08 |
| 165.22.127.136 | attackspam | ssh brute force attempt |
2020-09-06 15:10:47 |
| 62.234.20.135 | attack | Sep 6 07:57:36 ns382633 sshd\[18769\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.20.135 user=root Sep 6 07:57:38 ns382633 sshd\[18769\]: Failed password for root from 62.234.20.135 port 36218 ssh2 Sep 6 07:59:38 ns382633 sshd\[18983\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.20.135 user=root Sep 6 07:59:41 ns382633 sshd\[18983\]: Failed password for root from 62.234.20.135 port 55252 ssh2 Sep 6 08:00:40 ns382633 sshd\[19521\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.20.135 user=root |
2020-09-06 15:19:08 |
| 156.96.62.82 | attackbotsspam | Sep 5 21:19:35 mail postfix/smtpd[26616]: warning: unknown[156.96.62.82]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Sep 5 21:19:41 mail postfix/smtpd[26616]: warning: unknown[156.96.62.82]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Sep 5 21:19:51 mail postfix/smtpd[26616]: warning: unknown[156.96.62.82]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 |
2020-09-06 14:55:30 |