城市(city): unknown
省份(region): unknown
国家(country): Viet Nam
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 14.161.76.67
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 22274
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;14.161.76.67. IN A
;; AUTHORITY SECTION:
. 598 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022022701 1800 900 604800 86400
;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 04:10:32 CST 2022
;; MSG SIZE rcvd: 105
67.76.161.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.76.161.14.in-addr.arpa name = static.vnpt.vn.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 37.75.127.240 | attack | Apr 22 14:36:29 prod4 vsftpd\[5955\]: \[anonymous\] FAIL LOGIN: Client "37.75.127.240" Apr 22 14:36:32 prod4 vsftpd\[5957\]: \[www\] FAIL LOGIN: Client "37.75.127.240" Apr 22 14:36:33 prod4 vsftpd\[5959\]: \[www\] FAIL LOGIN: Client "37.75.127.240" Apr 22 14:36:36 prod4 vsftpd\[5961\]: \[www\] FAIL LOGIN: Client "37.75.127.240" Apr 22 14:36:38 prod4 vsftpd\[5965\]: \[www\] FAIL LOGIN: Client "37.75.127.240" ... |
2020-04-22 21:13:43 |
| 41.41.216.227 | attackbots | 20/4/22@08:04:13: FAIL: Alarm-Network address from=41.41.216.227 ... |
2020-04-22 21:11:17 |
| 173.44.164.14 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found millenniumchiro.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 tha |
2020-04-22 20:51:52 |
| 109.75.44.224 | attack | Unauthorised access (Apr 22) SRC=109.75.44.224 LEN=48 TTL=119 ID=19427 DF TCP DPT=445 WINDOW=8192 SYN |
2020-04-22 20:55:30 |
| 185.176.27.246 | attack | 04/22/2020-09:05:52.937361 185.176.27.246 Protocol: 6 ET DROP Dshield Block Listed Source group 1 |
2020-04-22 21:08:49 |
| 14.63.168.66 | attack | Apr 22 18:58:47 itv-usvr-02 sshd[2271]: Invalid user admin from 14.63.168.66 port 60282 Apr 22 18:58:47 itv-usvr-02 sshd[2271]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.63.168.66 Apr 22 18:58:47 itv-usvr-02 sshd[2271]: Invalid user admin from 14.63.168.66 port 60282 Apr 22 18:58:49 itv-usvr-02 sshd[2271]: Failed password for invalid user admin from 14.63.168.66 port 60282 ssh2 Apr 22 19:04:04 itv-usvr-02 sshd[2407]: Invalid user ao from 14.63.168.66 port 51472 |
2020-04-22 21:20:02 |
| 167.71.96.148 | attackspambots | Apr 21 11:27:26 rs-7 sshd[5329]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.96.148 user=r.r Apr 21 11:27:28 rs-7 sshd[5329]: Failed password for r.r from 167.71.96.148 port 49462 ssh2 Apr 21 11:27:28 rs-7 sshd[5329]: Received disconnect from 167.71.96.148 port 49462:11: Bye Bye [preauth] Apr 21 11:27:28 rs-7 sshd[5329]: Disconnected from 167.71.96.148 port 49462 [preauth] Apr 21 11:36:21 rs-7 sshd[7501]: Invalid user wh from 167.71.96.148 port 56850 Apr 21 11:36:21 rs-7 sshd[7501]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.71.96.148 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=167.71.96.148 |
2020-04-22 21:26:07 |
| 50.104.13.15 | spambotsattack | This is 1 of several ip addresses stalking and hard my kids and me on internet for 2 in a half years. They have my credit card info all my passwords stole 7 email ACCTS that r still active and used with different names. They edit right on the screen everything even legal documents. My ip is 192.168.254.254 please look into this issue and block these psycho paths. Also they have my apps cloned so they can run them |
2020-04-22 21:28:21 |
| 111.229.48.106 | attackbots | Apr 22 09:50:27 dns1 sshd[8593]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.48.106 Apr 22 09:50:30 dns1 sshd[8593]: Failed password for invalid user wv from 111.229.48.106 port 56660 ssh2 Apr 22 09:55:26 dns1 sshd[8928]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.229.48.106 |
2020-04-22 21:27:35 |
| 113.189.46.45 | attackspam | Unauthorized connection attempt detected from IP address 113.189.46.45 to port 445 |
2020-04-22 21:03:59 |
| 50.104.13.15 | spambotsattack | This is 1 of several ip addresses stalking and hard my kids and me on internet for 2 in a half years. They have my credit card info all my passwords stole 7 email ACCTS that r still active and used with different names. They edit right on the screen everything even legal documents. My ip is 192.168.254.254 please look into this issue and block these psycho paths. Also they have my apps cloned so they can run them |
2020-04-22 21:28:07 |
| 54.39.138.246 | attackspambots | "fail2ban match" |
2020-04-22 21:10:18 |
| 45.143.220.112 | attackbots | UDP scanned port list, 15080, 25080, 35080, 45080, 55080 |
2020-04-22 21:16:48 |
| 116.104.78.47 | attackbotsspam | Lines containing failures of 116.104.78.47 Apr 22 04:43:32 server-name sshd[6842]: Invalid user admin from 116.104.78.47 port 36490 Apr 22 04:43:32 server-name sshd[6842]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.104.78.47 Apr 22 04:43:34 server-name sshd[6842]: Failed password for invalid user admin from 116.104.78.47 port 36490 ssh2 Apr 22 04:43:36 server-name sshd[6842]: Connection closed by invalid user admin 116.104.78.47 port 36490 [preauth] ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=116.104.78.47 |
2020-04-22 21:24:04 |
| 182.255.42.116 | attack | Automatic report - XMLRPC Attack |
2020-04-22 20:50:49 |