城市(city): unknown
省份(region): unknown
国家(country): Japan
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 220.14.99.121
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 19535
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;220.14.99.121. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021401 1800 900 604800 86400
;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 15 03:27:22 CST 2025
;; MSG SIZE rcvd: 106121.99.14.220.in-addr.arpa domain name pointer softbank220014099121.bbtec.net.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
121.99.14.220.in-addr.arpa name = softbank220014099121.bbtec.net.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 75.75.232.194 | attack | (From eric@talkwithwebvisitor.com) Good day, My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations What for? Part of my job is to check out websites and the work you’ve done with serenityfamilychiropractic.com definitely stands out. It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality. There is, however, a catch… more accurately, a question… So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know? More importantly, how do you make a connection with that person? Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind. Here’s a way to create INSTANT engagement that you may not have known about… Talk With Web Visitor is a software widget that’s works on your site, ready to |
2020-06-23 07:29:05 |
| 193.148.70.68 | attack | Jun 22 20:26:29 localhost sshd[126168]: Invalid user diana from 193.148.70.68 port 38166 Jun 22 20:26:29 localhost sshd[126168]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.148.70.68 Jun 22 20:26:29 localhost sshd[126168]: Invalid user diana from 193.148.70.68 port 38166 Jun 22 20:26:31 localhost sshd[126168]: Failed password for invalid user diana from 193.148.70.68 port 38166 ssh2 Jun 22 20:34:56 localhost sshd[127263]: Invalid user student05 from 193.148.70.68 port 38190 ... |
2020-06-23 07:37:59 |
| 120.92.91.176 | attackbotsspam | $f2bV_matches |
2020-06-23 07:42:05 |
| 91.221.66.60 | attack | WebFormToEmail Comment SPAM |
2020-06-23 07:55:03 |
| 202.148.29.218 | attackspambots |
|
2020-06-23 07:55:41 |
| 178.128.125.10 | attackbots | Invalid user lbs from 178.128.125.10 port 42826 |
2020-06-23 07:49:39 |
| 103.225.50.14 | attackbots | xmlrpc attack |
2020-06-23 07:53:00 |
| 211.112.18.37 | attackbotsspam | 980. On Jun 22 2020 experienced a Brute Force SSH login attempt -> 1 unique times by 211.112.18.37. |
2020-06-23 07:31:24 |
| 104.248.160.58 | attackbotsspam | Jun 23 01:05:33 OPSO sshd\[27387\]: Invalid user mohammed from 104.248.160.58 port 57908 Jun 23 01:05:33 OPSO sshd\[27387\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.160.58 Jun 23 01:05:35 OPSO sshd\[27387\]: Failed password for invalid user mohammed from 104.248.160.58 port 57908 ssh2 Jun 23 01:13:44 OPSO sshd\[28967\]: Invalid user oracle from 104.248.160.58 port 53176 Jun 23 01:13:44 OPSO sshd\[28967\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.248.160.58 |
2020-06-23 07:37:14 |
| 190.207.109.3 | attackspam | 445/tcp [2020-06-22]1pkt |
2020-06-23 07:29:36 |
| 178.128.144.227 | attackbots | 2020-06-22T21:32:42.633336abusebot-8.cloudsearch.cf sshd[6867]: Invalid user admin from 178.128.144.227 port 36746 2020-06-22T21:32:42.639873abusebot-8.cloudsearch.cf sshd[6867]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.144.227 2020-06-22T21:32:42.633336abusebot-8.cloudsearch.cf sshd[6867]: Invalid user admin from 178.128.144.227 port 36746 2020-06-22T21:32:44.758552abusebot-8.cloudsearch.cf sshd[6867]: Failed password for invalid user admin from 178.128.144.227 port 36746 ssh2 2020-06-22T21:36:53.649950abusebot-8.cloudsearch.cf sshd[6876]: Invalid user release from 178.128.144.227 port 40946 2020-06-22T21:36:53.655951abusebot-8.cloudsearch.cf sshd[6876]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.144.227 2020-06-22T21:36:53.649950abusebot-8.cloudsearch.cf sshd[6876]: Invalid user release from 178.128.144.227 port 40946 2020-06-22T21:36:56.231368abusebot-8.cloudsearch.cf sshd[687 ... |
2020-06-23 07:14:47 |
| 172.172.30.216 | attack | 8080/tcp [2020-06-22]1pkt |
2020-06-23 07:34:16 |
| 119.18.194.130 | attackbotsspam | $f2bV_matches |
2020-06-23 07:54:20 |
| 50.58.85.142 | attackspambots | 20/6/22@16:35:07: FAIL: Alarm-Network address from=50.58.85.142 20/6/22@16:35:07: FAIL: Alarm-Network address from=50.58.85.142 ... |
2020-06-23 07:26:09 |
| 134.175.176.97 | attack | 2020-06-22T20:34:28.167788mail.csmailer.org sshd[20245]: Failed password for root from 134.175.176.97 port 53622 ssh2 2020-06-22T20:36:24.477741mail.csmailer.org sshd[20568]: Invalid user crp from 134.175.176.97 port 55878 2020-06-22T20:36:24.481353mail.csmailer.org sshd[20568]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.176.97 2020-06-22T20:36:24.477741mail.csmailer.org sshd[20568]: Invalid user crp from 134.175.176.97 port 55878 2020-06-22T20:36:25.857878mail.csmailer.org sshd[20568]: Failed password for invalid user crp from 134.175.176.97 port 55878 ssh2 ... |
2020-06-23 07:51:39 |