城市(city): unknown
省份(region): unknown
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 18.144.34.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 33014
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;18.144.34.1. IN A
;; AUTHORITY SECTION:
. 207 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022021800 1800 900 604800 86400
;; Query time: 57 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 18:48:12 CST 2022
;; MSG SIZE rcvd: 1041.34.144.18.in-addr.arpa domain name pointer ec2-18-144-34-1.us-west-1.compute.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
1.34.144.18.in-addr.arpa name = ec2-18-144-34-1.us-west-1.compute.amazonaws.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 218.92.0.221 | attackspambots | Aug 15 10:20:52 scw-6657dc sshd[26536]: Failed password for root from 218.92.0.221 port 23380 ssh2 Aug 15 10:20:52 scw-6657dc sshd[26536]: Failed password for root from 218.92.0.221 port 23380 ssh2 Aug 15 10:20:54 scw-6657dc sshd[26536]: Failed password for root from 218.92.0.221 port 23380 ssh2 ... |
2020-08-15 18:25:55 |
| 183.61.109.23 | attackbotsspam | frenzy |
2020-08-15 18:13:23 |
| 62.210.7.59 | attackbotsspam | 62.210.7.59 - - [15/Aug/2020:10:49:10 +0100] "POST /wp-login.php HTTP/1.1" 200 2100 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 62.210.7.59 - - [15/Aug/2020:10:49:11 +0100] "POST /wp-login.php HTTP/1.1" 200 2101 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 62.210.7.59 - - [15/Aug/2020:10:49:11 +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-08-15 18:25:23 |
| 176.31.127.152 | attackbots | frenzy |
2020-08-15 18:22:06 |
| 87.246.7.30 | attackspam | SSH invalid-user multiple login try |
2020-08-15 18:24:22 |
| 192.241.239.189 | attack | [Thu Aug 06 03:49:30 2020] - DDoS Attack From IP: 192.241.239.189 Port: 54114 |
2020-08-15 17:59:33 |
| 183.89.120.180 | attack | Unauthorised access (Aug 15) SRC=183.89.120.180 LEN=52 TOS=0x10 PREC=0x40 TTL=113 ID=21326 DF TCP DPT=445 WINDOW=8192 SYN |
2020-08-15 17:58:33 |
| 139.155.127.59 | attackspam | Aug 15 10:05:52 pornomens sshd\[20440\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.127.59 user=root Aug 15 10:05:54 pornomens sshd\[20440\]: Failed password for root from 139.155.127.59 port 49502 ssh2 Aug 15 10:24:59 pornomens sshd\[20655\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.127.59 user=root ... |
2020-08-15 18:22:21 |
| 139.59.83.203 | attack | 139.59.83.203 - - [15/Aug/2020:10:22:10 +0100] "POST /wp-login.php HTTP/1.1" 200 1968 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 139.59.83.203 - - [15/Aug/2020:10:22:13 +0100] "POST /wp-login.php HTTP/1.1" 200 1952 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0" 139.59.83.203 - - [15/Aug/2020:10:22:13 +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-08-15 18:14:38 |
| 45.72.61.23 | attackbotsspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found norburgchiro.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 c |
2020-08-15 17:50:04 |
| 218.21.240.24 | attackbotsspam | Aug 15 07:52:59 ns3033917 sshd[8463]: Failed password for root from 218.21.240.24 port 1989 ssh2 Aug 15 07:55:31 ns3033917 sshd[8486]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.21.240.24 user=root Aug 15 07:55:33 ns3033917 sshd[8486]: Failed password for root from 218.21.240.24 port 52108 ssh2 ... |
2020-08-15 18:03:51 |
| 128.199.92.187 | attack | TCP port : 13478 |
2020-08-15 18:26:26 |
| 221.156.126.1 | attack | frenzy |
2020-08-15 17:53:26 |
| 101.69.200.162 | attackbotsspam | Aug 15 11:44:36 vpn01 sshd[7782]: Failed password for root from 101.69.200.162 port 29292 ssh2 ... |
2020-08-15 18:16:03 |
| 75.112.68.166 | attackspambots | Aug 14 22:41:47 web1 sshd\[4552\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=75.112.68.166 user=root Aug 14 22:41:49 web1 sshd\[4552\]: Failed password for root from 75.112.68.166 port 44899 ssh2 Aug 14 22:46:34 web1 sshd\[4907\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=75.112.68.166 user=root Aug 14 22:46:35 web1 sshd\[4907\]: Failed password for root from 75.112.68.166 port 21666 ssh2 Aug 14 22:51:17 web1 sshd\[5256\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=75.112.68.166 user=root |
2020-08-15 17:52:22 |