City: unknown
Region: unknown
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.21.27.74
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 44032
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.21.27.74. IN A
;; AUTHORITY SECTION:
. 230 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022021700 1800 900 604800 86400
;; Query time: 20 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 02:21:07 CST 2022
;; MSG SIZE rcvd: 105Host 74.27.21.104.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 74.27.21.104.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 113.189.46.45 | attackspam | Unauthorized connection attempt detected from IP address 113.189.46.45 to port 445 |
2020-04-22 21:03:59 |
| 103.66.232.47 | attackspam | scan r |
2020-04-22 20:46:58 |
| 68.116.41.6 | attack | no |
2020-04-22 20:36:00 |
| 103.241.5.174 | attackspambots | Sending SPAM email |
2020-04-22 20:24:32 |
| 75.127.5.72 | attackspambots | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found millenniumchiro.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 tha |
2020-04-22 20:48:41 |
| 209.17.96.226 | attack | Automatic report - Banned IP Access |
2020-04-22 20:37:21 |
| 150.109.147.145 | attackbots | Apr 22 04:59:18 mockhub sshd[9459]: Failed password for root from 150.109.147.145 port 49868 ssh2 Apr 22 05:04:59 mockhub sshd[9645]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=150.109.147.145 ... |
2020-04-22 20:29:49 |
| 218.102.55.123 | attack | Honeypot attack, port: 5555, PTR: wtsc5a123.netvigator.com. |
2020-04-22 20:50:34 |
| 36.26.64.143 | attackspambots | srv03 Mass scanning activity detected Target: 29085 .. |
2020-04-22 21:06:43 |
| 134.122.117.242 | attack | Apr 22 14:14:33 meumeu sshd[4781]: Failed password for root from 134.122.117.242 port 33880 ssh2 Apr 22 14:18:24 meumeu sshd[5342]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.122.117.242 Apr 22 14:18:26 meumeu sshd[5342]: Failed password for invalid user ubuntu from 134.122.117.242 port 47560 ssh2 ... |
2020-04-22 20:28:44 |
| 117.172.210.218 | attackspam | Apr 22 14:04:16 hell sshd[20844]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.172.210.218 Apr 22 14:04:18 hell sshd[20844]: Failed password for invalid user test from 117.172.210.218 port 35870 ssh2 ... |
2020-04-22 20:56:04 |
| 111.206.198.92 | attackbots | Bad bot/spoofed identity |
2020-04-22 21:00:10 |
| 123.195.99.9 | attackspam | Apr 22 14:07:02 jane sshd[7029]: Failed password for root from 123.195.99.9 port 40746 ssh2 ... |
2020-04-22 20:58:47 |
| 116.228.37.90 | attackbots | $f2bV_matches |
2020-04-22 21:02:34 |
| 113.210.150.107 | attackbotsspam | fail2ban |
2020-04-22 20:35:08 |