城市(city): unknown
省份(region): unknown
国家(country): Guam
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 116.68.13.152
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 47408
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;116.68.13.152. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025022700 1800 900 604800 86400
;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 27 23:59:54 CST 2025
;; MSG SIZE rcvd: 106
152.13.68.116.in-addr.arpa domain name pointer 116.68-13-152.dpacguam.net.
Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
152.13.68.116.in-addr.arpa name = 116.68-13-152.dpacguam.net.
Authoritative answers can be found from:
| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 192.163.207.48 | attackspambots | 2020-01-14T22:32:27.519713shield sshd\[16269\]: Invalid user richard from 192.163.207.48 port 43716 2020-01-14T22:32:27.524233shield sshd\[16269\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=server.coachquoter.co.uk 2020-01-14T22:32:29.706522shield sshd\[16269\]: Failed password for invalid user richard from 192.163.207.48 port 43716 ssh2 2020-01-14T22:35:37.848902shield sshd\[17213\]: Invalid user sysadmin from 192.163.207.48 port 45724 2020-01-14T22:35:37.854947shield sshd\[17213\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=server.coachquoter.co.uk |
2020-01-15 06:36:17 |
| 79.177.29.64 | attackbots | Automatic report - Port Scan Attack |
2020-01-15 06:36:37 |
| 113.175.165.246 | attack | Unauthorized connection attempt from IP address 113.175.165.246 on Port 445(SMB) |
2020-01-15 06:23:10 |
| 192.210.201.152 | attackspam | (From eric@talkwithcustomer.com) Hello romechiropractic.com, People ask, “why does TalkWithCustomer work so well?” It’s simple. TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time. - NOT one week, two weeks, three weeks after they’ve checked out your website romechiropractic.com. - NOT with a form letter style email that looks like it was written by a bot. - NOT with a robocall that could come at any time out of the blue. TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU. They kick off the conversation. They take that first step. They ask to hear from you regarding what you have to offer and how it can make their life better. And it happens almost immediately. In real time. While they’re still looking over your website romechiropractic.com, trying to make up their mind whether you are right for them. When you connect with them at that very moment it’s the ultimate in Perfect Timing – as one |
2020-01-15 06:13:49 |
| 37.57.91.206 | attackbots | Unauthorized connection attempt from IP address 37.57.91.206 on Port 445(SMB) |
2020-01-15 06:30:14 |
| 103.1.94.96 | attackspam | $f2bV_matches |
2020-01-15 06:25:01 |
| 103.45.111.55 | attackspambots | Jan 14 21:22:32 vtv3 sshd[22963]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.45.111.55 Jan 14 21:22:34 vtv3 sshd[22963]: Failed password for invalid user www from 103.45.111.55 port 55506 ssh2 Jan 14 21:32:11 vtv3 sshd[27795]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.45.111.55 Jan 14 21:55:44 vtv3 sshd[7070]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.45.111.55 Jan 14 21:55:46 vtv3 sshd[7070]: Failed password for invalid user yy from 103.45.111.55 port 59720 ssh2 Jan 14 22:03:41 vtv3 sshd[10658]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.45.111.55 Jan 15 00:10:04 vtv3 sshd[8131]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.45.111.55 Jan 15 00:10:07 vtv3 sshd[8131]: Failed password for invalid user admin from 103.45.111.55 port 34224 ssh2 Jan 15 00:16:43 vtv3 ssh |
2020-01-15 06:10:52 |
| 118.25.74.199 | attackspam | Unauthorized connection attempt detected from IP address 118.25.74.199 to port 2220 [J] |
2020-01-15 06:31:55 |
| 31.13.191.88 | attack | fell into ViewStateTrap:berlin |
2020-01-15 06:28:04 |
| 159.138.128.138 | attack | badbot |
2020-01-15 06:17:18 |
| 41.32.163.54 | attackbots | Unauthorized connection attempt from IP address 41.32.163.54 on Port 445(SMB) |
2020-01-15 06:45:27 |
| 222.186.173.215 | attackspambots | Jan 14 23:07:49 MK-Soft-VM8 sshd[20082]: Failed password for root from 222.186.173.215 port 32528 ssh2 Jan 14 23:07:52 MK-Soft-VM8 sshd[20082]: Failed password for root from 222.186.173.215 port 32528 ssh2 ... |
2020-01-15 06:11:13 |
| 51.83.98.52 | attackspambots | $f2bV_matches |
2020-01-15 06:12:30 |
| 117.55.242.131 | attackspambots | Unauthorized connection attempt from IP address 117.55.242.131 on Port 445(SMB) |
2020-01-15 06:48:38 |
| 218.92.0.212 | attackbotsspam | Jan 14 23:18:21 legacy sshd[13330]: Failed password for root from 218.92.0.212 port 24403 ssh2 Jan 14 23:18:34 legacy sshd[13330]: error: maximum authentication attempts exceeded for root from 218.92.0.212 port 24403 ssh2 [preauth] Jan 14 23:18:42 legacy sshd[13343]: Failed password for root from 218.92.0.212 port 55475 ssh2 ... |
2020-01-15 06:27:11 |