城市(city): unknown
省份(region): unknown
国家(country): Lithuania
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 78.63.204.91
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 31498
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;78.63.204.91. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021100 1800 900 604800 86400
;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 11 18:23:09 CST 2025
;; MSG SIZE rcvd: 10591.204.63.78.in-addr.arpa domain name pointer 78-63-204-91.static.zebra.lt.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
91.204.63.78.in-addr.arpa name = 78-63-204-91.static.zebra.lt.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 51.77.220.127 | attackbots | 51.77.220.127 - - [06/Sep/2020:02:19:22 +0400] "POST /GponForm/diag_Form?style/ HTTP/1.1" 502 157 "-" "curl/7.3.2" ... |
2020-09-06 06:55:15 |
| 14.161.50.104 | attack | $f2bV_matches |
2020-09-06 07:13:26 |
| 134.202.64.131 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found staytunedchiropractic.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 softwa |
2020-09-06 07:15:16 |
| 222.186.42.213 | attackspambots | Sep 6 01:10:05 OPSO sshd\[23123\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.213 user=root Sep 6 01:10:07 OPSO sshd\[23123\]: Failed password for root from 222.186.42.213 port 43549 ssh2 Sep 6 01:10:09 OPSO sshd\[23123\]: Failed password for root from 222.186.42.213 port 43549 ssh2 Sep 6 01:10:12 OPSO sshd\[23123\]: Failed password for root from 222.186.42.213 port 43549 ssh2 Sep 6 01:10:14 OPSO sshd\[23191\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.213 user=root |
2020-09-06 07:11:05 |
| 14.29.215.211 | attack | Port probing on unauthorized port 6379 |
2020-09-06 06:46:11 |
| 37.254.110.43 | attackbotsspam | php WP PHPmyadamin ABUSE blocked for 12h |
2020-09-06 07:09:54 |
| 106.8.164.185 | attackspam | 2020-08-31 07:02:10 login_virtual_exim authenticator failed for (Qb2PqNspx) [106.8.164.185]: 535 Incorrect authentication data (set_id=strueber.stellpflug) ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=106.8.164.185 |
2020-09-06 06:59:18 |
| 162.243.130.67 | attackspam | " " |
2020-09-06 07:17:46 |
| 145.239.80.14 | attackspambots | Sep 6 00:00:51 markkoudstaal sshd[19338]: Failed password for root from 145.239.80.14 port 47432 ssh2 Sep 6 00:04:41 markkoudstaal sshd[28362]: Failed password for root from 145.239.80.14 port 53272 ssh2 ... |
2020-09-06 07:12:54 |
| 213.180.203.49 | attackspam | Mailserver and mailaccount attacks |
2020-09-06 06:45:30 |
| 120.53.243.211 | attack | Sep 5 18:49:50 ip106 sshd[30142]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.53.243.211 Sep 5 18:49:52 ip106 sshd[30142]: Failed password for invalid user ljq from 120.53.243.211 port 49968 ssh2 ... |
2020-09-06 06:44:55 |
| 46.114.56.28 | attackbots | Lines containing failures of 46.114.56.28 Aug 31 07:02:12 dns01 sshd[17892]: Bad protocol version identification '' from 46.114.56.28 port 60776 Aug 31 07:02:28 dns01 sshd[17898]: Invalid user pi from 46.114.56.28 port 43030 Aug 31 07:02:28 dns01 sshd[17898]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.114.56.28 Aug 31 07:02:29 dns01 sshd[17898]: Failed password for invalid user pi from 46.114.56.28 port 43030 ssh2 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=46.114.56.28 |
2020-09-06 07:03:40 |
| 45.142.120.36 | attack | (smtpauth) Failed SMTP AUTH login from 45.142.120.36 (RU/Russia/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SMTPAUTH; Logs: 2020-09-05 18:24:13 dovecot_login authenticator failed for (User) [45.142.120.36]:35824: 535 Incorrect authentication data (set_id=department@xeoserver.com) 2020-09-05 18:24:20 dovecot_login authenticator failed for (User) [45.142.120.36]:37392: 535 Incorrect authentication data (set_id=department@xeoserver.com) 2020-09-05 18:24:30 dovecot_login authenticator failed for (User) [45.142.120.36]:47262: 535 Incorrect authentication data (set_id=tabid@xeoserver.com) 2020-09-05 18:24:38 dovecot_login authenticator failed for (User) [45.142.120.36]:3510: 535 Incorrect authentication data (set_id=tabid@xeoserver.com) 2020-09-05 18:24:49 dovecot_login authenticator failed for (User) [45.142.120.36]:44402: 535 Incorrect authentication data (set_id=tabid@xeoserver.com) |
2020-09-06 06:47:12 |
| 171.13.47.75 | attackbots | Lines containing failures of 171.13.47.75 (max 1000) ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=171.13.47.75 |
2020-09-06 07:15:41 |
| 194.61.24.102 | attackbotsspam | Automatic report - XMLRPC Attack |
2020-09-06 06:43:45 |