城市(city): unknown
省份(region): unknown
国家(country): Germany
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 77.14.104.48
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 54129
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;77.14.104.48. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020901 1800 900 604800 86400
;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 05:50:10 CST 2025
;; MSG SIZE rcvd: 10548.104.14.77.in-addr.arpa domain name pointer dynamic-077-014-104-048.77.14.pool.telefonica.de.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
48.104.14.77.in-addr.arpa name = dynamic-077-014-104-048.77.14.pool.telefonica.de.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 196.52.43.55 | attack | [portscan] tcp/21 [FTP] *(RWIN=65535)(09171029) |
2019-09-17 16:18:20 |
| 185.93.3.114 | attackbotsspam | (From patsyboX@gmail.com) hi there We all know there are no tricks with google anymore So, instead of looking for ways to trick google, why not perform a whitehat results driven monthly SEO Plan instead. Check out our plans https://googlealexarank.com/index.php/seo-packages/ We know how to get you into top safely, without risking your investment during google updates thanks and regards Mike str8creativecom@gmail.com |
2019-09-17 16:01:04 |
| 103.121.26.150 | attack | Sep 17 03:56:11 ny01 sshd[5178]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.121.26.150 Sep 17 03:56:14 ny01 sshd[5178]: Failed password for invalid user dr from 103.121.26.150 port 30196 ssh2 Sep 17 04:00:47 ny01 sshd[6165]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.121.26.150 |
2019-09-17 16:05:51 |
| 191.23.14.219 | attack | port scan and connect, tcp 23 (telnet) |
2019-09-17 16:28:34 |
| 61.19.23.30 | attack | Sep 17 07:20:03 dedicated sshd[30733]: Invalid user 1libuuid from 61.19.23.30 port 49220 |
2019-09-17 16:08:05 |
| 180.96.14.98 | attackbots | Sep 17 10:00:30 lnxmysql61 sshd[28108]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.96.14.98 Sep 17 10:00:32 lnxmysql61 sshd[28108]: Failed password for invalid user server from 180.96.14.98 port 3001 ssh2 Sep 17 10:07:58 lnxmysql61 sshd[28812]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.96.14.98 |
2019-09-17 16:20:08 |
| 129.204.205.171 | attack | Sep 17 07:39:10 hcbbdb sshd\[23339\]: Invalid user frederick from 129.204.205.171 Sep 17 07:39:10 hcbbdb sshd\[23339\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.205.171 Sep 17 07:39:12 hcbbdb sshd\[23339\]: Failed password for invalid user frederick from 129.204.205.171 port 48488 ssh2 Sep 17 07:44:53 hcbbdb sshd\[23920\]: Invalid user temp from 129.204.205.171 Sep 17 07:44:53 hcbbdb sshd\[23920\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.204.205.171 |
2019-09-17 16:02:09 |
| 175.139.242.49 | attack | (sshd) Failed SSH login from 175.139.242.49 (MY/Malaysia/Kedah/Sungai Petani/-/[AS4788 TM Net, Internet Service Provider]): 1 in the last 3600 secs |
2019-09-17 15:55:27 |
| 139.199.168.184 | attackspam | Sep 17 09:40:07 s64-1 sshd[31824]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.168.184 Sep 17 09:40:09 s64-1 sshd[31824]: Failed password for invalid user redhat from 139.199.168.184 port 54954 ssh2 Sep 17 09:45:22 s64-1 sshd[31924]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.168.184 ... |
2019-09-17 15:47:05 |
| 121.7.127.92 | attack | k+ssh-bruteforce |
2019-09-17 16:27:47 |
| 202.163.126.134 | attackspam | Invalid user sales2 from 202.163.126.134 port 60862 |
2019-09-17 15:44:07 |
| 115.29.3.34 | attackbotsspam | Sep 17 10:04:09 dedicated sshd[20039]: Invalid user mortimer from 115.29.3.34 port 45779 |
2019-09-17 16:10:59 |
| 51.89.151.214 | attackspambots | Automated report - ssh fail2ban: Sep 17 08:50:35 authentication failure Sep 17 08:50:37 wrong password, user=rootme, port=46714, ssh2 Sep 17 08:54:10 wrong password, user=root, port=32882, ssh2 |
2019-09-17 15:50:44 |
| 95.242.177.213 | attack | detected by Fail2Ban |
2019-09-17 16:17:42 |
| 125.65.40.233 | attackbotsspam | Automatic report - Port Scan Attack |
2019-09-17 16:27:30 |