城市(city): Milpitas
省份(region): California
国家(country): United States
运营商(isp): AT&T
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.54.243.85
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40787
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.54.243.85. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021202 1800 900 604800 86400
;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 13 08:48:13 CST 2025
;; MSG SIZE rcvd: 106
85.243.54.104.in-addr.arpa domain name pointer 104-54-243-85.lightspeed.sntcca.sbcglobal.net.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
85.243.54.104.in-addr.arpa name = 104-54-243-85.lightspeed.sntcca.sbcglobal.net.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 52.164.186.102 | attackspambots | Mar 28 02:03:35 django sshd[79087]: Invalid user iyq from 52.164.186.102 Mar 28 02:03:35 django sshd[79087]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.164.186.102 Mar 28 02:03:37 django sshd[79087]: Failed password for invalid user iyq from 52.164.186.102 port 47566 ssh2 Mar 28 02:03:37 django sshd[79088]: Received disconnect from 52.164.186.102: 11: Bye Bye Mar 28 02:16:41 django sshd[81186]: Invalid user prachi from 52.164.186.102 Mar 28 02:16:41 django sshd[81186]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=52.164.186.102 Mar 28 02:16:43 django sshd[81186]: Failed password for invalid user prachi from 52.164.186.102 port 35752 ssh2 Mar 28 02:16:43 django sshd[81187]: Received disconnect from 52.164.186.102: 11: Bye Bye Mar 28 02:24:18 django sshd[82309]: Invalid user shanice from 52.164.186.102 Mar 28 02:24:18 django sshd[82309]: pam_unix(sshd:auth): authentication failure........ ------------------------------- |
2020-03-29 04:36:36 |
| 89.248.160.150 | attack | 89.248.160.150 was recorded 15 times by 9 hosts attempting to connect to the following ports: 1089,1282,1284. Incident counter (4h, 24h, all-time): 15, 101, 8998 |
2020-03-29 04:22:14 |
| 89.204.137.119 | attackspambots | [MK-VM1] Blocked by UFW |
2020-03-29 04:30:29 |
| 80.82.77.234 | attack | Mar 28 20:01:29 debian-2gb-nbg1-2 kernel: \[7681154.489989\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=80.82.77.234 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=25954 PROTO=TCP SPT=59913 DPT=46589 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-03-29 04:07:34 |
| 51.83.216.215 | attackbotsspam | SIP/5060 Probe, BF, Hack - |
2020-03-29 04:23:03 |
| 106.51.73.204 | attackspam | ... |
2020-03-29 04:28:31 |
| 69.229.6.46 | attackspambots | SSH Brute Force |
2020-03-29 04:32:42 |
| 80.41.82.235 | attackspambots | [27/Mar/2020:04:32:30 -0400] "GET / HTTP/1.1" Chrome 52.0 UA |
2020-03-29 04:34:30 |
| 78.128.112.58 | attackbotsspam | ET CINS Active Threat Intelligence Poor Reputation IP group 63 - port: 3399 proto: TCP cat: Misc Attack |
2020-03-29 04:09:52 |
| 27.50.165.198 | attackspambots | ET SCAN Suspicious inbound to mySQL port 3306 - port: 3306 proto: TCP cat: Potentially Bad Traffic |
2020-03-29 04:18:45 |
| 35.200.170.217 | attackbots | Mar 28 19:40:30 MainVPS sshd[19477]: Invalid user lmc from 35.200.170.217 port 48528 Mar 28 19:40:30 MainVPS sshd[19477]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.200.170.217 Mar 28 19:40:30 MainVPS sshd[19477]: Invalid user lmc from 35.200.170.217 port 48528 Mar 28 19:40:32 MainVPS sshd[19477]: Failed password for invalid user lmc from 35.200.170.217 port 48528 ssh2 Mar 28 19:45:10 MainVPS sshd[28401]: Invalid user yck from 35.200.170.217 port 59178 ... |
2020-03-29 04:39:13 |
| 87.251.74.15 | attackbots | ET CINS Active Threat Intelligence Poor Reputation IP group 78 - port: 2303 proto: TCP cat: Misc Attack |
2020-03-29 04:22:46 |
| 66.117.225.3 | attack | ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic |
2020-03-29 04:12:48 |
| 14.29.156.148 | attackbotsspam | Mar 28 20:36:04 ns392434 sshd[2781]: Invalid user cge from 14.29.156.148 port 46858 Mar 28 20:36:04 ns392434 sshd[2781]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.29.156.148 Mar 28 20:36:04 ns392434 sshd[2781]: Invalid user cge from 14.29.156.148 port 46858 Mar 28 20:36:06 ns392434 sshd[2781]: Failed password for invalid user cge from 14.29.156.148 port 46858 ssh2 Mar 28 20:51:56 ns392434 sshd[3343]: Invalid user yis from 14.29.156.148 port 54719 Mar 28 20:51:56 ns392434 sshd[3343]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=14.29.156.148 Mar 28 20:51:56 ns392434 sshd[3343]: Invalid user yis from 14.29.156.148 port 54719 Mar 28 20:51:58 ns392434 sshd[3343]: Failed password for invalid user yis from 14.29.156.148 port 54719 ssh2 Mar 28 20:57:30 ns392434 sshd[3530]: Invalid user vlx from 14.29.156.148 port 54502 |
2020-03-29 04:35:41 |
| 119.31.123.147 | attackbots | Mar 28 18:31:25 ns382633 sshd\[24900\]: Invalid user lesly from 119.31.123.147 port 47434 Mar 28 18:31:25 ns382633 sshd\[24900\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.31.123.147 Mar 28 18:31:27 ns382633 sshd\[24900\]: Failed password for invalid user lesly from 119.31.123.147 port 47434 ssh2 Mar 28 18:39:53 ns382633 sshd\[26236\]: Invalid user swj from 119.31.123.147 port 43844 Mar 28 18:39:53 ns382633 sshd\[26236\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.31.123.147 |
2020-03-29 04:33:57 |