City: unknown
Region: unknown
Country: Japan
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 66.11.54.66
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 8527
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;66.11.54.66. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021100 1800 900 604800 86400
;; Query time: 40 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 11 16:03:25 CST 2025
;; MSG SIZE rcvd: 10466.54.11.66.in-addr.arpa domain name pointer fp420b3642.ap.nuro.jp.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
66.54.11.66.in-addr.arpa name = fp420b3642.ap.nuro.jp.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 59.9.210.52 | attackbotsspam | May 16 22:34:35 santamaria sshd\[29685\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.9.210.52 user=root May 16 22:34:38 santamaria sshd\[29685\]: Failed password for root from 59.9.210.52 port 48946 ssh2 May 16 22:37:53 santamaria sshd\[29710\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.9.210.52 user=root ... |
2020-05-17 04:52:48 |
| 106.13.150.200 | attack | May 16 14:07:36 mailserver sshd\[9136\]: Invalid user test from 106.13.150.200 ... |
2020-05-17 04:19:25 |
| 113.204.205.66 | attack | May 16 20:35:17 scw-6657dc sshd[25354]: Failed password for postfix from 113.204.205.66 port 50242 ssh2 May 16 20:35:17 scw-6657dc sshd[25354]: Failed password for postfix from 113.204.205.66 port 50242 ssh2 May 16 20:37:49 scw-6657dc sshd[25434]: Invalid user demjen from 113.204.205.66 port 30852 ... |
2020-05-17 04:56:25 |
| 64.227.14.137 | attackspam | May 16 15:04:13 ws22vmsma01 sshd[11809]: Failed password for root from 64.227.14.137 port 40640 ssh2 ... |
2020-05-17 04:33:19 |
| 103.81.156.10 | attack | 2020-05-16T20:36:56.406018rocketchat.forhosting.nl sshd[24512]: Failed password for invalid user ins from 103.81.156.10 port 41586 ssh2 2020-05-16T20:41:28.293552rocketchat.forhosting.nl sshd[24581]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.81.156.10 user=root 2020-05-16T20:41:30.337586rocketchat.forhosting.nl sshd[24581]: Failed password for root from 103.81.156.10 port 48452 ssh2 ... |
2020-05-17 04:21:43 |
| 122.51.10.222 | attackspambots | frenzy |
2020-05-17 04:54:14 |
| 23.81.231.221 | attackspam | (From eric@talkwithwebvisitor.com) Cool website! My name’s Eric, and I just found your site - ringgoldchiropractic.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 ringgoldchiropractic.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-05-17 04:44:10 |
| 95.85.9.94 | attack | May 16 21:54:16 srv01 sshd[6333]: Invalid user imc from 95.85.9.94 port 39528 May 16 21:54:16 srv01 sshd[6333]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.85.9.94 May 16 21:54:16 srv01 sshd[6333]: Invalid user imc from 95.85.9.94 port 39528 May 16 21:54:19 srv01 sshd[6333]: Failed password for invalid user imc from 95.85.9.94 port 39528 ssh2 May 16 22:01:51 srv01 sshd[6507]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.85.9.94 user=root May 16 22:01:53 srv01 sshd[6507]: Failed password for root from 95.85.9.94 port 44066 ssh2 ... |
2020-05-17 04:30:42 |
| 85.105.154.118 | attackbots | Automatic report - Port Scan Attack |
2020-05-17 04:56:50 |
| 45.95.168.124 | attackspam | May 16 20:11:40 debian-2gb-nbg1-2 kernel: \[11911543.744382\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=45.95.168.124 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=242 ID=54321 PROTO=TCP SPT=45074 DPT=8088 WINDOW=65535 RES=0x00 SYN URGP=0 |
2020-05-17 04:33:52 |
| 103.200.21.242 | attackbotsspam | Port probing on unauthorized port 1433 |
2020-05-17 04:24:44 |
| 1.23.146.66 | attackspambots | Portscan - Unauthorized connection attempt |
2020-05-17 04:15:22 |
| 178.128.217.58 | attackbotsspam | May 16 22:35:26 jane sshd[16349]: Failed password for root from 178.128.217.58 port 45844 ssh2 ... |
2020-05-17 04:49:23 |
| 198.12.118.140 | attackbots | (From eric@talkwithwebvisitor.com) Cool website! My name’s Eric, and I just found your site - ringgoldchiropractic.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 ringgoldchiropractic.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-05-17 04:44:56 |
| 177.85.24.229 | attackspam | 20/5/16@08:07:39: FAIL: Alarm-Network address from=177.85.24.229 20/5/16@08:07:39: FAIL: Alarm-Network address from=177.85.24.229 ... |
2020-05-17 04:20:28 |