城市(city): Jakarta
省份(region): Jakarta
国家(country): Indonesia
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.193.26.92
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 5439
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;139.193.26.92. IN A
;; AUTHORITY SECTION:
. 507 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2020081302 1800 900 604800 86400
;; Query time: 81 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Aug 14 07:21:02 CST 2020
;; MSG SIZE rcvd: 117
92.26.193.139.in-addr.arpa domain name pointer fm-dyn-139-193-26-92.fast.net.id.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
92.26.193.139.in-addr.arpa name = fm-dyn-139-193-26-92.fast.net.id.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 104.203.102.205 | attack | (From eric@talkwithwebvisitor.com) Good day, My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations What for? Part of my job is to check out websites and the work you’ve done with advancedchirosolutions.com definitely stands out. It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality. There is, however, a catch… more accurately, a question… So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know? More importantly, how do you make a connection with that person? Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind. Here’s a way to create INSTANT engagement that you may not have known about… Talk With Web Visitor is a software widget that’s works on your site, ready to capt |
2020-06-04 03:27:39 |
| 54.38.240.23 | attackbotsspam | Jun 3 14:27:20 firewall sshd[4961]: Failed password for root from 54.38.240.23 port 38228 ssh2 Jun 3 14:30:46 firewall sshd[5111]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.38.240.23 user=root Jun 3 14:30:48 firewall sshd[5111]: Failed password for root from 54.38.240.23 port 42910 ssh2 ... |
2020-06-04 03:18:33 |
| 91.124.88.174 | attack | Port probing on unauthorized port 445 |
2020-06-04 03:28:13 |
| 193.112.93.94 | attackspam | Unauthorized SSH login attempts |
2020-06-04 03:26:48 |
| 189.90.255.108 | attack | Jun 3 16:43:24 ws12vmsma01 sshd[10890]: Failed password for root from 189.90.255.108 port 50264 ssh2 Jun 3 16:46:34 ws12vmsma01 sshd[11489]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip-189-90-255-108.isp.valenet.com.br user=root Jun 3 16:46:37 ws12vmsma01 sshd[11489]: Failed password for root from 189.90.255.108 port 50802 ssh2 ... |
2020-06-04 03:47:40 |
| 114.67.67.41 | attack | odoo8 ... |
2020-06-04 03:36:17 |
| 159.65.136.196 | attackbotsspam | Jun 3 13:47:50 |
2020-06-04 03:17:42 |
| 106.12.209.57 | attackbotsspam | Repeated brute force against a port |
2020-06-04 03:17:04 |
| 93.176.179.138 | attack | Automatic report - Port Scan Attack |
2020-06-04 03:45:13 |
| 109.199.91.58 | attack | Automatic report - Banned IP Access |
2020-06-04 03:29:33 |
| 113.199.164.76 | attack | Unauthorized connection attempt detected from IP address 113.199.164.76 to port 23 |
2020-06-04 03:42:20 |
| 117.50.61.55 | attack | (sshd) Failed SSH login from 117.50.61.55 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Jun 3 14:27:57 s1 sshd[20853]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.50.61.55 user=root Jun 3 14:27:59 s1 sshd[20853]: Failed password for root from 117.50.61.55 port 24523 ssh2 Jun 3 14:44:35 s1 sshd[21423]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.50.61.55 user=root Jun 3 14:44:37 s1 sshd[21423]: Failed password for root from 117.50.61.55 port 18745 ssh2 Jun 3 14:47:39 s1 sshd[21513]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.50.61.55 user=root |
2020-06-04 03:25:25 |
| 144.217.83.201 | attack | Automatic report BANNED IP |
2020-06-04 03:43:18 |
| 62.234.145.195 | attackspam | 2020-06-03T18:21:18.207644ns386461 sshd\[10055\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.145.195 user=root 2020-06-03T18:21:20.914680ns386461 sshd\[10055\]: Failed password for root from 62.234.145.195 port 37158 ssh2 2020-06-03T18:36:26.033925ns386461 sshd\[23971\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.145.195 user=root 2020-06-03T18:36:27.392849ns386461 sshd\[23971\]: Failed password for root from 62.234.145.195 port 56678 ssh2 2020-06-03T18:39:20.392051ns386461 sshd\[26801\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.145.195 user=root ... |
2020-06-04 03:47:06 |
| 183.88.34.91 | attackbotsspam | 1591184852 - 06/03/2020 13:47:32 Host: 183.88.34.91/183.88.34.91 Port: 445 TCP Blocked |
2020-06-04 03:32:22 |