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
Aug 1, 2026, 5:12 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
48/100

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability44%Agent Easeof Use51%Security& Trust62%GEO, AIO, AEO33%SEO83%Performance36%Accessibility63%
  • AI Discoverability 44 out of 100
  • Agent Ease of Use 51 out of 100
  • Security & Trust 62 out of 100
  • GEO, AIO and AEO 33 out of 100
  • SEO 83 out of 100
  • Performance 36 out of 100
  • Accessibility 63 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Login - Oniroco favicon

Login - Oniroco

No page metadata or readable excerpt was captured.

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
44
Priority fix1300
Discoverability
40
Priority fix400
Content Readiness
16
Priority fix500
Bot Access Control
69
Needs work400
Agent Ease of Use
51
Needs work221View details
Skill Discovery
53
Needs work111View details
Google Agentic Browsing
50
Needs work110View details
GEO, AIO and AEO
33
Priority fix200
AIO Readiness
Not Applicable
Not Applicable100
AEO Readiness
Not Applicable
Not Applicable100
SEO
83
Mostly ready700
SEO
83
Mostly ready700
Security & Trust
62
Needs work1410View details
Security & Trust
62
Needs work1410View details
Performance
36
Priority fix1300
Performance
36
Priority fix1300

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Find enforcing CSP delivery".

60 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

Only Content-Security-Policy-Report-Only is present; report-only policies are not enforced.

Details

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

40/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 "Find enforcing CSP delivery".

Validation steps

  1. Find enforcing CSP delivery

    Only Content-Security-Policy-Report-Only is present; report-only policies are not enforced.

    Enforcing Content-Security-Policy header is missing
Evidence log1 step · 4 lines
Find enforcing CSP delivery [fail]! Only Content-Security-Policy-Report-Only is present; report-only policies are not enforced.INFOFind enforcing CSP deliveryINFORead CSP delivery headers enforcingHeader="missing" reportOnlyHeader="default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://use.typekit.net https://www.googletagmanager.com https://www.google-analytics.com https://ssl.google-analytics.com https://connect.facebook.net https://assets.customer.io https://cdn.lr-ingest.com https://www.clarity.ms https://browser.sentry-cdn.com https://dev.visualwebsiteoptimizer.com https://cdn.leadinfo.net; style-src 'self' 'unsafe-inline' https://use.typekit.net https://fonts.googleapis.com; font-src 'self' data:" metaPolicyCount=0 legacyHeadersPresent=[]FAILRequire enforcing Content-Security-Policy header actual="missing" expected="present" issue="Only Content-Security-Policy-Report-Only is present; report-only policies are not enforced."FAILOnly Content-Security-Policy-Report-Only is present; report-only policies are not enforced.

Agent Ease of UseSkill DiscoveryEmerging recommendation

DNS-AID Agent Discovery

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

39 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

61/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.

    DNS-AID HTTPS/SVCB records are malformed
    Malformed record issues
    [
      {
        "ownerName": "_index._agents.oniroco.app",
        "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 db d0 be 46 76 00 00 8b 7f 2f 1c"
      },
      {
        "ownerName": "_a2a._agents.oniroco.app",
        "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 9b d0 be 46 76 00 00 8b 7f 2f 1c"
      }
    ]
  2. Check DNSSEC authentication evidence

    DNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.

    DNSSEC authentication evidence is missing
Evidence log2 steps · 17 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.oniroco.app" rrtype="HTTPS" mode="unknown" warnings=["SvcPriority is missing or not numeric."]FAILDNS-AID record has parse/shape warnings ownerName="_a2a._agents.oniroco.app" 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.Check DNSSEC authentication evidence [warning]! DNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.INFOCheck DNSSEC authentication evidenceWARNCompare DNSSEC authenticated-data flag actual=false expected=trueWARNCompare visible DNSSEC material actual=false expected=trueWARNResolver did not confirm authenticated DNSSEC data name="_index._agents.oniroco.app" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.oniroco.app" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.oniroco.app" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.oniroco.app" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.oniroco.app" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.oniroco.app" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="oniroco.app" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNDNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.

Agent Ease of UseGoogle Agentic BrowsingBrowser audit

Accessibility tree is not well-formed

100 Fail

Check name

Accessibility tree is not well-formed

Score

0/100

Status

fail

Device

desktop

Category

Google Agentic Browsing

Fix guidance

A well-formed [accessibility tree](https://developer.chrome.com/docs/lighthouse/agentic-browsing/accessibility-for-agents) helps AI agents to navigate and interact with the page.

Evidence
{
  "description": "A well-formed [accessibility tree](https://developer.chrome.com/docs/lighthouse/agentic-browsing/accessibility-for-agents) helps AI agents to navigate and interact with the page."
}

Sign in to see 42 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