城市(city): unknown
省份(region): unknown
国家(country): Japan
运营商(isp): SoftBank
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 126.97.31.195
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 58840
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;126.97.31.195. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021401 1800 900 604800 86400
;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 15 08:20:17 CST 2025
;; MSG SIZE rcvd: 106195.31.97.126.in-addr.arpa domain name pointer softbank126097031195.bbtec.net.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
195.31.97.126.in-addr.arpa name = softbank126097031195.bbtec.net.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 120.244.116.166 | attackbotsspam | Unauthorized connection attempt detected from IP address 120.244.116.166 to port 3389 |
2019-12-31 22:45:54 |
| 120.244.114.77 | attackspam | Unauthorized connection attempt detected from IP address 120.244.114.77 to port 3389 |
2019-12-31 22:48:18 |
| 107.175.92.123 | attackspam | (From eric@talkwithcustomer.com) Hello naturalhealthdcs.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 naturalhealthdcs.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 naturalhealthdcs.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 f |
2019-12-31 23:01:42 |
| 180.104.112.226 | attackspam | Unauthorized connection attempt detected from IP address 180.104.112.226 to port 1433 |
2019-12-31 22:40:53 |
| 106.75.79.172 | attack | Unauthorized connection attempt detected from IP address 106.75.79.172 to port 548 |
2019-12-31 22:27:48 |
| 101.80.247.197 | attack | Unauthorized connection attempt detected from IP address 101.80.247.197 to port 445 |
2019-12-31 22:29:13 |
| 58.246.4.50 | attack | Unauthorized connection attempt detected from IP address 58.246.4.50 to port 1433 |
2019-12-31 22:30:59 |
| 139.9.235.252 | attack | Unauthorized connection attempt detected from IP address 139.9.235.252 to port 348 |
2019-12-31 22:43:31 |
| 223.72.94.140 | attack | Unauthorized connection attempt detected from IP address 223.72.94.140 to port 3389 |
2019-12-31 22:37:13 |
| 47.105.86.68 | attack | Unauthorized connection attempt detected from IP address 47.105.86.68 to port 23 |
2019-12-31 22:33:33 |
| 205.185.123.237 | attackbots | 2019-12-31T14:54:10.359942shield sshd\[23609\]: Invalid user ubnt from 205.185.123.237 port 49804 2019-12-31T14:54:10.366235shield sshd\[23609\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=205.185.123.237 2019-12-31T14:54:12.338259shield sshd\[23609\]: Failed password for invalid user ubnt from 205.185.123.237 port 49804 ssh2 2019-12-31T14:54:17.944515shield sshd\[23609\]: Failed password for invalid user ubnt from 205.185.123.237 port 49804 ssh2 2019-12-31T14:54:23.384987shield sshd\[23609\]: Failed password for invalid user ubnt from 205.185.123.237 port 49804 ssh2 |
2019-12-31 23:03:35 |
| 110.137.101.3 | attack | Unauthorized connection attempt detected from IP address 110.137.101.3 to port 445 |
2019-12-31 22:55:10 |
| 139.9.228.41 | attack | Unauthorized connection attempt detected from IP address 139.9.228.41 to port 358 |
2019-12-31 22:44:23 |
| 222.94.195.121 | attack | Unauthorized connection attempt detected from IP address 222.94.195.121 to port 350 |
2019-12-31 22:37:45 |
| 180.211.162.234 | attack | Honeypot attack, port: 445, PTR: PTR record not found |
2019-12-31 22:40:35 |