City: unknown
Region: unknown
Country: None
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.21.34.127
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46020
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.21.34.127. IN A
;; AUTHORITY SECTION:
. 395 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022021702 1800 900 604800 86400
;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 08:37:08 CST 2022
;; MSG SIZE rcvd: 106Host 127.34.21.104.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 127.34.21.104.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 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 |
| 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 |
| 5.117.126.86 | attackspambots | 1584369602 - 03/16/2020 15:40:02 Host: 5.117.126.86/5.117.126.86 Port: 445 TCP Blocked |
2020-03-17 03:33:20 |
| 123.17.87.194 | attack | 20/3/16@11:40:32: FAIL: Alarm-Network address from=123.17.87.194 ... |
2020-03-17 03:05:08 |
| 140.127.231.37 | attack | Attempted connection to port 12850. |
2020-03-17 03:04:20 |
| 177.139.177.94 | attack | Attempted connection to port 22. |
2020-03-17 03:12:28 |
| 92.118.37.99 | attackspambots | 03/16/2020-15:18:38.742053 92.118.37.99 Protocol: 6 ET SCAN NMAP -sS window 1024 |
2020-03-17 03:34:29 |
| 34.234.54.252 | attack | lew-Joomla User : try to access forms... |
2020-03-17 03:30:07 |
| 185.176.27.42 | attack | Mar 16 19:29:20 debian-2gb-nbg1-2 kernel: \[6642479.960413\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.42 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=13649 PROTO=TCP SPT=46653 DPT=9252 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-03-17 03:19:12 |
| 45.143.220.28 | attackbotsspam | Automatic report - Banned IP Access |
2020-03-17 03:25:58 |
| 193.124.67.36 | attack | firewall-block, port(s): 1433/tcp |
2020-03-17 03:08:56 |
| 117.202.27.242 | attackspam | Port probing on unauthorized port 445 |
2020-03-17 03:15:47 |
| 38.143.23.66 | attackbots | SpamScore above: 10.0 |
2020-03-17 02:56:43 |
| 159.65.158.30 | attackspam | Mar 16 16:24:43 haigwepa sshd[26864]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.158.30 Mar 16 16:24:45 haigwepa sshd[26864]: Failed password for invalid user ertu from 159.65.158.30 port 45396 ssh2 ... |
2020-03-17 03:07:55 |
| 49.88.112.113 | attackbots | March 16 2020, 19:03:03 [sshd] - Banned from the Cipher Host hosting platform by Fail2ban. |
2020-03-17 03:09:48 |