City: unknown
Region: unknown
Country: Australia
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 1.131.45.85
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 18948
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;1.131.45.85. IN A
;; AUTHORITY SECTION:
. 3600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019090701 1800 900 604800 86400
;; Query time: 2 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Sun Sep 08 03:20:22 CST 2019
;; MSG SIZE rcvd: 115Host 85.45.131.1.in-addr.arpa. not found: 3(NXDOMAIN)Server: 67.207.67.2
Address: 67.207.67.2#53
** server can't find 85.45.131.1.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 194.26.25.97 | attack | Multiport scan : 43 ports scanned 58 221 292 322 442 565 710 939 1876 1891 1901 2025 2552 2795 4894 5435 5671 6336 8990 9222 9351 9456 9585 9769 12124 13022 13135 13226 14145 14444 14725 18586 19495 19756 20726 21216 21439 22021 22227 24445 26914 31112 32122 |
2020-09-05 07:12:45 |
| 154.70.208.66 | attack | Sep 5 00:01:35 haigwepa sshd[32486]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=154.70.208.66 Sep 5 00:01:37 haigwepa sshd[32486]: Failed password for invalid user dp from 154.70.208.66 port 49078 ssh2 ... |
2020-09-05 06:52:39 |
| 195.54.160.180 | attackspam | 2020-09-04T17:15:50.893333correo.[domain] sshd[35756]: Invalid user effectuate from 195.54.160.180 port 29630 2020-09-04T17:15:53.113747correo.[domain] sshd[35756]: Failed password for invalid user effectuate from 195.54.160.180 port 29630 ssh2 2020-09-04T17:15:53.810523correo.[domain] sshd[35759]: Invalid user fiberfix from 195.54.160.180 port 36605 ... |
2020-09-05 07:14:54 |
| 185.225.136.37 | 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 drlesliechiro.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 leads – |
2020-09-05 07:09:31 |
| 220.134.169.119 | attackspam | [N10.H2.VM2] Port Scanner Detected Blocked by UFW |
2020-09-05 07:03:13 |
| 198.23.250.38 | attackbots | (From eric@talkwithwebvisitor.com) Cool website! My name’s Eric, and I just found your site - myvenicechiropractor.com - 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 myvenicechiropractor.com, 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 look |
2020-09-05 07:03:38 |
| 159.65.155.255 | attack | SSH Invalid Login |
2020-09-05 07:21:34 |
| 212.129.16.53 | attackbotsspam | Sep 5 00:50:20 eventyay sshd[24352]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.129.16.53 Sep 5 00:50:21 eventyay sshd[24352]: Failed password for invalid user nfe from 212.129.16.53 port 33196 ssh2 Sep 5 00:53:37 eventyay sshd[24482]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=212.129.16.53 ... |
2020-09-05 07:08:09 |
| 183.194.212.16 | attackspambots | Sep 4 23:40:39 vps sshd[20024]: Failed password for git from 183.194.212.16 port 48468 ssh2 Sep 4 23:55:53 vps sshd[20711]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.194.212.16 Sep 4 23:55:55 vps sshd[20711]: Failed password for invalid user integra from 183.194.212.16 port 35680 ssh2 ... |
2020-09-05 07:15:47 |
| 211.34.252.96 | attack | Honeypot attack, port: 81, PTR: PTR record not found |
2020-09-05 06:58:58 |
| 78.28.233.52 | attack | Honeypot attack, port: 445, PTR: PTR record not found |
2020-09-05 07:07:15 |
| 183.129.146.18 | attackspambots | Sep 5 sshd[25071]: Invalid user adsl from 183.129.146.18 port 10297 |
2020-09-05 07:28:53 |
| 143.202.209.47 | attackbots | fail2ban -- 143.202.209.47 ... |
2020-09-05 07:11:43 |
| 191.233.199.68 | attackbots | " " |
2020-09-05 07:28:23 |
| 51.75.123.7 | attack | "XSS Attack Detected via libinjection - Matched Data: XSS data found within ARGS_NAMES: |
2020-09-05 07:18:20 |