城市(city): unknown
省份(region): unknown
国家(country): United States of America (the)
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 209.195.159.81
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 61163
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;209.195.159.81. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021100 1800 900 604800 86400
;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 11 16:09:16 CST 2025
;; MSG SIZE rcvd: 10781.159.195.209.in-addr.arpa domain name pointer 16.cuvl2.xdsl.nauticom.net.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
81.159.195.209.in-addr.arpa name = 16.cuvl2.xdsl.nauticom.net.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 104.244.78.197 | attack | k+ssh-bruteforce |
2020-03-17 03:01:11 |
| 78.186.2.74 | attackspambots | DIS,DEF GET /shell?busybox |
2020-03-17 02:54:30 |
| 23.83.179.123 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found alicebehrchiropractic.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-03-17 03:24:40 |
| 140.127.231.37 | attack | Attempted connection to port 12850. |
2020-03-17 03:04:20 |
| 121.199.37.87 | attackbotsspam | SMTP |
2020-03-17 03:24:23 |
| 52.183.136.248 | attackbotsspam | Mar 16 15:40:55 iago sshd[27663]: Invalid user tinkerware from 52.183.136.248 Mar 16 15:40:55 iago sshd[27663]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.183.136.248 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=52.183.136.248 |
2020-03-17 02:56:01 |
| 176.113.115.43 | attackbots | Mar 16 15:40:55 debian-2gb-nbg1-2 kernel: \[6628775.647790\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=176.113.115.43 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=1243 PROTO=TCP SPT=55468 DPT=3392 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-03-17 02:54:11 |
| 107.172.52.118 | attack | (From eric@talkwithwebvisitor.com) Cool website! My name’s Eric, and I just found your site - bennettchiro.net - while surfing the net. You showed up at the top of the search results, so I checked you out. Looks like what you’re doing is pretty cool. But if you don’t mind me asking – after someone like me stumbles across bennettchiro.net, what usually happens? Is your site generating leads for your business? I’m guessing some, but I also bet you’d like more… studies show that 7 out 10 who land on a site wind up leaving without a trace. Not good. Here’s a thought – what if there was an easy way for every visitor to “raise their hand” to get a phone call from you INSTANTLY… the second they hit your site and said, “call me now.” You can – Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number. It lets you know IMMEDIATELY – so that you can talk to that lead while they’re literally looking over your si |
2020-03-17 03:30:35 |
| 63.245.45.135 | attack | Mar 16 15:36:16 web8 sshd\[17624\]: Invalid user testsftp from 63.245.45.135 Mar 16 15:36:16 web8 sshd\[17624\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=63.245.45.135 Mar 16 15:36:18 web8 sshd\[17624\]: Failed password for invalid user testsftp from 63.245.45.135 port 38415 ssh2 Mar 16 15:39:10 web8 sshd\[19027\]: Invalid user teamspeak from 63.245.45.135 Mar 16 15:39:10 web8 sshd\[19027\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=63.245.45.135 |
2020-03-17 03:18:01 |
| 46.38.145.164 | attackbotsspam | Mar 16 19:54:59 relay postfix/smtpd\[11599\]: warning: unknown\[46.38.145.164\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Mar 16 19:55:05 relay postfix/smtpd\[11599\]: warning: unknown\[46.38.145.164\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Mar 16 19:55:15 relay postfix/smtpd\[11599\]: warning: unknown\[46.38.145.164\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Mar 16 20:00:19 relay postfix/smtpd\[4989\]: warning: unknown\[46.38.145.164\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Mar 16 20:00:25 relay postfix/smtpd\[4989\]: warning: unknown\[46.38.145.164\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-03-17 03:23:26 |
| 49.48.222.12 | attackbots | 1584369604 - 03/16/2020 15:40:04 Host: 49.48.222.12/49.48.222.12 Port: 445 TCP Blocked |
2020-03-17 03:25:30 |
| 91.226.79.134 | attack | firewall-block, port(s): 23/tcp |
2020-03-17 03:35:31 |
| 94.176.66.188 | attack | Automatic report - Port Scan Attack |
2020-03-17 03:22:34 |
| 89.248.168.202 | attackspam | ET CINS Active Threat Intelligence Poor Reputation IP group 82 - port: 1980 proto: TCP cat: Misc Attack |
2020-03-17 03:16:10 |
| 14.175.51.107 | attackbotsspam | Attempt to attack host OS, exploiting network vulnerabilities, on 16-03-2020 14:40:10. |
2020-03-17 03:31:25 |