城市(city): unknown
省份(region): unknown
国家(country): Australia
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 23.40.161.11
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28870
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;23.40.161.11. IN A
;; AUTHORITY SECTION:
. 29 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020602 1800 900 604800 86400
;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 07 08:52:11 CST 2025
;; MSG SIZE rcvd: 10511.161.40.23.in-addr.arpa domain name pointer a23-40-161-11.deploy.static.akamaitechnologies.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
11.161.40.23.in-addr.arpa name = a23-40-161-11.deploy.static.akamaitechnologies.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 136.49.109.217 | attackspam | Aug 11 17:35:50 host sshd\[13036\]: Invalid user vpsco1212 from 136.49.109.217 Aug 11 17:35:50 host sshd\[13036\]: Failed password for invalid user vpsco1212 from 136.49.109.217 port 49702 ssh2 Aug 11 17:39:22 host sshd\[13216\]: Invalid user 2WSXZAQ1 from 136.49.109.217 Aug 11 17:39:22 host sshd\[13216\]: Failed password for invalid user 2WSXZAQ1 from 136.49.109.217 port 60008 ssh2 ... |
2020-08-12 06:53:06 |
| 23.90.29.129 | attackbotsspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found sordillochiropracticcentre.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 s |
2020-08-12 06:40:37 |
| 35.186.145.141 | attackbotsspam | Aug 11 22:25:17 serwer sshd\[1873\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.186.145.141 user=root Aug 11 22:25:19 serwer sshd\[1873\]: Failed password for root from 35.186.145.141 port 55102 ssh2 Aug 11 22:34:46 serwer sshd\[2676\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.186.145.141 user=root ... |
2020-08-12 07:15:22 |
| 91.240.118.113 | attack | 3394/tcp 3399/tcp 3395/tcp... [2020-06-17/08-11]327pkt,14pt.(tcp) |
2020-08-12 07:00:28 |
| 219.118.146.175 | attack | Port Scan ... |
2020-08-12 07:00:51 |
| 117.50.101.117 | attack | 27017/tcp 25565/tcp 3128/tcp... [2020-06-12/08-11]60pkt,18pt.(tcp) |
2020-08-12 07:08:29 |
| 34.220.48.101 | attack | IP 34.220.48.101 attacked honeypot on port: 4444 at 8/11/2020 1:34:16 PM |
2020-08-12 07:00:09 |
| 182.254.149.130 | attackbotsspam | Aug 11 18:41:35 firewall sshd[17074]: Failed password for root from 182.254.149.130 port 54829 ssh2 Aug 11 18:45:49 firewall sshd[17206]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.254.149.130 user=root Aug 11 18:45:50 firewall sshd[17206]: Failed password for root from 182.254.149.130 port 59126 ssh2 ... |
2020-08-12 06:51:31 |
| 182.61.40.252 | attack | Failed password for root from 182.61.40.252 port 53212 ssh2 pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.40.252 user=root Failed password for root from 182.61.40.252 port 58900 ssh2 pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.40.252 user=root Failed password for root from 182.61.40.252 port 36364 ssh2 |
2020-08-12 06:54:29 |
| 192.241.236.133 | attack | 1597185906 - 08/12/2020 00:45:06 Host: 192.241.236.133/192.241.236.133 Port: 771 TCP Blocked ... |
2020-08-12 07:01:30 |
| 117.103.2.114 | attackbots | "$f2bV_matches" |
2020-08-12 06:59:02 |
| 112.85.42.180 | attackspambots | Aug 12 00:35:14 cosmoit sshd[4648]: Failed password for root from 112.85.42.180 port 12410 ssh2 |
2020-08-12 06:52:37 |
| 36.111.47.193 | attackbotsspam | 12166/tcp 10456/tcp 2733/tcp... [2020-06-23/08-11]14pkt,13pt.(tcp) |
2020-08-12 07:05:26 |
| 103.254.94.19 | attackspam | Automatic report - Port Scan |
2020-08-12 07:13:35 |
| 110.88.160.179 | attack | 2020-08-11T17:33:26.7849461495-001 sshd[35403]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.88.160.179 user=root 2020-08-11T17:33:28.7012011495-001 sshd[35403]: Failed password for root from 110.88.160.179 port 43780 ssh2 2020-08-11T17:39:03.3005131495-001 sshd[35635]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.88.160.179 user=root 2020-08-11T17:39:05.4821711495-001 sshd[35635]: Failed password for root from 110.88.160.179 port 48468 ssh2 2020-08-11T17:44:40.9373301495-001 sshd[35922]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.88.160.179 user=root 2020-08-11T17:44:42.7176631495-001 sshd[35922]: Failed password for root from 110.88.160.179 port 53168 ssh2 ... |
2020-08-12 07:08:41 |