城市(city): unknown
省份(region): unknown
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 18.211.104.14
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2932
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;18.211.104.14. IN A
;; AUTHORITY SECTION:
. 599 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022031801 1800 900 604800 86400
;; Query time: 66 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 19 03:44:17 CST 2022
;; MSG SIZE rcvd: 10614.104.211.18.in-addr.arpa domain name pointer ec2-18-211-104-14.compute-1.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
14.104.211.18.in-addr.arpa name = ec2-18-211-104-14.compute-1.amazonaws.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 106.75.153.43 | attack | SSH/22 MH Probe, BF, Hack - |
2019-08-15 17:42:34 |
| 188.31.11.2 | attackbotsspam | this PM doesn't deliver -likely chaos - promised a lot before being a PM/not under delivering - - sort it out - or renew labour and conservatives bull - can't afford to or wish to lose trade with our USA uk -also review on texting rape or murder online acceptable in uk -in the GP range likely be arrested -online or offline rules -confirm GSTATIC IS BBC ITV and rest of trash unregulated TV MEDIA and exploiting -another unregulated service provider -ntt.net/gtt.net -already have the data -it is controlled by uk |
2019-08-15 17:19:40 |
| 213.21.67.184 | attack | Aug 15 09:29:50 unicornsoft sshd\[13552\]: Invalid user test2 from 213.21.67.184 Aug 15 09:29:50 unicornsoft sshd\[13552\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.21.67.184 Aug 15 09:29:52 unicornsoft sshd\[13552\]: Failed password for invalid user test2 from 213.21.67.184 port 58415 ssh2 |
2019-08-15 17:37:36 |
| 187.44.113.33 | attack | Aug 15 01:22:03 nextcloud sshd\[6144\]: Invalid user rm from 187.44.113.33 Aug 15 01:22:03 nextcloud sshd\[6144\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.44.113.33 Aug 15 01:22:05 nextcloud sshd\[6144\]: Failed password for invalid user rm from 187.44.113.33 port 36994 ssh2 ... |
2019-08-15 17:26:44 |
| 187.198.96.128 | attackbotsspam | Looking for resource vulnerabilities |
2019-08-15 17:22:56 |
| 192.3.177.213 | attackspambots | Invalid user wn from 192.3.177.213 port 38368 |
2019-08-15 17:15:00 |
| 79.10.92.46 | attackspambots | Aug 15 02:37:09 OPSO sshd\[3763\]: Invalid user patrice from 79.10.92.46 port 58430 Aug 15 02:37:09 OPSO sshd\[3763\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.10.92.46 Aug 15 02:37:11 OPSO sshd\[3763\]: Failed password for invalid user patrice from 79.10.92.46 port 58430 ssh2 Aug 15 02:46:40 OPSO sshd\[5219\]: Invalid user support from 79.10.92.46 port 35828 Aug 15 02:46:40 OPSO sshd\[5219\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.10.92.46 |
2019-08-15 17:04:06 |
| 172.93.192.212 | attackspambots | (From eric@talkwithcustomer.com) Hello siegelchiropractic.com, People ask, “why does TalkWithCustomer work so well?” It’s simple. TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time. - NOT one week, two weeks, three weeks after they’ve checked out your website siegelchiropractic.com. - NOT with a form letter style email that looks like it was written by a bot. - NOT with a robocall that could come at any time out of the blue. TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU. They kick off the conversation. They take that first step. They ask to hear from you regarding what you have to offer and how it can make their life better. And it happens almost immediately. In real time. While they’re still looking over your website siegelchiropractic.com, trying to make up their mind whether you are right for them. When you connect with them at that very moment it’s the ultimate in Perfect Timing – as |
2019-08-15 17:45:16 |
| 157.230.14.226 | attack | Aug 15 11:28:23 localhost sshd\[586\]: Invalid user debian from 157.230.14.226 Aug 15 11:28:23 localhost sshd\[586\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.14.226 Aug 15 11:28:25 localhost sshd\[586\]: Failed password for invalid user debian from 157.230.14.226 port 33174 ssh2 Aug 15 11:38:09 localhost sshd\[1059\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.14.226 user=root Aug 15 11:38:11 localhost sshd\[1059\]: Failed password for root from 157.230.14.226 port 47450 ssh2 ... |
2019-08-15 17:39:13 |
| 181.215.151.77 | attackbots | (From eric@talkwithcustomer.com) Hello siegelchiropractic.com, People ask, “why does TalkWithCustomer work so well?” It’s simple. TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time. - NOT one week, two weeks, three weeks after they’ve checked out your website siegelchiropractic.com. - NOT with a form letter style email that looks like it was written by a bot. - NOT with a robocall that could come at any time out of the blue. TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU. They kick off the conversation. They take that first step. They ask to hear from you regarding what you have to offer and how it can make their life better. And it happens almost immediately. In real time. While they’re still looking over your website siegelchiropractic.com, trying to make up their mind whether you are right for them. When you connect with them at that very moment it’s the ultimate in Perfect Timing – as |
2019-08-15 17:38:53 |
| 218.1.18.78 | attackspam | Aug 15 04:36:52 debian sshd\[7994\]: Invalid user system from 218.1.18.78 port 65167 Aug 15 04:36:52 debian sshd\[7994\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.1.18.78 ... |
2019-08-15 16:56:56 |
| 193.80.166.174 | attack | 2019-08-15T19:29:51.265153luisaranguren sshd[724]: Connection from 193.80.166.174 port 49858 on 10.10.10.6 port 22 2019-08-15T19:29:53.040906luisaranguren sshd[724]: Invalid user edi from 193.80.166.174 port 49858 2019-08-15T19:29:53.045998luisaranguren sshd[724]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.80.166.174 2019-08-15T19:29:51.265153luisaranguren sshd[724]: Connection from 193.80.166.174 port 49858 on 10.10.10.6 port 22 2019-08-15T19:29:53.040906luisaranguren sshd[724]: Invalid user edi from 193.80.166.174 port 49858 2019-08-15T19:29:54.544689luisaranguren sshd[724]: Failed password for invalid user edi from 193.80.166.174 port 49858 ssh2 ... |
2019-08-15 17:36:47 |
| 187.163.181.234 | attackbotsspam | Automatic report - Port Scan Attack |
2019-08-15 17:02:12 |
| 138.122.38.129 | attack | failed_logins |
2019-08-15 17:09:02 |
| 54.37.136.87 | attackbots | $f2bV_matches |
2019-08-15 17:03:38 |