CanAgentUse tools

UCP Suite

Validate Universal Commerce Protocol discovery, then test product search, carts, checkout links, and merchant handoff flows.

MCP Playground

Connect to remote MCP servers, inspect tools and resources, test prompts, auth, headers, notifications, and JSON-RPC responses.

A2A Playground

Inspect Agent Cards, validate advertised endpoints, and prepare safe requests for agent-to-agent workflows.

Agent Website Viewer

Enter a public URL and see the roles, names, landmarks, controls, and blockers that shape how AI agents understand the page.

SCANNED
Jun 29, 2026, 10:23 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
59/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability49%Agent Easeof Use52%Security& Trust76%GEO, AIO, AEO58%SEO92%Performance94%Accessibility44%
  • AI Discoverability 49 out of 100
  • Agent Ease of Use 52 out of 100
  • Security & Trust 76 out of 100
  • GEO, AIO and AEO 58 out of 100
  • SEO 92 out of 100
  • Performance 94 out of 100
  • Accessibility 44 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Vocabulary.com - Learn Words - English Dictionary favicon

Vocabulary.com - Learn Words - English Dictionary

Vocabulary.com helps you learn new words, play games that improve your vocabulary, and explore language.

Open Agent View

Next step

Turn this report into a fix workflow

2 failed checks are ready to move into MCP or CLI remediation. Generate a repair prompt, connect the scanner to your coding agent, or open the integration docs before your next rescan.

Fix with MCP / CLI
Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
49
Priority fix1500
Discoverability
67
Needs work800
Content Readiness
14
Priority fix400
Bot Access Control
63
Needs work300
Agent Ease of Use
52
Needs work210View details
Skill Discovery
55
Needs work210View details
GEO, AIO and AEO
58
Needs work700
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable200
SEO
92
Strong900
SEO
92
Strong900
Security & Trust
76
Mostly ready2022View details
Security & Trust
76
Mostly ready2022View details
Performance
94
Strong1410View details
Performance
94
Strong1410View details

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Evaluate fetch baseline".

50 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

CSP does not define default-src; several fetch directives may have no restrictive fallback.

02

Why it matters

Content Security Policy reduces the impact of injection bugs by limiting where scripts, styles, frames, forms, and other browser resources can load or execute.

Check name

Content-Security-Policy

Score

50/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Constrain browser resource loading and script execution with an enforcing Content-Security-Policy header.

Result

Content-Security-Policy failed at "Evaluate fetch baseline".

Validation steps

  1. Evaluate fetch baseline

    CSP does not define default-src; several fetch directives may have no restrictive fallback.

  2. Evaluate script execution

    No script-src or default-src directive constrains script execution.

  3. Review hardening directives

    CSP is missing recommended hardening directives: object-src, base-uri, form-action.

  4. Review CSP reporting

    CSP does not define a reporting endpoint.

Evidence log4 steps · 16 lines
Evaluate fetch baseline [fail]! CSP does not define default-src; several fetch directives may have no restrictive fallback.INFOEvaluate fetch baselineINFOEvaluate resource loading fallback explicitFetchDirectives=[]FAILCompare fetch baseline actual="0 explicit fetch directives" expected="restricted default-src or broad explicit fetch coverage" issue="CSP does not define default-src; several fetch directives may have no restrictive fallback."FAILCSP does not define default-src; several fetch directives may have no restrictive fallback.Evaluate script execution [fail]! No script-src or default-src directive constrains script execution.INFOEvaluate script executionINFOInspect effective script directive FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":false,"hasUnsafeEval":false,"hasWildcardHost":false,"hasBroadScheme":false,"dangerousSchemes":[]} expected="constrained script sources without unsafe execution allowances" issue="No script-src or default-src directive constrains script execution."FAILNo script-src or default-src directive constrains script execution.Review hardening directives [warning]! CSP is missing recommended hardening directives: object-src, base-uri, form-action.INFOReview hardening directivesINFOInspect CSP hardening directives frameAncestors=["'self'"] formCount=2WARNCompare recommended hardening coverage actual=["object-src","base-uri","form-action"] expected="no missing object-src/base-uri/form-action requirements" issue="CSP is missing recommended hardening directives: object-src, base-uri, form-action."WARNCSP is missing recommended hardening directives: object-src, base-uri, form-action.Review CSP reporting [warning]! CSP does not define a reporting endpoint.INFOReview CSP reportingINFOInspect CSP reporting directives reportOnlyHeaderPresent=false reportOnlyDirectives=[]WARNCompare violation reporting configuration actual="no reporting endpoint" expected="report-to or report-uri present" issue="CSP does not define a reporting endpoint."WARNCSP does not define a reporting endpoint.

Agent Ease of UseSkill DiscoveryEmerging recommendation

DNS-AID Agent Discovery

DNS-AID Agent Discovery failed at "Validate HTTPS/SVCB shape".

29 Fail

Needs attention

DNS-AID Agent Discovery

Failed check
01

Issue

One or more DNS-AID records could not be parsed as usable HTTPS/SVCB ServiceMode records.

Details

02

Why it matters

DNS-AID lets agents discover index, A2A, and other agent entrypoints before fetching HTTP metadata. HTTPS/SVCB records provide the service-binding substrate, while DNSSEC can authenticate the discovery answer when available.

Check name

DNS-AID Agent Discovery

Score

71/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish DNS-AID HTTPS/SVCB records under _agents for DNS-based agent entrypoint discovery.

Result

DNS-AID Agent Discovery failed at "Validate HTTPS/SVCB shape".

Validation steps

  1. Validate HTTPS/SVCB shape

    One or more DNS-AID records could not be parsed as usable HTTPS/SVCB ServiceMode records.

    Malformed record issues
    [
      {
        "ownerName": "_index._agents.www.vocabulary.com",
        "rrtype": "HTTPS",
        "ttl": 60,
        "mode": "unknown",
        "targetName": "30",
        "params": [
          {
            "key": "00",
            "value": "present"
          },
          {
            "key": "01",
            "value": "present"
          },
          {
            "key": "00",
            "value": "present"
          },
          {
            "key": "00",
            "value": "present"
          },
          {
            "truncated": true,
            "omittedCount": 26,
            "originalCount": 30
          }
        ],
        "mandatory": [],
        "alpn": [],
        "endpointIssue": "missing endpoint",
        "unknownParams": [
          "00",
          "01",
          "00",
          "00",
          {
            "truncated": true,
            "omittedCount": 26,
            "originalCount": 30
          }
        ],
        "parseWarnings": [
          "SvcPriority is missing or not numeric."
        ],
        "source": "cloudflare-doh-json",
        "raw": "\\# 30 00 01 00 00 01 00 03 02 68 32 00 06 00 10 26 06 47 00 83 b1 8e 85 a5 76 00 00 fc 6f b2 07"
      },
      {
        "ownerName": "_a2a._agents.www.vocabulary.com",
        "rrtype": "HTTPS",
        "ttl": 60,
        "mode": "unknown",
        "targetName": "30",
        "params": [
          {
            "key": "00",
            "value": "present"
          },
          {
            "key": "01",
            "value": "present"
          },
          {
            "key": "00",
            "value": "present"
          },
          {
            "key": "00",
            "value": "present"
          },
          {
            "truncated": true,
            "omittedCount": 26,
            "originalCount": 30
          }
        ],
        "mandatory": [],
        "alpn": [],
        "endpointIssue": "missing endpoint",
        "unknownParams": [
          "00",
          "01",
          "00",
          "00",
          {
            "truncated": true,
            "omittedCount": 26,
            "originalCount": 30
          }
        ],
        "parseWarnings": [
          "SvcPriority is missing or not numeric."
        ],
        "source": "cloudflare-doh-json",
        "raw": "\\# 30 00 01 00 00 01 00 03 02 68 32 00 06 00 10 26 06 47 00 90 d1 8e 85 a5 76 00 00 fc 6f b2 07"
      }
    ]
Evidence log1 step · 6 lines
Validate HTTPS/SVCB shape [fail]! One or more DNS-AID records could not be parsed as usable HTTPS/SVCB ServiceMode records.INFOValidate HTTPS/SVCB shapeFAILCompare parsed DNS-AID record count actual=2 expected="> 0"FAILCompare ServiceMode record count actual=0 expected="> 0"FAILDNS-AID record has parse/shape warnings ownerName="_index._agents.www.vocabulary.com" rrtype="HTTPS" mode="unknown" warnings=["SvcPriority is missing or not numeric."]FAILDNS-AID record has parse/shape warnings ownerName="_a2a._agents.www.vocabulary.com" rrtype="HTTPS" mode="unknown" warnings=["SvcPriority is missing or not numeric."]FAILOne or more DNS-AID records could not be parsed as usable HTTPS/SVCB ServiceMode records.

PerformancePerformanceBrowser audit

Improve image delivery

100 Fail

Check name

Improve image delivery

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 227 KiB

Fix guidance

Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery)

Evidence
{
  "displayValue": "Est savings of 227 KiB",
  "description": "Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery)"
}

Sign in to see 35 other issues and the full report

Create a free account to unlock every issue, evidence details, exports, and higher free limits.

Fix with MCP or CLI

Use this report as the handoff into remediation. Generate a coding-agent prompt with the failing checks attached, or jump to the MCP and CLI setup docs before your next rescan.

Fix with MCP / CLI

Score history