# Dpok (dpok.com): agent-readiness 17/100, grade F

> Rank 981 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-29T03:40:16.250Z. Page: https://qomvia.com/site/dpok-com  JSON: https://qomvia.com/api/score/dpok-com

## Summary

{
  "known": false,
  "confidence": "low",
  "summary": "I do not have specific, pre-audited information about dpok.com in my knowledge base. Therefore, I cannot provide a summary of what this site is or what it does.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "The specific business model of dpok.com",
    "The primary services or products offered by dpok.com",
    "The target demographic or audience for dpok.com",
    "The geographic markets in which dpok.com operates",
    "Any notable features or unique selling propositions of dpok.com"
  ],
  "alternatives": [],
  "business": "No information available.",
  "competitors": []
}

## Score by group
- Machine access: 9/24
- Content legibility: 0/26
- Discovery surface: 0/20
- Identity & policy: 0/12
- Agent-facing performance: 8/8
- Agent protocols: 0/10
Failing checks:
- [blocker] Page metadata is incomplete
- [blocker] No discoverable sitemap
- [blocker] No llms.txt
- [blocker] The site does not say who it is
- [blocker] Content is buried in boilerplate

## FAQ
Q: Is Dpok readable by AI agents?
A: Dpok (dpok.com) scores 17 out of 100 for agent readiness, grade F, measured yesterday, on 29.09.2026. 0 of 3 agent classes we test can use the site, and 10 checks currently block agents outright.

Q: What stops agents from using dpok.com?
A: The heaviest problems are: Page metadata is incomplete; No discoverable sitemap; No llms.txt; The site does not say who it is; Content is buried in boilerplate. Each one is scored from a public HTTP response, and the fix for each is listed in the signed-in report.

Q: How is the Dpok agent-readiness score calculated?
A: Qomvia fetches public pages of dpok.com as an AI agent would and runs the core checks every site gets across 6 groups: Machine access, Content legibility, Discovery surface, Identity & policy, Agent-facing performance, Agent protocols. Checks are weighted by how much an agent loses when they fail, and the score is expressed out of 100.

Q: How often is this score updated?
A: Public scores are re-checked when the site is re-scanned; tracked domains are re-scanned weekly and their owners are alerted when a check regresses. This page shows the scan from yesterday, on 29.09.2026.

## Related
- Leaderboard: https://qomvia.com/leaderboard
- Score another site: https://qomvia.com/