城市(city): unknown
省份(region): unknown
国家(country): United States of America (the)
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 108.139.9.52
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 58105
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;108.139.9.52. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012800 1800 900 604800 86400
;; Query time: 43 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 29 00:51:02 CST 2025
;; MSG SIZE rcvd: 10552.9.139.108.in-addr.arpa domain name pointer server-108-139-9-52.sfo5.r.cloudfront.net.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
52.9.139.108.in-addr.arpa name = server-108-139-9-52.sfo5.r.cloudfront.net.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 104.131.190.193 | attack | Mar 27 21:30:36 ourumov-web sshd\[32299\]: Invalid user hxk from 104.131.190.193 port 36368 Mar 27 21:30:36 ourumov-web sshd\[32299\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.131.190.193 Mar 27 21:30:38 ourumov-web sshd\[32299\]: Failed password for invalid user hxk from 104.131.190.193 port 36368 ssh2 ... |
2020-03-28 04:42:51 |
| 139.198.124.14 | attackspam | Mar 27 20:40:47 ns382633 sshd\[24073\]: Invalid user uyo from 139.198.124.14 port 53182 Mar 27 20:40:47 ns382633 sshd\[24073\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.198.124.14 Mar 27 20:40:49 ns382633 sshd\[24073\]: Failed password for invalid user uyo from 139.198.124.14 port 53182 ssh2 Mar 27 20:44:34 ns382633 sshd\[24481\]: Invalid user ntb from 139.198.124.14 port 49826 Mar 27 20:44:34 ns382633 sshd\[24481\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.198.124.14 |
2020-03-28 04:44:35 |
| 103.79.169.34 | attackspam | Invalid user pee from 103.79.169.34 port 60556 |
2020-03-28 04:53:39 |
| 103.40.26.77 | attackspam | Mar 27 12:59:53 pixelmemory sshd[13545]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.40.26.77 Mar 27 12:59:55 pixelmemory sshd[13545]: Failed password for invalid user jha from 103.40.26.77 port 49580 ssh2 Mar 27 13:16:05 pixelmemory sshd[16058]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.40.26.77 ... |
2020-03-28 05:07:57 |
| 51.68.191.193 | attack | (smtpauth) Failed SMTP AUTH login from 51.68.191.193 (DE/Germany/193.ip-51-68-191.eu): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_TRIGGER; Logs: 2020-03-27 22:57:52 login authenticator failed for 193.ip-51-68-191.eu (USER) [51.68.191.193]: 535 Incorrect authentication data (set_id=info@nazeranyekta.com) |
2020-03-28 05:02:43 |
| 106.12.202.192 | attackbots | SSH login attempts brute force. |
2020-03-28 05:07:41 |
| 98.137.246.8 | attack | SSH login attempts. |
2020-03-28 04:55:49 |
| 104.131.13.199 | attack | $f2bV_matches |
2020-03-28 04:44:53 |
| 212.158.160.217 | attackbotsspam | 03/27/2020-08:28:52.922522 212.158.160.217 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433 |
2020-03-28 04:41:12 |
| 51.79.60.147 | attack | Mar 27 13:28:38 debian-2gb-nbg1-2 kernel: \[7571189.120101\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=51.79.60.147 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=238 ID=55813 PROTO=TCP SPT=45941 DPT=17316 WINDOW=1024 RES=0x00 SYN URGP=0 |
2020-03-28 05:04:04 |
| 51.254.205.6 | attackspambots | Mar 27 15:45:12 ns382633 sshd\[27460\]: Invalid user rck from 51.254.205.6 port 36978 Mar 27 15:45:12 ns382633 sshd\[27460\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.254.205.6 Mar 27 15:45:15 ns382633 sshd\[27460\]: Failed password for invalid user rck from 51.254.205.6 port 36978 ssh2 Mar 27 15:52:19 ns382633 sshd\[28658\]: Invalid user bgt from 51.254.205.6 port 60800 Mar 27 15:52:19 ns382633 sshd\[28658\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.254.205.6 |
2020-03-28 04:47:28 |
| 80.241.212.139 | attackspam | SSH login attempts. |
2020-03-28 04:45:38 |
| 103.63.109.74 | attack | 2020-03-27T18:32:00.611375abusebot-6.cloudsearch.cf sshd[18335]: Invalid user qrv from 103.63.109.74 port 37660 2020-03-27T18:32:00.620410abusebot-6.cloudsearch.cf sshd[18335]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.63.109.74 2020-03-27T18:32:00.611375abusebot-6.cloudsearch.cf sshd[18335]: Invalid user qrv from 103.63.109.74 port 37660 2020-03-27T18:32:02.597452abusebot-6.cloudsearch.cf sshd[18335]: Failed password for invalid user qrv from 103.63.109.74 port 37660 ssh2 2020-03-27T18:39:51.643003abusebot-6.cloudsearch.cf sshd[18817]: Invalid user admin from 103.63.109.74 port 47548 2020-03-27T18:39:51.649839abusebot-6.cloudsearch.cf sshd[18817]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.63.109.74 2020-03-27T18:39:51.643003abusebot-6.cloudsearch.cf sshd[18817]: Invalid user admin from 103.63.109.74 port 47548 2020-03-27T18:39:53.286203abusebot-6.cloudsearch.cf sshd[18817]: Failed passw ... |
2020-03-28 05:00:18 |
| 129.226.134.112 | attack | Mar 27 20:39:21 124388 sshd[30190]: Invalid user contry from 129.226.134.112 port 56904 Mar 27 20:39:21 124388 sshd[30190]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.226.134.112 Mar 27 20:39:21 124388 sshd[30190]: Invalid user contry from 129.226.134.112 port 56904 Mar 27 20:39:23 124388 sshd[30190]: Failed password for invalid user contry from 129.226.134.112 port 56904 ssh2 Mar 27 20:43:28 124388 sshd[30251]: Invalid user yif from 129.226.134.112 port 53028 |
2020-03-28 05:01:05 |
| 101.75.133.74 | attackspambots | MultiHost/MultiPort Probe, Scan, Hack - |
2020-03-28 05:13:30 |