城市(city): unknown
省份(region): unknown
国家(country): Viet Nam
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 14.245.245.67
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54800
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;14.245.245.67. IN A
;; AUTHORITY SECTION:
. 134 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022030803 1800 900 604800 86400
;; Query time: 21 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Mar 09 08:57:29 CST 2022
;; MSG SIZE rcvd: 10667.245.245.14.in-addr.arpa domain name pointer static.vnpt.vn.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
67.245.245.14.in-addr.arpa name = static.vnpt.vn.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 23.94.17.223 | attackbotsspam | (From eric@talkwithwebvisitor.com) Hey, my name’s Eric and for just a second, imagine this… - Someone does a search and winds up at hughesfamilychiro.com. - They hang out for a minute to check it out. “I’m interested… but… maybe…” - And then they hit the back button and check out the other search results instead. - Bottom line – you got an eyeball, but nothing else to show for it. - There they go. This isn’t really your fault – it happens a LOT – studies show 7 out of 10 visitors to any site disappear without leaving a trace. But you CAN fix that. Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number. It lets you know right then and there – enabling you to call that lead while they’re literally looking over your site. CLICK HERE http://www.talkwithwebvisitors.com to try out a Live Demo with Talk With Web Visitor now to see exactly how it works. Time is money when it comes to connecting with lea |
2020-08-15 14:29:18 |
| 119.45.50.17 | attack | 2020-08-15T05:50:22.656641vps-d63064a2 sshd[45460]: User root from 119.45.50.17 not allowed because not listed in AllowUsers 2020-08-15T05:50:24.456089vps-d63064a2 sshd[45460]: Failed password for invalid user root from 119.45.50.17 port 53678 ssh2 2020-08-15T05:51:21.949969vps-d63064a2 sshd[45475]: User root from 119.45.50.17 not allowed because not listed in AllowUsers 2020-08-15T05:51:21.966694vps-d63064a2 sshd[45475]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.45.50.17 user=root 2020-08-15T05:51:21.949969vps-d63064a2 sshd[45475]: User root from 119.45.50.17 not allowed because not listed in AllowUsers 2020-08-15T05:51:23.511882vps-d63064a2 sshd[45475]: Failed password for invalid user root from 119.45.50.17 port 32810 ssh2 ... |
2020-08-15 14:38:59 |
| 62.112.11.79 | attackbotsspam | Cowrie Honeypot: 10 unauthorised SSH/Telnet login attempts between 2020-08-15T03:25:33Z and 2020-08-15T03:55:04Z |
2020-08-15 14:54:11 |
| 62.112.11.81 | attackspam | Cowrie Honeypot: 10 unauthorised SSH/Telnet login attempts between 2020-08-15T03:25:31Z and 2020-08-15T03:55:16Z |
2020-08-15 14:46:04 |
| 115.217.19.16 | attack | 2020-08-15T06:07:57.455722shield sshd\[20097\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.217.19.16 user=root 2020-08-15T06:07:59.069986shield sshd\[20097\]: Failed password for root from 115.217.19.16 port 40958 ssh2 2020-08-15T06:10:26.459864shield sshd\[20363\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.217.19.16 user=root 2020-08-15T06:10:28.194778shield sshd\[20363\]: Failed password for root from 115.217.19.16 port 52576 ssh2 2020-08-15T06:12:46.193184shield sshd\[20638\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=115.217.19.16 user=root |
2020-08-15 14:48:31 |
| 106.12.69.68 | attackspambots | firewall-block, port(s): 24996/tcp |
2020-08-15 14:19:08 |
| 23.94.5.52 | attackspambots | (From eric@talkwithwebvisitor.com) Hey, my name’s Eric and for just a second, imagine this… - Someone does a search and winds up at hughesfamilychiro.com. - They hang out for a minute to check it out. “I’m interested… but… maybe…” - And then they hit the back button and check out the other search results instead. - Bottom line – you got an eyeball, but nothing else to show for it. - There they go. This isn’t really your fault – it happens a LOT – studies show 7 out of 10 visitors to any site disappear without leaving a trace. But you CAN fix that. Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number. It lets you know right then and there – enabling you to call that lead while they’re literally looking over your site. CLICK HERE http://www.talkwithwebvisitors.com to try out a Live Demo with Talk With Web Visitor now to see exactly how it works. Time is money when it comes to connecting with lea |
2020-08-15 14:31:56 |
| 222.186.31.166 | attackbots | Aug 15 02:45:27 NPSTNNYC01T sshd[29704]: Failed password for root from 222.186.31.166 port 17363 ssh2 Aug 15 02:45:38 NPSTNNYC01T sshd[29752]: Failed password for root from 222.186.31.166 port 45890 ssh2 Aug 15 02:45:40 NPSTNNYC01T sshd[29752]: Failed password for root from 222.186.31.166 port 45890 ssh2 ... |
2020-08-15 14:48:17 |
| 177.209.86.224 | attack | Automatic report - Port Scan Attack |
2020-08-15 14:27:42 |
| 183.144.74.40 | attackspambots | " " |
2020-08-15 14:29:42 |
| 219.135.209.164 | attackspam | Lines containing failures of 219.135.209.164 Aug 13 19:21:36 linuxrulz sshd[4006]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=219.135.209.164 user=r.r Aug 13 19:21:37 linuxrulz sshd[4006]: Failed password for r.r from 219.135.209.164 port 50633 ssh2 Aug 13 19:21:38 linuxrulz sshd[4006]: Received disconnect from 219.135.209.164 port 50633:11: Bye Bye [preauth] Aug 13 19:21:38 linuxrulz sshd[4006]: Disconnected from authenticating user r.r 219.135.209.164 port 50633 [preauth] Aug 13 19:36:59 linuxrulz sshd[5812]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=219.135.209.164 user=r.r Aug 13 19:37:02 linuxrulz sshd[5812]: Failed password for r.r from 219.135.209.164 port 62514 ssh2 Aug 13 19:37:03 linuxrulz sshd[5812]: Received disconnect from 219.135.209.164 port 62514:11: Bye Bye [preauth] Aug 13 19:37:03 linuxrulz sshd[5812]: Disconnected from authenticating user r.r 219.135.209.164 p........ ------------------------------ |
2020-08-15 14:35:51 |
| 178.47.143.198 | attackbots | Aug 15 04:22:23 serwer sshd\[20990\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.47.143.198 user=root Aug 15 04:22:25 serwer sshd\[20990\]: Failed password for root from 178.47.143.198 port 55004 ssh2 Aug 15 04:24:34 serwer sshd\[22217\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.47.143.198 user=root ... |
2020-08-15 14:53:07 |
| 5.69.54.109 | attack | Automatic report - Port Scan Attack |
2020-08-15 14:44:55 |
| 128.199.142.138 | attackspam | Aug 15 07:06:35 piServer sshd[16442]: Failed password for root from 128.199.142.138 port 56860 ssh2 Aug 15 07:09:24 piServer sshd[16715]: Failed password for root from 128.199.142.138 port 54146 ssh2 ... |
2020-08-15 14:57:07 |
| 101.108.185.43 | attack | Automatic report - Port Scan Attack |
2020-08-15 14:23:42 |