城市(city): unknown
省份(region): unknown
国家(country): China
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 218.26.235.157
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13391
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;218.26.235.157. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021700 1800 900 604800 86400
;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 17 18:19:41 CST 2025
;; MSG SIZE rcvd: 107157.235.26.218.in-addr.arpa domain name pointer 157.235.26.218.internet.sx.cn.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
157.235.26.218.in-addr.arpa name = 157.235.26.218.internet.sx.cn.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 75.127.5.72 | attackspambots | (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:48:41 |
| 36.26.64.143 | attackspambots | srv03 Mass scanning activity detected Target: 29085 .. |
2020-04-22 21:06:43 |
| 152.136.165.226 | attack | ... |
2020-04-22 21:12:26 |
| 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 |
| 194.152.206.93 | attackbotsspam | leo_www |
2020-04-22 21:17:21 |
| 122.152.204.104 | attack | Apr 22 13:13:21 nxxxxxxx sshd[3742]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.152.204.104 user=r.r Apr 22 13:13:23 nxxxxxxx sshd[3742]: Failed password for r.r from 122.152.204.104 port 55372 ssh2 Apr 22 13:13:24 nxxxxxxx sshd[3742]: Received disconnect from 122.152.204.104: 11: Bye Bye [preauth] Apr 22 13:18:10 nxxxxxxx sshd[4160]: Invalid user aj from 122.152.204.104 Apr 22 13:18:10 nxxxxxxx sshd[4160]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.152.204.104 Apr 22 13:18:12 nxxxxxxx sshd[4160]: Failed password for invalid user aj from 122.152.204.104 port 49382 ssh2 Apr 22 13:18:12 nxxxxxxx sshd[4160]: Received disconnect from 122.152.204.104: 11: Bye Bye [preauth] Apr 22 13:21:04 nxxxxxxx sshd[4514]: Invalid user joomla from 122.152.204.104 Apr 22 13:21:04 nxxxxxxx sshd[4514]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122......... ------------------------------- |
2020-04-22 21:08:05 |
| 222.186.30.76 | attackbots | 2020-04-22T14:42:39.752963sd-86998 sshd[31623]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.76 user=root 2020-04-22T14:42:41.744054sd-86998 sshd[31623]: Failed password for root from 222.186.30.76 port 37069 ssh2 2020-04-22T14:42:43.907630sd-86998 sshd[31623]: Failed password for root from 222.186.30.76 port 37069 ssh2 2020-04-22T14:42:39.752963sd-86998 sshd[31623]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.76 user=root 2020-04-22T14:42:41.744054sd-86998 sshd[31623]: Failed password for root from 222.186.30.76 port 37069 ssh2 2020-04-22T14:42:43.907630sd-86998 sshd[31623]: Failed password for root from 222.186.30.76 port 37069 ssh2 2020-04-22T14:42:39.752963sd-86998 sshd[31623]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.30.76 user=root 2020-04-22T14:42:41.744054sd-86998 sshd[31623]: Failed password for root from 222.186 ... |
2020-04-22 20:57:38 |
| 81.51.156.171 | attack | Apr 22 12:19:54 localhost sshd\[28128\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.51.156.171 user=root Apr 22 12:19:56 localhost sshd\[28128\]: Failed password for root from 81.51.156.171 port 39386 ssh2 Apr 22 12:33:41 localhost sshd\[28477\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.51.156.171 user=root ... |
2020-04-22 20:59:22 |
| 91.121.211.34 | attackspambots | Apr 22 12:04:32 scw-6657dc sshd[8131]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.121.211.34 Apr 22 12:04:32 scw-6657dc sshd[8131]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.121.211.34 Apr 22 12:04:34 scw-6657dc sshd[8131]: Failed password for invalid user yv from 91.121.211.34 port 55800 ssh2 ... |
2020-04-22 20:52:54 |
| 113.210.150.107 | attackbotsspam | fail2ban |
2020-04-22 20:35:08 |
| 183.106.237.197 | attack | Honeypot attack, port: 81, PTR: PTR record not found |
2020-04-22 20:38:51 |
| 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 |
| 167.172.100.195 | attack | Apr 22 12:40:00 mailrelay sshd[14412]: Invalid user test from 167.172.100.195 port 56140 Apr 22 12:40:00 mailrelay sshd[14412]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.100.195 Apr 22 12:40:02 mailrelay sshd[14412]: Failed password for invalid user test from 167.172.100.195 port 56140 ssh2 Apr 22 12:40:02 mailrelay sshd[14412]: Received disconnect from 167.172.100.195 port 56140:11: Bye Bye [preauth] Apr 22 12:40:02 mailrelay sshd[14412]: Disconnected from 167.172.100.195 port 56140 [preauth] Apr 22 12:51:28 mailrelay sshd[14656]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.100.195 user=r.r Apr 22 12:51:29 mailrelay sshd[14656]: Failed password for r.r from 167.172.100.195 port 35624 ssh2 Apr 22 12:51:29 mailrelay sshd[14656]: Received disconnect from 167.172.100.195 port 35624:11: Bye Bye [preauth] Apr 22 12:51:29 mailrelay sshd[14656]: Disconnected from 167.172......... ------------------------------- |
2020-04-22 21:03:29 |
| 119.28.132.211 | attackspambots | Apr 22 14:04:19 nextcloud sshd\[23433\]: Invalid user is from 119.28.132.211 Apr 22 14:04:19 nextcloud sshd\[23433\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.28.132.211 Apr 22 14:04:21 nextcloud sshd\[23433\]: Failed password for invalid user is from 119.28.132.211 port 44020 ssh2 |
2020-04-22 21:05:50 |
| 222.186.42.137 | attack | Apr 22 14:36:18 vmanager6029 sshd\[6885\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.137 user=root Apr 22 14:36:20 vmanager6029 sshd\[6864\]: error: PAM: Authentication failure for root from 222.186.42.137 Apr 22 14:36:21 vmanager6029 sshd\[6886\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.137 user=root |
2020-04-22 20:37:58 |