城市(city): unknown
省份(region): unknown
国家(country): Japan
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 121.104.254.32
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13537
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;121.104.254.32. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025020901 1800 900 604800 86400
;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 04:38:13 CST 2025
;; MSG SIZE rcvd: 10732.254.104.121.in-addr.arpa domain name pointer KD121104254032.ppp-bb.dion.ne.jp.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
32.254.104.121.in-addr.arpa name = KD121104254032.ppp-bb.dion.ne.jp.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 124.93.222.211 | attackspam | Aug 15 10:05:17 ajax sshd[32236]: Failed password for root from 124.93.222.211 port 45860 ssh2 |
2020-08-15 17:34:03 |
| 67.143.176.231 | attackspam | Brute forcing email accounts |
2020-08-15 17:42:14 |
| 222.186.175.151 | attack | Aug 15 09:42:34 rush sshd[29187]: Failed password for root from 222.186.175.151 port 43268 ssh2 Aug 15 09:42:49 rush sshd[29187]: error: maximum authentication attempts exceeded for root from 222.186.175.151 port 43268 ssh2 [preauth] Aug 15 09:42:57 rush sshd[29193]: Failed password for root from 222.186.175.151 port 14872 ssh2 ... |
2020-08-15 17:43:35 |
| 218.92.0.246 | attackbots | Aug 15 11:34:22 plg sshd[19006]: Failed none for invalid user root from 218.92.0.246 port 14560 ssh2 Aug 15 11:34:23 plg sshd[19006]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.246 user=root Aug 15 11:34:25 plg sshd[19006]: Failed password for invalid user root from 218.92.0.246 port 14560 ssh2 Aug 15 11:34:28 plg sshd[19006]: Failed password for invalid user root from 218.92.0.246 port 14560 ssh2 Aug 15 11:34:33 plg sshd[19006]: Failed password for invalid user root from 218.92.0.246 port 14560 ssh2 Aug 15 11:34:39 plg sshd[19006]: Failed password for invalid user root from 218.92.0.246 port 14560 ssh2 Aug 15 11:34:43 plg sshd[19006]: Failed password for invalid user root from 218.92.0.246 port 14560 ssh2 Aug 15 11:34:43 plg sshd[19006]: error: maximum authentication attempts exceeded for invalid user root from 218.92.0.246 port 14560 ssh2 [preauth] ... |
2020-08-15 17:40:03 |
| 64.227.125.204 | attackbots | 2020-08-15T13:58:50.018198hostname sshd[29283]: Failed password for root from 64.227.125.204 port 43930 ssh2 2020-08-15T14:03:21.246397hostname sshd[31003]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=64.227.125.204 user=root 2020-08-15T14:03:23.193584hostname sshd[31003]: Failed password for root from 64.227.125.204 port 36886 ssh2 ... |
2020-08-15 17:38:05 |
| 218.92.0.251 | attackbots | [MK-VM4] SSH login failed |
2020-08-15 17:29:25 |
| 82.221.131.71 | attackspambots | $f2bV_matches |
2020-08-15 17:46:36 |
| 23.95.204.167 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found scvfamilychiropractic.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well. So here’s my question – what happens AFTER someone lands on your site? Anything? Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever. That means that all the work and effort you put into getting them to show up, goes down the tubes. Why would you want all that good work – and the great site you’ve built – go to waste? Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry. But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket? You can – thanks to revolutionary new softwa |
2020-08-15 17:51:01 |
| 184.105.139.104 | attackbotsspam | srv02 Mass scanning activity detected Target: 123(ntp) .. |
2020-08-15 18:07:58 |
| 134.175.228.215 | attackbotsspam | 2020-08-15T04:21:02.207823morrigan.ad5gb.com sshd[3787613]: Failed password for root from 134.175.228.215 port 57504 ssh2 2020-08-15T04:21:02.669916morrigan.ad5gb.com sshd[3787613]: Disconnected from authenticating user root 134.175.228.215 port 57504 [preauth] |
2020-08-15 18:07:03 |
| 222.186.175.154 | attackbotsspam | Aug 15 05:25:37 ny01 sshd[7766]: Failed password for root from 222.186.175.154 port 64338 ssh2 Aug 15 05:25:51 ny01 sshd[7766]: error: maximum authentication attempts exceeded for root from 222.186.175.154 port 64338 ssh2 [preauth] Aug 15 05:25:58 ny01 sshd[7799]: Failed password for root from 222.186.175.154 port 2008 ssh2 |
2020-08-15 17:27:35 |
| 211.200.104.252 | attackbots | Aug 15 05:19:35 lanister sshd[10478]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.200.104.252 user=root Aug 15 05:19:37 lanister sshd[10478]: Failed password for root from 211.200.104.252 port 33842 ssh2 Aug 15 05:20:15 lanister sshd[10483]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.200.104.252 user=root Aug 15 05:20:17 lanister sshd[10483]: Failed password for root from 211.200.104.252 port 43268 ssh2 |
2020-08-15 18:07:26 |
| 201.236.182.92 | attackspam | $f2bV_matches |
2020-08-15 17:53:52 |
| 106.54.200.209 | attackspambots | $f2bV_matches |
2020-08-15 17:46:14 |
| 220.177.110.13 | attackspam | Automatic report - Port Scan Attack |
2020-08-15 17:31:29 |