Two public profiles · no score or winner
digsby.com and hindaspace.com
Measured takeaway
Botfy does not have comparable evidence for a strong policy takeaway; the available states are shown below.
Measured in Botfy's 2026-09-07 publication.At a glance
A difference appears only when both sites have comparable evidence. Unavailable or unresolved observations remain incomplete.
| Evidence | digsby.com | hindaspace.com |
|---|---|---|
| robots.txt | Returned HTTP 409 | Served and parsed |
| Google crawl posture | Open | Open |
| Unnamed crawler fallback | Unavailable | Allowed the wildcard (*) group is effectively open |
| Base /llms.txt | Not probed | Not probed |
Treatment by purpose
Only resolved blocked, allowed, or mixed states count as a policy agreement or difference. Unnamed agents still inherit each site's wildcard rules.
| Declared purpose | digsby.com | hindaspace.com |
|---|---|---|
| Model training | Observation unavailable | Blocked |
| AI search | Observation unavailable | Not explicitly addressed |
| Live assistant fetch | Observation unavailable | Blocked |
| Opt-out directives | Observation unavailable | Not explicitly addressed |
| Ambiguous / undocumented | Observation unavailable | Not explicitly addressed |
Named agents
Measured differences appear first. “Not explicitly addressed” is not the same as allowed; the site's wildcard fallback governs that crawler.
| Agent | digsby.com | hindaspace.com |
|---|---|---|
| GPTBot OpenAI | Observation unavailable | Blocked |
| ClaudeBot Anthropic | Observation unavailable | Blocked |
| CCBot Common Crawl | Observation unavailable | Blocked |
| meta-externalagent Meta | Observation unavailable | Blocked |
| ChatGPT-User OpenAI | Observation unavailable | Blocked |
How each site compares with its own rank peers
The sites may belong to different rank bands. Each percentage keeps its own population and denominator; Botfy does not subtract rates from unlike cohorts.
| Trait | digsby.com | hindaspace.com |
|---|---|---|
| Wildcard group | Parsing unavailable 89.6% Ranks 100,001–1,000,000 · n=680,000 | Yes 89.6% Ranks 100,001–1,000,000 · n=680,000 |
| Effectively open file | Parsing unavailable 26.0% Ranks 100,001–1,000,000 · n=680,000 | Yes 26.0% Ranks 100,001–1,000,000 · n=680,000 |
| Sitemap declared | Parsing unavailable 60.6% Ranks 100,001–1,000,000 · n=680,000 | Yes 60.6% Ranks 100,001–1,000,000 · n=680,000 |
| robots.txt served | No 61.8% Ranks 100,001–1,000,000 · n=1,111,034 | Yes 61.8% Ranks 100,001–1,000,000 · n=1,111,034 |
| robots.txt returned 404 | No 8.5% Ranks 100,001–1,000,000 · n=1,111,034 | No 8.5% Ranks 100,001–1,000,000 · n=1,111,034 |
| Over the RFC parse limit | Parsing unavailable 0.3% Ranks 100,001–1,000,000 · n=680,000 | No 0.3% Ranks 100,001–1,000,000 · n=680,000 |
| Blanket disallow | Parsing unavailable 10.8% Ranks 100,001–1,000,000 · n=680,000 | No 10.8% Ranks 100,001–1,000,000 · n=680,000 |
How this comparison is measured
Both sites use Botfy's latest published observations. A missing fetch, unresolved agent verdict, and measured absence are different states. Peer percentages use each site's exclusive Tranco rank band and print their own denominator. Populations, sources, and limits →