城市(city): unknown
省份(region): unknown
国家(country): United States of America (the)
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 35.94.214.31
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 11676
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;35.94.214.31. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012501 1800 900 604800 86400
;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 26 02:04:56 CST 2025
;; MSG SIZE rcvd: 10531.214.94.35.in-addr.arpa domain name pointer ec2-35-94-214-31.us-west-2.compute.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
31.214.94.35.in-addr.arpa name = ec2-35-94-214-31.us-west-2.compute.amazonaws.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 157.55.84.206 | attack | $f2bV_matches |
2020-07-16 14:30:25 |
| 62.234.110.91 | attack | Invalid user new from 62.234.110.91 port 34622 |
2020-07-16 14:28:55 |
| 3.226.116.202 | attack | trying to access non-authorized port |
2020-07-16 14:42:23 |
| 162.243.130.31 | attack | " " |
2020-07-16 14:37:28 |
| 61.177.172.41 | attackbots | Jul 16 08:03:20 jane sshd[28815]: Failed password for root from 61.177.172.41 port 11758 ssh2 Jul 16 08:03:23 jane sshd[28815]: Failed password for root from 61.177.172.41 port 11758 ssh2 ... |
2020-07-16 14:09:11 |
| 35.224.204.56 | attack | $f2bV_matches |
2020-07-16 14:34:13 |
| 211.108.69.103 | attackspam | Brute-force attempt banned |
2020-07-16 14:11:42 |
| 167.172.243.126 | attackbots | Jul 16 06:34:26 lnxweb62 sshd[29993]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.243.126 |
2020-07-16 14:14:13 |
| 23.90.28.66 | attack | (From syme.chara@googlemail.com) Hi, Do you have a Website? Of course you do because I am looking at your website martychiropractic.net now. Are you struggling for Leads and Sales? You’re not the only one. So many Website owners struggle to convert their Visitors into Leads & Sales. There’s a simple way to fix this problem. You could use a Live Chat app on your Website martychiropractic.net and hire Chat Agents. But only if you’ve got deep pockets and you’re happy to fork out THOUSANDS of dollars for the quality you need. ===== But what if you could automate Live Chat so it’s HUMAN-FREE? What if you could exploit NEW “AI” Technology to engage with your Visitors INSTANTLY. And AUTOMATICALLY convert them into Leads & Sales. WITHOUT spending THOUSANDS of dollars on Live Chat Agents. And WITHOUT hiring expensive coders. In fact, all you need to do to activate this LATEST “AI” Website Tech.. ..is to COPY & PASTE a single line of “Website Code”. ==> http://www.zoomsof |
2020-07-16 14:24:24 |
| 46.38.150.203 | attackbotsspam | Jul 16 08:17:47 relay postfix/smtpd\[7273\]: warning: unknown\[46.38.150.203\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 16 08:18:10 relay postfix/smtpd\[11034\]: warning: unknown\[46.38.150.203\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 16 08:18:28 relay postfix/smtpd\[7273\]: warning: unknown\[46.38.150.203\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 16 08:18:51 relay postfix/smtpd\[16176\]: warning: unknown\[46.38.150.203\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jul 16 08:19:08 relay postfix/smtpd\[12879\]: warning: unknown\[46.38.150.203\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-07-16 14:31:38 |
| 177.37.139.85 | attack | Automatic report - XMLRPC Attack |
2020-07-16 14:25:55 |
| 118.24.239.245 | attackspam | Jul 15 19:08:08 sachi sshd\[5644\]: Invalid user vmail from 118.24.239.245 Jul 15 19:08:08 sachi sshd\[5644\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.239.245 Jul 15 19:08:10 sachi sshd\[5644\]: Failed password for invalid user vmail from 118.24.239.245 port 59294 ssh2 Jul 15 19:12:42 sachi sshd\[6039\]: Invalid user user0 from 118.24.239.245 Jul 15 19:12:42 sachi sshd\[6039\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.239.245 |
2020-07-16 14:28:01 |
| 54.38.185.131 | attack | Jul 16 09:01:28 lukav-desktop sshd\[17957\]: Invalid user francois from 54.38.185.131 Jul 16 09:01:28 lukav-desktop sshd\[17957\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.38.185.131 Jul 16 09:01:29 lukav-desktop sshd\[17957\]: Failed password for invalid user francois from 54.38.185.131 port 47136 ssh2 Jul 16 09:05:44 lukav-desktop sshd\[13809\]: Invalid user yuanliang from 54.38.185.131 Jul 16 09:05:44 lukav-desktop sshd\[13809\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.38.185.131 |
2020-07-16 14:09:41 |
| 61.177.172.168 | attack | Jul 16 08:39:42 vmd17057 sshd[13337]: Failed password for root from 61.177.172.168 port 28738 ssh2 Jul 16 08:39:46 vmd17057 sshd[13337]: Failed password for root from 61.177.172.168 port 28738 ssh2 ... |
2020-07-16 14:41:37 |
| 111.93.71.219 | attackbots | 2020-07-16T08:03:32.373554sd-86998 sshd[35194]: Invalid user zou from 111.93.71.219 port 51915 2020-07-16T08:03:32.381872sd-86998 sshd[35194]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.93.71.219 2020-07-16T08:03:32.373554sd-86998 sshd[35194]: Invalid user zou from 111.93.71.219 port 51915 2020-07-16T08:03:34.825690sd-86998 sshd[35194]: Failed password for invalid user zou from 111.93.71.219 port 51915 ssh2 2020-07-16T08:08:33.100489sd-86998 sshd[35844]: Invalid user kate from 111.93.71.219 port 59359 ... |
2020-07-16 14:43:25 |