# pqoqubbw.md/%EF%BD%B0www.esecurify.com

[pqoqubbw.md/%EF%BD%B0www.esecurify.com](https://pqoqubbw.md/%EF%BD%B0www.esecurify.com)

- **Overall score:** 15/100 (Grade F)
- **Checks passed:** 1 / 30
- **Last computed:** 2026-06-10

## Components

### Content Discoverability

- **Score:** 0/100 · **Status:** fail
- **Summary:** 3 failed and 4 skipped across 7 AFDocs checks.
- **Rationale:** Agents need a clear entry point and crawl map before they can reliably discover the right pages.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ❌ **LLMS TXT Exists** — No llms.txt found at any candidate location (https://pqoqubbw.md/%EF%BD%B0www.esecurify.com/llms.txt, https://pqoqubbw.md/llms.txt, https://pqoqubbw.md/docs/llms.txt); 3 failed to fetch Create an llms.txt file at your site root containing an H1 title, a blockquote summary, and markdown links to your key documentation pages. This is the single highest-impact improvement for agent access to your docs.
- ⏭️ **LLMS TXT Valid** — Skipped: dependency check did not pass
- ⏭️ **LLMS TXT Size** — Skipped: dependency check did not pass
- ⏭️ **LLMS TXT Links Resolve** — Skipped: dependency check did not pass
- ⏭️ **LLMS TXT Links Markdown** — Skipped: dependency check did not pass
- ❌ **LLMS TXT Directive Html** — Could not test any pages; 1 failed to fetch No agent-facing directive pointing to llms.txt was detected in the HTML of any tested page. Add a visually-hidden element near the top of each page (e.g., a div with CSS clip-rect) containing a link to your llms.txt. If your site serves markdown versions of pages, mention that in the directive too so agents know to request it.
- ❌ **LLMS TXT Directive MD** — Could not fetch markdown for any of 1 pages; 1 had no markdown version No llms.txt directive was detected in the markdown of any tested page. Add a blockquote near the top of each markdown page (e.g., "> For the complete documentation index, see [llms.txt](/llms.txt)").

### Markdown Availability

- **Score:** 0/100 · **Status:** fail
- **Summary:** 2 failed across 2 AFDocs checks.
- **Rationale:** When markdown is available directly, agents spend less effort stripping presentation markup and guessing structure.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ❌ **Markdown Url Support** — No pages support .md URLs (0/0 tested) Your pages don't return markdown when .md is appended to the URL. Configure your docs platform to serve .md variants for all documentation pages.
- ❌ **Content Negotiation** — Server ignores Accept: text/markdown header (0/0 pages return markdown) Your server ignores Accept: text/markdown and returns HTML. Some agents (Claude Code, Cursor, OpenCode) request markdown this way. Configure your server to honor content negotiation.

### Page Size and Truncation Risk

- **Score:** 0/100 · **Status:** fail
- **Summary:** 3 failed and 1 skipped across 4 AFDocs checks.
- **Rationale:** Large pages and delayed primary content increase truncation risk and make retrieval less reliable.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ❌ **Rendering Strategy** — Could not fetch any pages to analyze; 1 failed to fetch 0 of 1 pages use client-side rendering. Agents receive an empty shell with no documentation content. Enable server-side rendering or pre-rendering for documentation pages.
- ⏭️ **Page Size Markdown** — Skipped: dependency check did not pass
- ❌ **Page Size Html** — Could not fetch any pages to measure; 1 failed to fetch 0 of 1 pages convert to over 100K characters of markdown. Break large pages into smaller units, reduce navigation boilerplate, or provide markdown versions that bypass the HTML conversion overhead.
- ❌ **Content Start Position** — Could not fetch any pages to analyze; 1 failed to fetch 0 of 1 pages have content starting past 50% of the converted output. Agents may never see the documentation content. Reduce navigation, breadcrumb, and sidebar markup that precedes the content area.

### Content Structure

- **Score:** 33/100 · **Status:** fail
- **Summary:** 1 failed and 1 skipped across 3 AFDocs checks.
- **Rationale:** Predictable sections, valid code fences, and serialized tabs make the content easier for agents to parse correctly.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ❌ **Tabbed Content Serialization** — Could not fetch any pages to analyze; 1 failed to fetch Tabbed content on 1 pages serializes to over 100K characters. Agents see only the first few tab variants; content in later tabs is truncated. Break variants into separate pages.
- ✅ **Section Header Quality** — No tabbed content found; header quality check not applicable
- ⏭️ **Markdown Code Fence Validity** — Site does not serve markdown content; nothing to analyze

### URL Stability and Redirects

- **Score:** 0/100 · **Status:** fail
- **Summary:** 2 failed across 2 AFDocs checks.
- **Rationale:** Stable URLs and sane redirect behavior prevent retrieval drift and broken tool references.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ❌ **Http Status Codes** — Could not test any URLs; 1 failed to fetch Your site returns 200 for non-existent pages (soft 404). Agents try to extract information from the error page content instead of recognizing the page is missing. Configure your server to return 404 for pages that don't exist.
- ❌ **Redirect Behavior** — Could not test any URLs; 1 failed to fetch JavaScript-based redirects detected on 0 pages. Agents don't execute JavaScript and will not follow these redirects. Use HTTP 301/302 redirects instead.

### Observability and Content Health

- **Score:** 0/100 · **Status:** fail
- **Summary:** 1 failed and 2 skipped across 3 AFDocs checks.
- **Rationale:** Coverage, parity, and cache behavior determine whether agents can trust the content they retrieve.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ⏭️ **LLMS TXT Coverage** — Skipped: dependency check did not pass
- ⏭️ **Markdown Content Parity** — Skipped: dependency check did not pass
- ❌ **Cache Header Hygiene** — Could not fetch any endpoints to check cache headers; 1 failed to fetch 0 endpoints have aggressive caching (>24h) or missing cache headers. Set max-age under 3600 or add must-revalidate with ETag/Last-Modified so content updates reach agents promptly.

### Authentication and Access

- **Score:** 100/100 · **Status:** fail
- **Summary:** 1 failed and 1 skipped across 2 AFDocs checks.
- **Rationale:** Agents need either public access or a clear alternative path when documentation is gated behind auth.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ❌ **Auth Gate Detection** — Could not fetch any pages to check authentication; 1 failed to fetch All or most documentation pages require authentication. Agents cannot access your documentation and will rely on potentially outdated training data or secondary sources. Consider providing alternative access paths (see auth-alternative-access check).
- ⏭️ **Auth Alternative Access** — auth-gate-detection failed due to fetch errors, not detected auth responses; cannot assess alternative access

### Full Content Discoverability

- **Score:** 0/100 · **Status:** fail
- **Summary:** llms-full.txt has 1 failing check.
- **Rationale:** A full-document snapshot gives long-context agents a single canonical corpus to ingest without repeated crawling.
- **Reference:** [llms-full.txt guide](https://www.mintlify.com/docs/ai/llmstxt#llms-full-txt)

**Checks**

- ❌ **LLMS Full Exists** — No llms-full.txt file was discovered.
- ⏭️ **LLMS Full Size** — Skipped because llms-full.txt was not found.
- ⏭️ **LLMS Full Valid** — Skipped because llms-full.txt was not found.
- ⏭️ **LLMS Full Links Resolve** — Skipped because llms-full.txt was not found.

### Agent Skills

- **Score:** 0/100 · **Status:** fail
- **Summary:** skill.md has 1 failing check.
- **Rationale:** Agent skills provide product-specific operating guidance that plain documentation pages do not encode on their own.
- **Reference:** [skill.md guide](https://www.mintlify.com/docs/ai/skillmd)

**Checks**

- ❌ **Skill MD** — No agent skill definition was discovered.

### MCP Server

- **Score:** 0/100 · **Status:** fail
- **Summary:** MCP has 1 failing check.
- **Rationale:** A discoverable MCP server lets agents use first-class tools instead of scraping pages and inferring behavior.
- **Reference:** [MCP guide](https://www.mintlify.com/docs/ai/model-context-protocol)

**Checks**

- ❌ **MCP Server Discoverable** — No MCP server was discovered at the expected endpoints.
- ⏭️ **MCP Tool Count** — Skipped because the MCP server was not discoverable.