Ascendant Finance crawlers: what each bot does
Ascendant Finance runs 2 bots that we document: BeaconBot, KoryoScout. They have different jobs (special-purpose crawler), so a robots.txt rule for one does not apply to the others.
| Bot | Category | robots.txt token | Honors robots.txt? | What blocking does |
|---|---|---|---|---|
| BeaconBot | Special-purpose crawler | BeaconBot | Yes, per Ascendant Finance | Ascendant Finance says any one opt-out stops all BeaconBot activity for your domain permanently, including passive lookups. Nothing about your search visibility changes. |
| KoryoScout | Special-purpose crawler | KoryoScout | Yes, per Ascendant Finance | Ascendant Finance says it then stops reading your site and stops contacting addresses at your domain. Nothing about your search visibility changes. |
Is a request really from Ascendant Finance?
A user-agent string is only a claim. These are the checks Ascendant Finance publishes for its bots; where there is none, the user agent alone cannot prove a request is genuine.
- BeaconBot: no IP list published that we found (compared 2026-11-09).
- KoryoScout: no IP list published that we found (compared 2026-11-09).
Paste an address into the crawler IP checker to test it against the lists we can read.
What Ascendant Finance says about robots.txt
BeaconBot
Ascendant Finance says it fetches robots.txt first and honors it. It accepts three opt-outs: User-agent: BeaconBot with Disallow: /, the line Beacon-Opt-Out: true in /.well-known/security.txt, or an email with the domain name.
KoryoScout
Ascendant Finance says it reads /robots.txt first and honors it, and shows User-agent: KoryoScout with Disallow: / as the opt-out. It also accepts an email with the domain name.
No request from a Ascendant Finance bot has been recorded on this site in the last 30 days. Bot traffic data