City: unknown
Region: unknown
Country: None
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 140.116.207.55
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 64015
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;140.116.207.55. IN A
;; AUTHORITY SECTION:
. 423 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019103101 1800 900 604800 86400
;; Query time: 197 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Nov 01 07:16:31 CST 2019
;; MSG SIZE rcvd: 11855.207.116.140.in-addr.arpa domain name pointer news.lib.ncku.edu.tw.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
55.207.116.140.in-addr.arpa name = news.lib.ncku.edu.tw.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 41.80.78.74 | attack | Brute forcing RDP port 3389 |
2020-06-15 04:25:57 |
| 176.31.255.63 | attackbotsspam | 2020-06-14 14:03:58.310788-0500 localhost sshd[67357]: Failed password for invalid user mohamed from 176.31.255.63 port 52006 ssh2 |
2020-06-15 04:44:27 |
| 179.61.132.206 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found drtomalin.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 that can |
2020-06-15 04:30:30 |
| 106.12.194.204 | attack | Jun 14 15:05:25 django-0 sshd\[31284\]: Failed password for root from 106.12.194.204 port 41856 ssh2Jun 14 15:08:09 django-0 sshd\[31338\]: Failed password for root from 106.12.194.204 port 43130 ssh2Jun 14 15:11:04 django-0 sshd\[31370\]: Failed password for root from 106.12.194.204 port 44400 ssh2 ... |
2020-06-15 04:50:52 |
| 187.5.3.56 | attack | Jun 14 12:42:37 ws26vmsma01 sshd[95451]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.5.3.56 Jun 14 12:42:39 ws26vmsma01 sshd[95451]: Failed password for invalid user zena from 187.5.3.56 port 49336 ssh2 ... |
2020-06-15 04:56:56 |
| 211.159.150.41 | attack | Jun 14 10:28:09 pixelmemory sshd[3640714]: Failed password for invalid user tyr from 211.159.150.41 port 57648 ssh2 Jun 14 10:31:13 pixelmemory sshd[3645556]: Invalid user jose from 211.159.150.41 port 36858 Jun 14 10:31:13 pixelmemory sshd[3645556]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.159.150.41 Jun 14 10:31:13 pixelmemory sshd[3645556]: Invalid user jose from 211.159.150.41 port 36858 Jun 14 10:31:15 pixelmemory sshd[3645556]: Failed password for invalid user jose from 211.159.150.41 port 36858 ssh2 ... |
2020-06-15 04:54:52 |
| 91.134.157.246 | attack | SSH Brute-Force Attack |
2020-06-15 04:27:08 |
| 222.186.31.83 | attack | 2020-06-14T20:22:50.887029mail.csmailer.org sshd[29315]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.83 user=root 2020-06-14T20:22:53.462232mail.csmailer.org sshd[29315]: Failed password for root from 222.186.31.83 port 11334 ssh2 2020-06-14T20:22:50.887029mail.csmailer.org sshd[29315]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.83 user=root 2020-06-14T20:22:53.462232mail.csmailer.org sshd[29315]: Failed password for root from 222.186.31.83 port 11334 ssh2 2020-06-14T20:22:55.351087mail.csmailer.org sshd[29315]: Failed password for root from 222.186.31.83 port 11334 ssh2 ... |
2020-06-15 04:26:37 |
| 61.62.72.91 | attack | Unauthorised access (Jun 14) SRC=61.62.72.91 LEN=40 TTL=52 ID=17047 TCP DPT=23 WINDOW=3273 SYN |
2020-06-15 04:28:36 |
| 52.80.20.135 | attackspam | "XSS Attack Detected via libinjection - Matched Data: XSS data found within ARGS_NAMES: |
2020-06-15 04:27:53 |
| 139.198.5.79 | attackspam | 2020-06-14T18:22:20.389084abusebot.cloudsearch.cf sshd[27854]: Invalid user wallace from 139.198.5.79 port 33748 2020-06-14T18:22:20.394765abusebot.cloudsearch.cf sshd[27854]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.198.5.79 2020-06-14T18:22:20.389084abusebot.cloudsearch.cf sshd[27854]: Invalid user wallace from 139.198.5.79 port 33748 2020-06-14T18:22:23.081606abusebot.cloudsearch.cf sshd[27854]: Failed password for invalid user wallace from 139.198.5.79 port 33748 ssh2 2020-06-14T18:25:28.726874abusebot.cloudsearch.cf sshd[28085]: Invalid user cym from 139.198.5.79 port 55542 2020-06-14T18:25:28.732257abusebot.cloudsearch.cf sshd[28085]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.198.5.79 2020-06-14T18:25:28.726874abusebot.cloudsearch.cf sshd[28085]: Invalid user cym from 139.198.5.79 port 55542 2020-06-14T18:25:30.560987abusebot.cloudsearch.cf sshd[28085]: Failed password for invalid ... |
2020-06-15 04:44:52 |
| 79.130.152.21 | attackbots | Automatic report - Port Scan Attack |
2020-06-15 04:42:32 |
| 175.207.13.22 | attackspam | Jun 14 16:06:35 buvik sshd[22557]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=175.207.13.22 Jun 14 16:06:37 buvik sshd[22557]: Failed password for invalid user vietnam from 175.207.13.22 port 53586 ssh2 Jun 14 16:10:23 buvik sshd[23096]: Invalid user th from 175.207.13.22 ... |
2020-06-15 04:46:47 |
| 220.100.130.78 | attackbots | Trying to IMAP sync remote attack email |
2020-06-15 04:54:31 |
| 5.157.17.60 | attackbots | Unauthorized access detected from black listed ip! |
2020-06-15 04:57:23 |