城市(city): unknown
省份(region): unknown
国家(country): Indonesia
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 114.121.254.6
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16484
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;114.121.254.6. IN A
;; AUTHORITY SECTION:
. 540 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022030400 1800 900 604800 86400
;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Mar 04 14:48:51 CST 2022
;; MSG SIZE rcvd: 106Host 6.254.121.114.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 6.254.121.114.in-addr.arpa: NXDOMAIN| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 23.95.224.43 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found decubellisfamilychiropractic.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 |
2020-08-15 14:25:42 |
| 170.239.85.39 | attack | Lines containing failures of 170.239.85.39 Aug 13 05:10:30 shared03 sshd[1546]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.239.85.39 user=r.r Aug 13 05:10:33 shared03 sshd[1546]: Failed password for r.r from 170.239.85.39 port 53174 ssh2 Aug 13 05:10:33 shared03 sshd[1546]: Received disconnect from 170.239.85.39 port 53174:11: Bye Bye [preauth] Aug 13 05:10:33 shared03 sshd[1546]: Disconnected from authenticating user r.r 170.239.85.39 port 53174 [preauth] Aug 13 05:13:09 shared03 sshd[2277]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.239.85.39 user=r.r Aug 13 05:13:11 shared03 sshd[2277]: Failed password for r.r from 170.239.85.39 port 55778 ssh2 Aug 13 05:13:12 shared03 sshd[2277]: Received disconnect from 170.239.85.39 port 55778:11 .... truncated .... Lines containing failures of 170.239.85.39 Aug 13 05:10:30 shared03 sshd[1546]: pam_unix(sshd:auth): authentication fa........ ------------------------------ |
2020-08-15 14:37:12 |
| 106.12.173.149 | attackspambots | frenzy |
2020-08-15 14:26:15 |
| 212.33.203.228 | attackspambots | Aug 15 09:02:10 root sshd[26878]: Failed password for invalid user ansible from 212.33.203.228 port 54936 ssh2 ... |
2020-08-15 14:35:08 |
| 72.130.10.216 | attackbots | Port 22 Scan, PTR: None |
2020-08-15 14:31:10 |
| 218.92.0.223 | attack | Fail2Ban Ban Triggered (2) |
2020-08-15 14:28:46 |
| 111.229.136.177 | attackbots | frenzy |
2020-08-15 14:15:26 |
| 23.94.5.52 | attackspambots | (From eric@talkwithwebvisitor.com) Hey, my name’s Eric and for just a second, imagine this… - Someone does a search and winds up at hughesfamilychiro.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.talkwithwebvisitors.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 lea |
2020-08-15 14:31:56 |
| 51.178.41.60 | attackspambots | frenzy |
2020-08-15 14:13:50 |
| 45.32.216.101 | attackspam | 22/tcp [2020-08-15]1pkt |
2020-08-15 14:37:54 |
| 222.186.173.183 | attack | 2020-08-15T09:12:49.880836afi-git.jinr.ru sshd[14511]: Failed password for root from 222.186.173.183 port 27068 ssh2 2020-08-15T09:12:53.090996afi-git.jinr.ru sshd[14511]: Failed password for root from 222.186.173.183 port 27068 ssh2 2020-08-15T09:12:56.376311afi-git.jinr.ru sshd[14511]: Failed password for root from 222.186.173.183 port 27068 ssh2 2020-08-15T09:12:56.376430afi-git.jinr.ru sshd[14511]: error: maximum authentication attempts exceeded for root from 222.186.173.183 port 27068 ssh2 [preauth] 2020-08-15T09:12:56.376444afi-git.jinr.ru sshd[14511]: Disconnecting: Too many authentication failures [preauth] ... |
2020-08-15 14:15:59 |
| 159.89.89.65 | attackbotsspam | frenzy |
2020-08-15 14:32:49 |
| 222.186.42.7 | attack | Aug 15 08:45:56 abendstille sshd\[21796\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.7 user=root Aug 15 08:45:57 abendstille sshd\[21796\]: Failed password for root from 222.186.42.7 port 44503 ssh2 Aug 15 08:46:05 abendstille sshd\[22145\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.7 user=root Aug 15 08:46:08 abendstille sshd\[22145\]: Failed password for root from 222.186.42.7 port 23601 ssh2 Aug 15 08:46:14 abendstille sshd\[22204\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.7 user=root ... |
2020-08-15 14:47:43 |
| 85.209.0.101 | attackspam | Aug 15 08:39:32 db sshd[21214]: User root from 85.209.0.101 not allowed because none of user's groups are listed in AllowGroups ... |
2020-08-15 14:49:12 |
| 101.108.185.43 | attack | Automatic report - Port Scan Attack |
2020-08-15 14:23:42 |