City: unknown
Region: unknown
Country: Japan
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 54.199.38.12
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 31924
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;54.199.38.12. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012001 1800 900 604800 86400
;; Query time: 39 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 21 11:11:32 CST 2025
;; MSG SIZE rcvd: 10512.38.199.54.in-addr.arpa domain name pointer ec2-54-199-38-12.ap-northeast-1.compute.amazonaws.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
12.38.199.54.in-addr.arpa name = ec2-54-199-38-12.ap-northeast-1.compute.amazonaws.com.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 45.152.34.51 | attackbotsspam | (From eric@talkwithwebvisitor.com) Cool website! My name’s Eric, and I just found your site - newlifechiropracticcenter.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 newlifechiropracticcenter.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 lite |
2020-03-09 20:55:12 |
| 110.227.216.32 | attackbots | Unauthorized connection attempt from IP address 110.227.216.32 on Port 445(SMB) |
2020-03-09 21:12:09 |
| 188.166.159.148 | attackbots | Mar 9 13:31:46 host sshd[29066]: Invalid user bwadmin from 188.166.159.148 port 56102 ... |
2020-03-09 20:44:30 |
| 222.186.52.78 | attack | Mar 9 13:30:37 * sshd[12000]: Failed password for root from 222.186.52.78 port 19163 ssh2 |
2020-03-09 20:44:00 |
| 64.227.70.114 | attack | Mar 9 13:16:54 XXX sshd[16349]: Invalid user ubnt from 64.227.70.114 port 41418 |
2020-03-09 21:15:35 |
| 180.104.21.137 | attackspambots | Email rejected due to spam filtering |
2020-03-09 20:39:48 |
| 41.208.150.114 | attackbots | 2020-03-09T13:26:05.080638vps751288.ovh.net sshd\[1444\]: Invalid user informix from 41.208.150.114 port 48934 2020-03-09T13:26:05.093368vps751288.ovh.net sshd\[1444\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.208.150.114 2020-03-09T13:26:06.491448vps751288.ovh.net sshd\[1444\]: Failed password for invalid user informix from 41.208.150.114 port 48934 ssh2 2020-03-09T13:32:28.040061vps751288.ovh.net sshd\[1463\]: Invalid user yala from 41.208.150.114 port 41705 2020-03-09T13:32:28.050023vps751288.ovh.net sshd\[1463\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.208.150.114 |
2020-03-09 20:50:41 |
| 222.186.175.167 | attackspambots | Mar 9 13:57:01 SilenceServices sshd[13944]: Failed password for root from 222.186.175.167 port 58478 ssh2 Mar 9 13:57:14 SilenceServices sshd[13944]: error: maximum authentication attempts exceeded for root from 222.186.175.167 port 58478 ssh2 [preauth] Mar 9 13:57:20 SilenceServices sshd[14056]: Failed password for root from 222.186.175.167 port 42812 ssh2 |
2020-03-09 20:57:59 |
| 175.213.185.129 | attackbots | $f2bV_matches |
2020-03-09 20:48:17 |
| 202.88.252.53 | attack | Mar 9 13:43:03 srv01 sshd[9736]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.88.252.53 user=root Mar 9 13:43:05 srv01 sshd[9736]: Failed password for root from 202.88.252.53 port 42567 ssh2 Mar 9 13:45:28 srv01 sshd[9985]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.88.252.53 user=root Mar 9 13:45:31 srv01 sshd[9985]: Failed password for root from 202.88.252.53 port 24334 ssh2 Mar 9 13:47:51 srv01 sshd[10111]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.88.252.53 user=root Mar 9 13:47:53 srv01 sshd[10111]: Failed password for root from 202.88.252.53 port 34182 ssh2 ... |
2020-03-09 21:13:56 |
| 103.29.69.96 | attack | Fail2Ban Ban Triggered |
2020-03-09 21:13:39 |
| 183.88.168.160 | attackspam | Unauthorized connection attempt from IP address 183.88.168.160 on Port 445(SMB) |
2020-03-09 20:41:23 |
| 190.201.124.91 | attackspambots | Unauthorized connection attempt from IP address 190.201.124.91 on Port 445(SMB) |
2020-03-09 21:10:32 |
| 49.235.81.23 | attack | SSH authentication failure x 6 reported by Fail2Ban ... |
2020-03-09 20:47:01 |
| 218.92.0.138 | attack | Mar 9 02:50:22 wbs sshd\[12024\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.138 user=root Mar 9 02:50:24 wbs sshd\[12024\]: Failed password for root from 218.92.0.138 port 9341 ssh2 Mar 9 02:50:34 wbs sshd\[12024\]: Failed password for root from 218.92.0.138 port 9341 ssh2 Mar 9 02:50:37 wbs sshd\[12024\]: Failed password for root from 218.92.0.138 port 9341 ssh2 Mar 9 02:50:42 wbs sshd\[12039\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.138 user=root |
2020-03-09 20:58:54 |