城市(city): unknown
省份(region): unknown
国家(country): Austria
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 62.218.91.20
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 18261
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;62.218.91.20. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012201 1800 900 604800 86400
;; Query time: 12 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 23 04:20:26 CST 2025
;; MSG SIZE rcvd: 10520.91.218.62.in-addr.arpa domain name pointer linzu4-91-20.utaonline.at.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
20.91.218.62.in-addr.arpa name = linzu4-91-20.utaonline.at.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 148.66.145.42 | attackspam | Wordpress_xmlrpc_attack |
2020-03-22 22:45:09 |
| 189.15.202.177 | attackbots | Automatic report - Port Scan Attack |
2020-03-22 23:10:05 |
| 106.12.123.239 | attackbotsspam | Mar 22 14:01:30 |
2020-03-22 22:48:15 |
| 45.152.34.11 | attackspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found middletonchiropractic.net 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-03-22 23:17:37 |
| 122.121.70.204 | attackbotsspam | Unauthorized connection attempt from IP address 122.121.70.204 on Port 445(SMB) |
2020-03-22 22:56:17 |
| 148.72.232.53 | attackspam | Wordpress_xmlrpc_attack |
2020-03-22 22:43:38 |
| 95.52.252.96 | attack | Unauthorized connection attempt from IP address 95.52.252.96 on Port 445(SMB) |
2020-03-22 23:23:34 |
| 95.168.118.4 | attackspam | F2B blocked SSH BF |
2020-03-22 22:39:47 |
| 45.134.179.240 | attack | Mar 22 14:01:22 debian-2gb-nbg1-2 kernel: \[7141175.950585\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=45.134.179.240 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=27694 PROTO=TCP SPT=45169 DPT=4400 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-03-22 23:29:05 |
| 93.88.176.27 | attackspambots | 2020-03-22T13:47:29.230785rocketchat.forhosting.nl sshd[14348]: Invalid user ts4 from 93.88.176.27 port 44988 2020-03-22T13:47:31.031679rocketchat.forhosting.nl sshd[14348]: Failed password for invalid user ts4 from 93.88.176.27 port 44988 ssh2 2020-03-22T14:01:43.806676rocketchat.forhosting.nl sshd[14484]: Invalid user deffer from 93.88.176.27 port 35098 ... |
2020-03-22 23:11:49 |
| 203.128.83.213 | attackbotsspam | Unauthorized connection attempt from IP address 203.128.83.213 on Port 445(SMB) |
2020-03-22 23:20:07 |
| 217.111.239.37 | attackbots | Mar 22 16:00:14 lukav-desktop sshd\[6546\]: Invalid user onie from 217.111.239.37 Mar 22 16:00:14 lukav-desktop sshd\[6546\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.111.239.37 Mar 22 16:00:17 lukav-desktop sshd\[6546\]: Failed password for invalid user onie from 217.111.239.37 port 33260 ssh2 Mar 22 16:04:08 lukav-desktop sshd\[11495\]: Invalid user www1 from 217.111.239.37 Mar 22 16:04:08 lukav-desktop sshd\[11495\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.111.239.37 |
2020-03-22 22:38:49 |
| 106.53.33.77 | attackbots | SSH brute-force attempt |
2020-03-22 22:36:14 |
| 222.186.170.77 | attackbots | Unauthorized connection attempt detected from IP address 222.186.170.77 to port 8007 |
2020-03-22 23:01:23 |
| 42.118.254.239 | attackspam | Unauthorized connection attempt from IP address 42.118.254.239 on Port 445(SMB) |
2020-03-22 22:51:13 |