城市(city): Tokyo
省份(region): Tokyo
国家(country): Japan
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 221.240.244.139
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13593
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;221.240.244.139. IN A
;; AUTHORITY SECTION:
. 475 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2020090100 1800 900 604800 86400
;; Query time: 86 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Sep 01 13:39:57 CST 2020
;; MSG SIZE rcvd: 119139.244.240.221.in-addr.arpa domain name pointer 221x240x244x139.ap221.ftth.ucom.ne.jp.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
139.244.240.221.in-addr.arpa name = 221x240x244x139.ap221.ftth.ucom.ne.jp.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 213.169.39.218 | attackspam | $f2bV_matches |
2020-02-26 23:08:45 |
| 213.60.165.77 | attackspam | $f2bV_matches |
2020-02-26 22:38:40 |
| 213.232.127.216 | attack | $f2bV_matches |
2020-02-26 22:53:59 |
| 192.3.52.143 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found serenityfamilychiropractic.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 s |
2020-02-26 23:04:58 |
| 188.136.200.158 | attackbotsspam | 20/2/26@08:37:44: FAIL: Alarm-Network address from=188.136.200.158 20/2/26@08:37:44: FAIL: Alarm-Network address from=188.136.200.158 ... |
2020-02-26 22:50:14 |
| 213.32.52.1 | attackspam | $f2bV_matches |
2020-02-26 22:46:42 |
| 213.176.61.59 | attack | $f2bV_matches |
2020-02-26 23:06:45 |
| 213.32.120.155 | attack | $f2bV_matches |
2020-02-26 22:49:16 |
| 213.245.35.117 | attack | $f2bV_matches |
2020-02-26 22:52:45 |
| 212.95.137.242 | attackspam | $f2bV_matches |
2020-02-26 23:21:55 |
| 107.152.164.16 | attackspam | MYH,DEF GET http://meyerpantalones.es/magmi/web/magmi.php |
2020-02-26 23:14:33 |
| 213.32.19.142 | attack | $f2bV_matches |
2020-02-26 22:47:29 |
| 213.212.255.140 | attack | $f2bV_matches |
2020-02-26 22:58:19 |
| 112.85.42.172 | attackspambots | Feb 26 15:56:46 dedicated sshd[9203]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.172 user=root Feb 26 15:56:49 dedicated sshd[9203]: Failed password for root from 112.85.42.172 port 59114 ssh2 |
2020-02-26 23:01:26 |
| 106.12.215.238 | attackbots | (sshd) Failed SSH login from 106.12.215.238 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Feb 26 15:52:51 amsweb01 sshd[18716]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.215.238 user=root Feb 26 15:52:53 amsweb01 sshd[18716]: Failed password for root from 106.12.215.238 port 51792 ssh2 Feb 26 15:54:47 amsweb01 sshd[18878]: User mysql from 106.12.215.238 not allowed because not listed in AllowUsers Feb 26 15:54:47 amsweb01 sshd[18878]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.215.238 user=mysql Feb 26 15:54:48 amsweb01 sshd[18878]: Failed password for invalid user mysql from 106.12.215.238 port 39108 ssh2 |
2020-02-26 22:59:08 |