城市(city): unknown
省份(region): unknown
国家(country): Italy
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 79.21.7.239
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 39284
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;79.21.7.239. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021400 1800 900 604800 86400
;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 14 17:13:06 CST 2025
;; MSG SIZE rcvd: 104239.7.21.79.in-addr.arpa domain name pointer host-79-21-7-239.retail.telecomitalia.it.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
239.7.21.79.in-addr.arpa name = host-79-21-7-239.retail.telecomitalia.it.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 222.186.173.154 | attackspambots | 2020-06-27T13:01:03.659531vps751288.ovh.net sshd\[29598\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.154 user=root 2020-06-27T13:01:05.313744vps751288.ovh.net sshd\[29598\]: Failed password for root from 222.186.173.154 port 12248 ssh2 2020-06-27T13:01:08.335621vps751288.ovh.net sshd\[29598\]: Failed password for root from 222.186.173.154 port 12248 ssh2 2020-06-27T13:01:13.008580vps751288.ovh.net sshd\[29598\]: Failed password for root from 222.186.173.154 port 12248 ssh2 2020-06-27T13:01:16.227162vps751288.ovh.net sshd\[29598\]: Failed password for root from 222.186.173.154 port 12248 ssh2 |
2020-06-27 19:07:41 |
| 36.22.187.34 | attackspam | 2020-06-26T23:33:00.624203hostname sshd[27214]: Invalid user lqy from 36.22.187.34 port 46076 2020-06-26T23:33:02.784823hostname sshd[27214]: Failed password for invalid user lqy from 36.22.187.34 port 46076 ssh2 2020-06-26T23:37:07.448447hostname sshd[30307]: Invalid user postgres from 36.22.187.34 port 55870 ... |
2020-06-27 19:19:48 |
| 222.186.173.238 | attackbotsspam | Jun 27 12:46:45 abendstille sshd\[23694\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.173.238 user=root Jun 27 12:46:47 abendstille sshd\[23694\]: Failed password for root from 222.186.173.238 port 50444 ssh2 Jun 27 12:46:50 abendstille sshd\[23694\]: Failed password for root from 222.186.173.238 port 50444 ssh2 Jun 27 12:46:54 abendstille sshd\[23694\]: Failed password for root from 222.186.173.238 port 50444 ssh2 Jun 27 12:46:57 abendstille sshd\[23694\]: Failed password for root from 222.186.173.238 port 50444 ssh2 ... |
2020-06-27 18:50:21 |
| 218.92.0.216 | attackspambots | Jun 27 11:07:59 localhost sshd[103166]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.216 user=root Jun 27 11:08:01 localhost sshd[103166]: Failed password for root from 218.92.0.216 port 59187 ssh2 Jun 27 11:08:03 localhost sshd[103166]: Failed password for root from 218.92.0.216 port 59187 ssh2 Jun 27 11:07:59 localhost sshd[103166]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.216 user=root Jun 27 11:08:01 localhost sshd[103166]: Failed password for root from 218.92.0.216 port 59187 ssh2 Jun 27 11:08:03 localhost sshd[103166]: Failed password for root from 218.92.0.216 port 59187 ssh2 Jun 27 11:07:59 localhost sshd[103166]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.216 user=root Jun 27 11:08:01 localhost sshd[103166]: Failed password for root from 218.92.0.216 port 59187 ssh2 Jun 27 11:08:03 localhost sshd[103166]: Failed pa ... |
2020-06-27 19:17:22 |
| 107.172.229.157 | attackspambots | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found loischiropractic.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 th |
2020-06-27 19:22:09 |
| 13.76.241.176 | attack | 20 attempts against mh-ssh on frost |
2020-06-27 19:10:37 |
| 45.115.178.83 | attackbots | Jun 27 02:19:23 ws24vmsma01 sshd[55023]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.115.178.83 Jun 27 02:19:25 ws24vmsma01 sshd[55023]: Failed password for invalid user ubuntu from 45.115.178.83 port 58562 ssh2 ... |
2020-06-27 19:21:10 |
| 112.3.27.97 | attack | Jun 27 12:26:56 buvik sshd[28879]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.3.27.97 Jun 27 12:26:58 buvik sshd[28879]: Failed password for invalid user git from 112.3.27.97 port 40776 ssh2 Jun 27 12:31:16 buvik sshd[29505]: Invalid user msq from 112.3.27.97 ... |
2020-06-27 18:52:44 |
| 137.74.173.182 | attackbots | Jun 27 12:45:55 nextcloud sshd\[4773\]: Invalid user wim from 137.74.173.182 Jun 27 12:45:55 nextcloud sshd\[4773\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.74.173.182 Jun 27 12:45:57 nextcloud sshd\[4773\]: Failed password for invalid user wim from 137.74.173.182 port 41176 ssh2 |
2020-06-27 19:26:36 |
| 42.81.160.213 | attackbotsspam | Invalid user admin from 42.81.160.213 port 56940 |
2020-06-27 19:16:59 |
| 78.128.113.109 | attackspambots | Time: Sat Jun 27 06:43:50 2020 -0400 IP: 78.128.113.109 (BG/Bulgaria/ip-113-109.4vendeta.com) Failures: 30 (smtpauth) Interval: 3600 seconds Blocked: Permanent Block |
2020-06-27 19:04:04 |
| 36.226.173.172 | attack | unauthorized connection attempt |
2020-06-27 19:08:41 |
| 198.245.64.185 | attackspambots | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found loischiropractic.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 th |
2020-06-27 19:24:38 |
| 112.21.188.148 | attackspambots | 2020-06-27T01:04:54.490663devel sshd[19635]: Invalid user test from 112.21.188.148 port 37828 2020-06-27T01:04:55.893731devel sshd[19635]: Failed password for invalid user test from 112.21.188.148 port 37828 ssh2 2020-06-27T01:37:07.577829devel sshd[21795]: Invalid user scan1 from 112.21.188.148 port 40972 |
2020-06-27 19:11:46 |
| 41.221.251.19 | attackbots | port scan and connect, tcp 1433 (ms-sql-s) |
2020-06-27 19:12:11 |