城市(city): unknown
省份(region): unknown
国家(country): None
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 197.41.81.85
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 28904
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;197.41.81.85. IN A
;; AUTHORITY SECTION:
. 376 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022021301 1800 900 604800 86400
;; Query time: 64 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 14 11:18:08 CST 2022
;; MSG SIZE rcvd: 10585.81.41.197.in-addr.arpa domain name pointer host-197.41.81.85.tedata.net.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
85.81.41.197.in-addr.arpa name = host-197.41.81.85.tedata.net.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 106.13.120.224 | attack | 2020-06-14T12:28:08.290755randservbullet-proofcloud-66.localdomain sshd[13922]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.120.224 user=root 2020-06-14T12:28:10.116700randservbullet-proofcloud-66.localdomain sshd[13922]: Failed password for root from 106.13.120.224 port 47142 ssh2 2020-06-14T12:42:53.391837randservbullet-proofcloud-66.localdomain sshd[13989]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.120.224 user=root 2020-06-14T12:42:55.377698randservbullet-proofcloud-66.localdomain sshd[13989]: Failed password for root from 106.13.120.224 port 43848 ssh2 ... |
2020-06-15 04:48:37 |
| 200.92.102.203 | attack | fail2ban -- 200.92.102.203 ... |
2020-06-15 04:22:11 |
| 206.253.167.205 | attackspambots | Jun 14 20:08:13 ns392434 sshd[20724]: Invalid user suporte from 206.253.167.205 port 44012 Jun 14 20:08:13 ns392434 sshd[20724]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.253.167.205 Jun 14 20:08:13 ns392434 sshd[20724]: Invalid user suporte from 206.253.167.205 port 44012 Jun 14 20:08:15 ns392434 sshd[20724]: Failed password for invalid user suporte from 206.253.167.205 port 44012 ssh2 Jun 14 20:15:04 ns392434 sshd[20949]: Invalid user qi from 206.253.167.205 port 56048 Jun 14 20:15:04 ns392434 sshd[20949]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.253.167.205 Jun 14 20:15:04 ns392434 sshd[20949]: Invalid user qi from 206.253.167.205 port 56048 Jun 14 20:15:06 ns392434 sshd[20949]: Failed password for invalid user qi from 206.253.167.205 port 56048 ssh2 Jun 14 20:17:23 ns392434 sshd[21077]: Invalid user hours from 206.253.167.205 port 43378 |
2020-06-15 04:47:07 |
| 120.35.26.129 | attackbots | SSH Brute-Force. Ports scanning. |
2020-06-15 04:19:57 |
| 79.130.152.21 | attackbots | Automatic report - Port Scan Attack |
2020-06-15 04:42:32 |
| 52.44.26.206 | attack | web-1 [ssh] SSH Attack |
2020-06-15 04:49:10 |
| 66.150.71.224 | attackbots | (From eric@talkwithwebvisitor.com) Hey, my name’s Eric and for just a second, imagine this… - Someone does a search and winds up at lauxchiropractic.com. - They hang out for a minute to check it out. “I’m interested… but… maybe…” - And then they hit the back button and check out the other search results instead. - Bottom line – you got an eyeball, but nothing else to show for it. - There they go. This isn’t really your fault – it happens a LOT – studies show 7 out of 10 visitors to any site disappear without leaving a trace. But you CAN fix that. 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 right then and there – enabling you to call that lead while they’re literally looking over your site. CLICK HERE http://www.talkwithwebvisitor.com to try out a Live Demo with Talk With Web Visitor now to see exactly how it works. Time is money when it comes to connecting with leads |
2020-06-15 04:39:37 |
| 35.199.73.100 | attackspam | Jun 14 22:37:22 meumeu sshd[509585]: Invalid user ub from 35.199.73.100 port 34784 Jun 14 22:37:22 meumeu sshd[509585]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.199.73.100 Jun 14 22:37:22 meumeu sshd[509585]: Invalid user ub from 35.199.73.100 port 34784 Jun 14 22:37:24 meumeu sshd[509585]: Failed password for invalid user ub from 35.199.73.100 port 34784 ssh2 Jun 14 22:38:14 meumeu sshd[509676]: Invalid user taller from 35.199.73.100 port 46696 Jun 14 22:38:14 meumeu sshd[509676]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.199.73.100 Jun 14 22:38:14 meumeu sshd[509676]: Invalid user taller from 35.199.73.100 port 46696 Jun 14 22:38:16 meumeu sshd[509676]: Failed password for invalid user taller from 35.199.73.100 port 46696 ssh2 Jun 14 22:39:05 meumeu sshd[509790]: Invalid user charity from 35.199.73.100 port 58644 ... |
2020-06-15 04:43:47 |
| 49.232.165.42 | attack | 2020-06-14T23:16:49.700215lavrinenko.info sshd[29351]: Failed password for root from 49.232.165.42 port 54502 ssh2 2020-06-14T23:19:55.479915lavrinenko.info sshd[29668]: Invalid user sales1 from 49.232.165.42 port 33638 2020-06-14T23:19:55.485474lavrinenko.info sshd[29668]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.165.42 2020-06-14T23:19:55.479915lavrinenko.info sshd[29668]: Invalid user sales1 from 49.232.165.42 port 33638 2020-06-14T23:19:57.368256lavrinenko.info sshd[29668]: Failed password for invalid user sales1 from 49.232.165.42 port 33638 ssh2 ... |
2020-06-15 04:29:44 |
| 72.11.135.222 | attack | Jun 14 22:42:41 WHD8 postfix/smtpd\[40465\]: warning: unknown\[72.11.135.222\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jun 14 22:42:48 WHD8 postfix/smtpd\[40465\]: warning: unknown\[72.11.135.222\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Jun 14 22:42:59 WHD8 postfix/smtpd\[40465\]: warning: unknown\[72.11.135.222\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ... |
2020-06-15 04:52:05 |
| 54.38.241.162 | attackbots | Jun 14 14:41:04 nas sshd[16825]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.38.241.162 Jun 14 14:41:06 nas sshd[16825]: Failed password for invalid user zili from 54.38.241.162 port 42732 ssh2 Jun 14 14:43:05 nas sshd[16858]: Failed password for root from 54.38.241.162 port 35262 ssh2 ... |
2020-06-15 04:40:08 |
| 38.111.144.139 | attackspam | Automated report (2020-06-14T22:24:23+08:00). Faked user agent detected. |
2020-06-15 04:21:27 |
| 119.29.173.247 | attackbots | Jun 14 15:49:16 piServer sshd[20184]: Failed password for root from 119.29.173.247 port 56536 ssh2 Jun 14 15:52:55 piServer sshd[20484]: Failed password for root from 119.29.173.247 port 36152 ssh2 Jun 14 15:56:44 piServer sshd[20770]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.173.247 ... |
2020-06-15 04:51:17 |
| 45.141.84.30 | attack | Jun 14 22:34:29 debian-2gb-nbg1-2 kernel: \[14425580.048457\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=45.141.84.30 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=40908 PROTO=TCP SPT=50749 DPT=577 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-06-15 04:37:21 |
| 179.61.132.206 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found drtomalin.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 that can |
2020-06-15 04:30:30 |