城市(city): unknown
省份(region): unknown
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 135.164.147.234
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30410
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;135.164.147.234. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025021300 1800 900 604800 86400
;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 13 16:49:14 CST 2025
;; MSG SIZE rcvd: 108234.147.164.135.in-addr.arpa domain name pointer nothing.attdns.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
234.147.164.135.in-addr.arpa name = nothing.attdns.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 23.245.154.67 | attack | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found kestenchiro.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 software that ca |
2020-03-12 02:24:55 |
| 95.213.143.90 | attackbotsspam | Mar 11 14:09:53 ws19vmsma01 sshd[83240]: Failed password for root from 95.213.143.90 port 35896 ssh2 ... |
2020-03-12 02:05:48 |
| 184.13.120.96 | attackbotsspam | [portscan] Port scan |
2020-03-12 02:22:33 |
| 49.233.153.71 | attack | Mar 11 11:41:34 mailserver sshd\[21823\]: Invalid user rstudio from 49.233.153.71 ... |
2020-03-12 01:51:39 |
| 209.17.96.114 | attackspam | The IP has triggered Cloudflare WAF. CF-Ray: 57241cda3ba4f1c6 | WAF_Rule_ID: ipr24 | WAF_Kind: firewall | CF_Action: challenge | Country: US | CF_IPClass: unknown | Protocol: HTTP/1.1 | Method: GET | Host: theme-suka.skk.moe | User-Agent: Mozilla/5.0 (compatible; Nimbostratus-Bot/v1.3.2; http://cloudsystemnetworks.com) | CF_DC: ATL. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB). |
2020-03-12 02:10:44 |
| 149.135.121.242 | attack | Mar 11 05:38:59 dallas01 sshd[11033]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=149.135.121.242 Mar 11 05:39:01 dallas01 sshd[11033]: Failed password for invalid user tecnici from 149.135.121.242 port 38700 ssh2 Mar 11 05:41:01 dallas01 sshd[12646]: Failed password for root from 149.135.121.242 port 49016 ssh2 |
2020-03-12 02:15:37 |
| 218.90.138.98 | attackspambots | $f2bV_matches |
2020-03-12 01:57:09 |
| 73.198.6.163 | attack | Invalid user pi from 73.198.6.163 port 52324 |
2020-03-12 02:01:41 |
| 59.108.143.83 | attackspam | suspicious action Wed, 11 Mar 2020 11:36:25 -0300 |
2020-03-12 02:07:03 |
| 148.70.242.55 | attackspam | 5x Failed Password |
2020-03-12 02:12:47 |
| 41.46.229.86 | attack | 1583923272 - 03/11/2020 11:41:12 Host: 41.46.229.86/41.46.229.86 Port: 445 TCP Blocked |
2020-03-12 02:19:00 |
| 106.12.49.158 | attackbotsspam | Mar 10 13:33:24 lock-38 sshd[8936]: Failed password for invalid user oikawa from 106.12.49.158 port 35960 ssh2 Mar 10 13:58:08 lock-38 sshd[9118]: Failed password for invalid user developer from 106.12.49.158 port 55644 ssh2 ... |
2020-03-12 01:58:04 |
| 88.135.39.140 | attack | Mar 11 18:21:51 srv-ubuntu-dev3 sshd[22759]: Invalid user elasticsearch from 88.135.39.140 Mar 11 18:21:51 srv-ubuntu-dev3 sshd[22759]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.135.39.140 Mar 11 18:21:51 srv-ubuntu-dev3 sshd[22759]: Invalid user elasticsearch from 88.135.39.140 Mar 11 18:21:53 srv-ubuntu-dev3 sshd[22759]: Failed password for invalid user elasticsearch from 88.135.39.140 port 35032 ssh2 Mar 11 18:26:21 srv-ubuntu-dev3 sshd[23443]: Invalid user sinusbot from 88.135.39.140 Mar 11 18:26:21 srv-ubuntu-dev3 sshd[23443]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.135.39.140 Mar 11 18:26:21 srv-ubuntu-dev3 sshd[23443]: Invalid user sinusbot from 88.135.39.140 Mar 11 18:26:23 srv-ubuntu-dev3 sshd[23443]: Failed password for invalid user sinusbot from 88.135.39.140 port 42974 ssh2 Mar 11 18:30:54 srv-ubuntu-dev3 sshd[24202]: Invalid user precos from 88.135.39.140 ... |
2020-03-12 01:54:47 |
| 73.221.204.29 | attackspambots | 5x Failed Password |
2020-03-12 02:14:35 |
| 146.185.141.95 | attackbotsspam | Invalid user ubuntu from 146.185.141.95 port 36782 |
2020-03-12 01:53:04 |