城市(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 <<>> 74.134.239.98
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30114
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;74.134.239.98. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025012801 1800 900 604800 86400
;; Query time: 37 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 29 04:46:49 CST 2025
;; MSG SIZE rcvd: 10698.239.134.74.in-addr.arpa domain name pointer syn-074-134-239-098.res.spectrum.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
98.239.134.74.in-addr.arpa name = syn-074-134-239-098.res.spectrum.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 51.38.132.29 | attack | Dec 25 10:22:07 xxxxxxx0 sshd[8480]: Invalid user ching from 51.38.132.29 port 55864 Dec 25 10:22:09 xxxxxxx0 sshd[8480]: Failed password for invalid user ching from 51.38.132.29 port 55864 ssh2 Dec 25 10:31:28 xxxxxxx0 sshd[9829]: Failed password for backup from 51.38.132.29 port 53322 ssh2 Dec 25 10:33:05 xxxxxxx0 sshd[10078]: Failed password for lp from 51.38.132.29 port 41312 ssh2 Dec 25 10:34:36 xxxxxxx0 sshd[10376]: Failed password for r.r from 51.38.132.29 port 57530 ssh2 ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=51.38.132.29 |
2019-12-25 19:58:13 |
| 180.136.90.172 | attackspambots | Scanning |
2019-12-25 19:38:21 |
| 103.236.114.38 | attack | postfix (unknown user, SPF fail or relay access denied) |
2019-12-25 20:02:42 |
| 95.174.102.70 | attackbots | Dec 25 07:17:35 s1 sshd\[25130\]: Invalid user slatford from 95.174.102.70 port 41764 Dec 25 07:17:35 s1 sshd\[25130\]: Failed password for invalid user slatford from 95.174.102.70 port 41764 ssh2 Dec 25 07:20:51 s1 sshd\[26115\]: Invalid user up from 95.174.102.70 port 36230 Dec 25 07:20:51 s1 sshd\[26115\]: Failed password for invalid user up from 95.174.102.70 port 36230 ssh2 Dec 25 07:22:22 s1 sshd\[26173\]: Invalid user n from 95.174.102.70 port 50138 Dec 25 07:22:22 s1 sshd\[26173\]: Failed password for invalid user n from 95.174.102.70 port 50138 ssh2 ... |
2019-12-25 19:40:22 |
| 125.71.238.182 | attackbotsspam | Unauthorized connection attempt detected from IP address 125.71.238.182 to port 1433 |
2019-12-25 19:37:28 |
| 14.246.30.138 | attack | Unauthorized connection attempt detected from IP address 14.246.30.138 to port 445 |
2019-12-25 19:33:51 |
| 51.83.42.244 | attackspambots | Invalid user info from 51.83.42.244 port 54168 |
2019-12-25 19:30:46 |
| 49.88.160.204 | attackbotsspam | Scanning |
2019-12-25 19:58:40 |
| 128.199.104.242 | attackbotsspam | $f2bV_matches |
2019-12-25 19:46:00 |
| 110.152.108.79 | attack | Scanning |
2019-12-25 20:01:47 |
| 176.112.108.58 | attackspambots | email spam |
2019-12-25 20:00:09 |
| 185.153.199.155 | attackspam | Dec 25 13:01:22 pkdns2 sshd\[16229\]: Address 185.153.199.155 maps to server-185-153-199-155.cloudedic.net, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Dec 25 13:01:22 pkdns2 sshd\[16229\]: Invalid user 0 from 185.153.199.155Dec 25 13:01:25 pkdns2 sshd\[16229\]: Failed password for invalid user 0 from 185.153.199.155 port 32618 ssh2Dec 25 13:01:30 pkdns2 sshd\[16233\]: Address 185.153.199.155 maps to server-185-153-199-155.cloudedic.net, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Dec 25 13:01:30 pkdns2 sshd\[16233\]: Invalid user 22 from 185.153.199.155Dec 25 13:01:34 pkdns2 sshd\[16233\]: Failed password for invalid user 22 from 185.153.199.155 port 8434 ssh2 ... |
2019-12-25 19:26:55 |
| 18.141.9.16 | attack | "SSH brute force auth login attempt." |
2019-12-25 19:33:33 |
| 23.129.64.190 | attackspam | proto=tcp . spt=34978 . dpt=25 . (Found on talos Dec 25) (216) |
2019-12-25 19:24:18 |
| 5.135.116.82 | attack | fail2ban honeypot |
2019-12-25 19:53:47 |